-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
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
linkerd multicluster link --ha
generates invalid deployment spec
#11603
Labels
Comments
mateiidavid
added a commit
that referenced
this issue
Nov 13, 2023
Two clusters can be linked in HA mode. When HA values are used, the service-mirror deployment receives some pod affinity rules to ensure fair scheduling of pods across a cluster's nodes. The service-mirror Deployment's template seems to be broken at the moment when using HA values. Affinity rules are incorrectly grouped under a top-level `podAntiAffinity` field. The Kubernetes API requires the rules to be grouped under a top-level `affinity` field. This change rectifies that by introducing the missing parent. Fixes #11603 Signed-off-by: Matei David <[email protected]>
mateiidavid
added a commit
that referenced
this issue
Nov 22, 2023
Two clusters can be linked in HA mode. When HA values are used, the service-mirror deployment receives some pod affinity rules to ensure fair scheduling of pods across a cluster's nodes. The service-mirror Deployment's template seems to be broken at the moment when using HA values. Affinity rules are incorrectly grouped under a top-level `podAntiAffinity` field. The Kubernetes API requires the rules to be grouped under a top-level `affinity` field. This change rectifies that by introducing the missing parent. Fixes #11603 Signed-off-by: Matei David <[email protected]>
Merged
hawkw
added a commit
that referenced
this issue
Nov 22, 2023
## edge-23.11.4 This edge release introduces support for the native sidecar containers entering beta support in Kubernetes 1.29. This improves the startup and shutdown ordering for the proxy relative to other containers, fixing the long-standing shutdown issue with injected `Job`s. Furthermore, traffic from other `initContainer`s can now be proxied by Linkerd. In addition, this edge release includes Helm chart improvements, and improvements to the multicluster extension. * Added a new `config.alpha.linkerd.io/proxy-enable-native-sidecar` annotation and `Proxy.NativeSidecar` Helm option that causes the proxy container to run as an init-container (thanks @teejaded!) (#11465; fixes #11461) * Fixed broken affinity rules for the multicluster `service-mirror` when running in HA mode (#11609; fixes #11603) * Added a new check to `linkerd check` that ensures all extension namespaces are configured properly (#11629; fixes #11509) * Updated the Prometheus Docker image used by the `linkerd-viz` extension to v2.48.0, resolving a number of CVEs in older Prometheus versions (#11633) * Added `nodeAffinity` to `deployment` templates in the `linkerd-viz` and `linkerd-jaeger` Helm charts (thanks @naing2victor!) (#11464; fixes #10680)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the issue?
I was trying out the new HA mode with
linkerd multicluster --ha
and couldn't apply the generated specs withkubectl
.How can it be reproduced?
linkerd --context=foo multicluster link --cluster-name foo --ha | kubectl --context=bar apply -f -
Logs, error output, etc
The relevant part of the spec is
output of
linkerd check -o short
Environment
Possible solution
Looking at https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#podspec-v1-core,
podAntiAffinity
only exists underspec.affinity
, so there might be something wrong with this helm chart:linkerd2/multicluster/charts/linkerd-multicluster-link/templates/service-mirror.yaml
Lines 123 to 126 in 4018b2f
Additional context
No response
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered: