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
fixed cilium-operator delete CEC cilium-ingress when other ingressclass resources are created #28638
Conversation
…ss resources are created Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Fixes cilium#28638
0400cb1
to
6b3ce74
Compare
Thanks a lot for the contribution @chaunceyjiang The check
Would be nice if you could shorten the commit message subject (first line) of your commit |
When the ingress controller is in shared mode, we create an ingress resources with an ingressclass does not belong to cilium, the ciliumEnvoyConfig resource in kube-system called cilium-ingress is deleted making all ingress routing by cilium fail. Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Fixes cilium#28638
6b3ce74
to
e688156
Compare
@mhofstetter Thank you for your reminder. |
When the ingress controller is in shared mode, we create an ingress resources with an ingressclass does not belong to cilium, the ciliumEnvoyConfig resource in kube-system called cilium-ingress is deleted making all ingress routing by cilium fail. Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Fixes cilium#28638
e688156
to
919a2c6
Compare
When the ingress controller is in shared mode, we create an ingress resources with an ingressclass does not belong to cilium, the ciliumEnvoyConfig resource in kube-system called cilium-ingress is deleted making all ingress routing by cilium fail. Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Fixes cilium#28638
919a2c6
to
b99d8ab
Compare
/test |
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 considering my suggestion
[ upstream commit d922109 ] When the ingress controller is in shared mode, we create an ingress resources with an ingressclass does not belong to cilium, the ciliumEnvoyConfig resource in kube-system called cilium-ingress is deleted making all ingress routing by cilium fail. Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Fixes cilium#28638 Signed-off-by: Tobias Klauser <tobias@cilium.io>
[ upstream commit d922109 ] When the ingress controller is in shared mode, we create an ingress resources with an ingressclass does not belong to cilium, the ciliumEnvoyConfig resource in kube-system called cilium-ingress is deleted making all ingress routing by cilium fail. Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Fixes #28638 Signed-off-by: Tobias Klauser <tobias@cilium.io>
[ upstream commit d922109 ] When the ingress controller is in shared mode, we create an ingress resources with an ingressclass does not belong to cilium, the ciliumEnvoyConfig resource in kube-system called cilium-ingress is deleted making all ingress routing by cilium fail. Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Fixes #28638 Signed-off-by: Tobias Klauser <tobias@cilium.io> Signed-off-by: Tobias Klauser <tobias@isovalent.com>
[ upstream commit d922109 ] When the ingress controller is in shared mode, we create an ingress resources with an ingressclass does not belong to cilium, the ciliumEnvoyConfig resource in kube-system called cilium-ingress is deleted making all ingress routing by cilium fail. Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Fixes #28638 Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Fixes: #28289
When the
ingress controller
is inshared
mode, we create an ingress resources with an ingressclass does not belong to cilium, the ciliumEnvoyConfig resource in kube-system called cilium-ingress is deleted making all ingress routing by cilium fail.