ingress: fix foreground deletion of Ingress #29367
Merged
Conversation
This file contains hidden or 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
1ee885c to
d78cfe6
Compare
Currently, when a shared Ingress resource (managed by Cilium) gets deleted via k8s foreground deletion (e.g. `kubectl delete ingress ... --cascade=foreground`) the corresponding shared CiliumEnvoyConfig in Ciliums namespace gets rewritten empty. This breaks all other shared Ingresses from working. The reason is an error in the condition that checks which Ingresses should be taken into account when building the model for the shared CiliumEnvoyConfig. The condition checks the `DeletionTimeStamp` (set via foreground deletion) from the modified Ingres instead of the one within the loop. In case of the foreground deletion this always evaluates to `true` - hence no entries in the CEC. This commit fixes the condition to check for any ongoing deletion on the Ingress that gets checked within the loop. Fixes: cilium#21386 Fixes: cilium#29306 Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
This commit moves the write of the log message about the deletion of a shared CiliumEnvoyConfig into the condition that checks whether it's a dedicated Ingress. This way, when deleting a shared Ingress, the irritating log message isn't displayed. Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
d78cfe6 to
c73a60a
Compare
2 tasks
|
/test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, when a shared Ingress resource (managed by Cilium) gets deleted via k8s foreground deletion (e.g.
kubectl delete ingress ... --cascade=foreground) the corresponding shared CiliumEnvoyConfig in Ciliums namespace gets rewritten empty.This breaks all shared Ingresses from working.
The reason is an error in the condition that checks which Ingresses should be taken into account when building the model for the shared CiliumEnvoyConfig.
The condition checks the
DeletionTimeStamp(set via foreground deletion) from the modified Ingress instead of the the one within the loop. In case of the foreground deletion this always evaluates totrue(exclude) - hence no entries in the CEC.This commit fixes the condition to check for any ongoing deletion on the Ingress that gets checked within the loop.
Fixes: #21386
Fixes: #29306