We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
meshservice.status
We noticed this in the multizone scenario with statefulsets, but the repro could be way simpler:
apiVersion: apps/v1 kind: StatefulSet metadata: name: redis namespace: kuma-demo spec: selector: matchLabels: app: redis serviceName: redis replicas: 0 template: metadata: labels: app: redis spec: containers: - name: redis image: "redis" ports: - name: tcp containerPort: 6379 env: - name: POD_NAME valueFrom: fieldRef: fieldPath: metadata.name lifecycle: preStop: # delay shutdown to support graceful mesh leave exec: command: ["/bin/sleep", "30"] postStart: exec: command: ["sh", "-c", "/usr/local/bin/redis-cli set zone ${POD_NAME}"]
kuma.io/origin
kind: HostnameGenerator apiVersion: kuma.io/v1alpha1 metadata: name: local-headless-kube-mesh-service namespace: kuma-system labels: kuma.io/origin: zone spec: template: '{{ label "statefulset.kubernetes.io/pod-name" }}.{{ label "k8s.kuma.io/service-name" }}.{{ .Namespace }}.svc.mesh.local' selector: meshService: matchLabels: kuma.io/managed-by: k8s-controller k8s.kuma.io/is-headless-service: "true"
The text was updated successfully, but these errors were encountered:
michaelbeaumont
Successfully merging a pull request may close this issue.
What happened?
meshservice.status
is constantly changing from the real hostname to the error messageWe noticed this in the multizone scenario with statefulsets, but the repro could be way simpler:
kuma.io/origin
label):The text was updated successfully, but these errors were encountered: