-
Notifications
You must be signed in to change notification settings - Fork 34
如果想调整nightingale-center pod分片数,nightingale-nginx需要随着调整吗? #140
Description
默认的helm只部署了一个center&nginx,现在想调整center的分片数为3,nginx需要跟着调吗?我自己额外添加了一个svc用来暴露服务,似乎不受nginx的影响,需要调整吗?docker部署时只有n9e这个容器
kubectl get svc -n xk-n9e-dev nightingale-center-public -o yaml
apiVersion: v1
kind: Service
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{"meta.helm.sh/release-name":"nightingale","meta.helm.sh/release-namespace":"xk-n9e-dev"},"labels":{"app":"n9e","app.kubernetes.io/managed-by":"Helm","chart":"nightingale","heritage":"Helm","release":"nightingale"},"name":"nightingale-center-public","namespace":"xk-n9e-dev"},"spec":{"externalIPs":["公网地址"],"internalTrafficPolicy":"Cluster","ipFamilies":["IPv4"],"ipFamilyPolicy":"SingleStack","ports":[{"name":"port","port":17777,"protocol":"TCP","targetPort":17000}],"selector":{"app":"n9e","component":"center","release":"nightingale"},"sessionAffinity":"None","type":"ClusterIP"}}
meta.helm.sh/release-name: nightingale
meta.helm.sh/release-namespace: xk-n9e-dev
creationTimestamp: "2025-11-04T13:49:10Z"
labels:
app: n9e
app.kubernetes.io/managed-by: Helm
chart: nightingale
external-vip: "true"
heritage: Helm
release: nightingale
name: nightingale-center-public
namespace: xk-n9e-dev
resourceVersion: "1057767854"
uid: 5a4ef183-93b2-4761-9fd6-703c7e64c8de
spec:
clusterIP: 10.222.167.44
clusterIPs:
- 10.222.167.44
externalIPs: - 公网地址
externalTrafficPolicy: Cluster
internalTrafficPolicy: Cluster
ipFamilies: - IPv4
ipFamilyPolicy: SingleStack
ports: - name: port
port: 17777
protocol: TCP
targetPort: 17000
selector:
app: n9e
component: center
release: nightingale
sessionAffinity: None
type: ClusterIP
status:
loadBalancer: {}