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
clustermesh: fix CEP status patch #16986
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
In 0681343 (from PR cilium#15632), we changed CEP CRD schema and removed the `status` subresource. This broke clustermesh logic as it was still trying to update CEP using the now removed `status` subresource. In particular, this resulted in a loss of connectivity in clustermeshes with external workloads: the VM could initially join the cluster but would immediately lose connectivity after failing to update the CEP resource (see cilium#16984 for full context). We change the clustermesh logic to adhere to the new CEP update CRD schema. Fixes: 0681343 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
nbusseneau
added
kind/bug
This is a bug in the Cilium logic.
area/clustermesh
Relates to multi-cluster routing functionality in Cilium.
release-note/misc
This PR makes changes that have no direct user impact.
labels
Jul 23, 2021
This was referenced Jul 23, 2021
Thanks for the debugging @Weil0ng :) |
Weil0ng
approved these changes
Jul 23, 2021
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.
LGTM! Thanks for the fix!
aanm
approved these changes
Jul 23, 2021
test-me-please |
|
We're in a bit of an interesting situation due to the zero-flake strategy:
😁 |
michi-covalent
approved these changes
Jul 27, 2021
michi-covalent
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Jul 27, 2021
done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/clustermesh
Relates to multi-cluster routing functionality in Cilium.
kind/bug
This is a bug in the Cilium logic.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/misc
This PR makes changes that have no direct user impact.
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.
In 0681343 (from PR #15632), we changed CEP CRD schema and removed the
status
subresource.This broke clustermesh logic as it was still trying to update CEP using the now removed
status
subresource. In particular, this resulted in a loss of connectivity in clustermeshes with external workloads: the VM could initially join the cluster but would immediately lose connectivity after failing to update the CEP resource (see #16984 for full context).We change the clustermesh logic to adhere to the new CEP update CRD schema.
Fixes: 0681343