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
envoy: Default to daemon set deployment from 1.16 #30034
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6b705c0
to
47ac43b
Compare
|
/test |
47ac43b
to
98b2992
Compare
|
/test |
98b2992
to
65cd196
Compare
|
/test |
65cd196
to
f4ec199
Compare
|
/test |
741140f
to
5433415
Compare
|
/test |
|
Adding @cilium/sig-servicemesh team for visibility and review. |
gandro
reviewed
Jan 15, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but I do wonder if we should/want to detect upgrade and keep the old behavior for existing installations. See inline comment.
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Feb 29, 2024
As Envoy DS is the default mode now, we should re-purpose the existing test to embedded mode, so that we still have required coverage. Relates: 21fa2df Relates: cilium#30034 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 5, 2024
This is to ensure that cilium-envoy will only run on the same node with cilium agent during pod scheduling. Kind note that scheduled pod will continue running, however, it will be just no-ops except a bunch of warn logs related to non-existence of shared unix domain socket. Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 5, 2024
This is to ensure that cilium-envoy will only run on the same node with cilium agent during pod scheduling. Kind note that scheduled pod will continue running, however, it will be just no-ops except a bunch of warn logs related to non-existence of shared unix domain socket. Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 5, 2024
This is the best effort to avoid cilium-envoy running on the node without cilium agent. Kind note that the extra cilium-envoy pod (if any) will be just no-ops except a bunch of warn logs related to non-existence of shared unix domain socket. Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 5, 2024
This is the best effort to avoid cilium-envoy running on the node without cilium agent. Kind note that the extra cilium-envoy pod (if any) will be just no-ops except a bunch of warn logs related to non-existence of shared unix domain socket. The reason for prefered but not required options is to avoid race condition for new installation between cilium-agent and cilium-envoy deamon sets. Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 5, 2024
This is the best effort to avoid cilium-envoy running on the node without cilium agent. Kind note that the extra cilium-envoy pod (if any) will be just no-ops except a bunch of warn logs related to non-existence of shared unix domain socket. The reason for preferred but not required options is to avoid race condition for new installation between cilium-agent and cilium-envoy deamon sets. Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 5, 2024
This is the best effort to avoid cilium-envoy running on the node without cilium agent. Kind note that the extra cilium-envoy pod (if any) will be just no-ops except a bunch of warn logs related to non-existence of shared unix domain socket. The reason for preferred but not required options is to avoid race condition for new installation between cilium-agent and cilium-envoy daemon sets. Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 12, 2024
This commit is to avoid cilium-envoy running on the node without cilium agent. Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 12, 2024
This commit is to avoid cilium-envoy running on the node without cilium agent. Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 12, 2024
This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent - tolerations with same values as the agent itself, this is to cater node without cilium cases Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 12, 2024
This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent - tolerations with same values as the agent itself, this is to cater node without cilium cases Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 12, 2024
This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent - tolerations with same values as the agent itself, this is to cater node without cilium cases Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 12, 2024
This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 12, 2024
This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Mar 12, 2024
This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: cilium#25081, cilium#30034 Fixes: cilium#31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 13, 2024
This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: #25081, #30034 Fixes: #31149 Signed-off-by: Tam Mach <tam.mach@cilium.io>
gandro
pushed a commit
that referenced
this pull request
Mar 19, 2024
[ upstream commit 44aeb53 ] [ backporter notes: Minor conflict in values.yaml due to different intendation of podAntiAffinity in v1.15 ] This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: #25081, #30034 Fixes: #31149 Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
gandro
pushed a commit
that referenced
this pull request
Mar 19, 2024
[ upstream commit 44aeb53 ] [ backporter notes: Minor conflict in values.yaml due to different intendation of podAntiAffinity in v1.14. Also needed to regenerate docs. ] This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: #25081, #30034 Fixes: #31149 Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
gandro
pushed a commit
that referenced
this pull request
Mar 20, 2024
[ upstream commit 44aeb53 ] [ backporter notes: Minor conflict in values.yaml due to different intendation of podAntiAffinity in v1.15 ] This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: #25081, #30034 Fixes: #31149 Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
gandro
pushed a commit
that referenced
this pull request
Mar 20, 2024
[ upstream commit 44aeb53 ] [ backporter notes: Minor conflict in values.yaml due to different intendation of podAntiAffinity in v1.15 ] This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: #25081, #30034 Fixes: #31149 Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
jrajahalme
pushed a commit
that referenced
this pull request
Mar 20, 2024
[ upstream commit 44aeb53 ] [ backporter notes: Minor conflict in values.yaml due to different intendation of podAntiAffinity in v1.14. Also needed to regenerate docs. ] This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: #25081, #30034 Fixes: #31149 Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
jrajahalme
pushed a commit
that referenced
this pull request
Mar 21, 2024
[ upstream commit 44aeb53 ] [ backporter notes: Minor conflict in values.yaml due to different intendation of podAntiAffinity in v1.15 ] This commit is to avoid cilium-envoy running on the node without cilium agent. Two main changes are: - nodeAffinity to make sure that cilium-envoy will not be scheduled on node without cilium agent - podAffinity with requiredDuringSchedulingIgnoredDuringExecution to cilium agent Relates: #25081, #30034 Fixes: #31149 Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/proxy
Impacts proxy components, including DNS, Kafka, Envoy and/or XDS servers.
area/servicemesh
GH issues or PRs regarding servicemesh
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/major
This PR introduces major new functionality to Cilium.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is to set the default envoy deployment to daemon set mode for new installation.