operator: Remove dummy ingress endpoint#43558
Conversation
dc03832 to
9eff324
Compare
|
/ci-ingress |
|
/ci-gateway-api |
|
/test |
|
@joamaki were you intending to land this in v1.19? Given reviews are all in and there's just an unresolved comment to look into, it seems like it could match the criteria for a feature freeze exception: (I see there is possible upgrade impact under discussion, if you think so then please also set the |
|
Proposing for 1.19 blocker for now, but if it doesn't need to go in then feel free to remove again and set |
|
Removing the release blocker and moving this back to draft. We'll need to have a good strategy for dealing with removing the dummy endpoints created by prior versions that also works with downgrading. |
9eff324 to
eb66b57
Compare
|
Re-added Helm managed |
Remove the skipping of the 192.192.192.192:9999 dummy ingress endpoint as the next commit will remove the creation of it. Signed-off-by: Jussi Maki <jussi@isovalent.com> Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
With the new agent load-balancer implementation the dummy endpoint is no longer necessary. Now that v1.18 has been released with that implementation we can remove the creation of the dummy endpoint without breaking upgrade. Note: This commit removes the dummy endpoint in the Operator- (Gateway API & dedicated Ingress) & Helm- (shared Ingress) managed `EndpointSlice`'s. The creation of the `EndpointSlice` itself will will be done in a separate PR. Fixes: cilium#19262 Signed-off-by: Jussi Maki <jussi@isovalent.com> Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
eb66b57 to
d47c890
Compare
|
Rebased on top of |
|
/test |
Now that v1.18 is out with the new LB control-plane we can finally remove the dummy ingress endpoint.
Fixes: #19262