Open laserpedro opened 1 month ago
NOTE: the contourDeployment enables to auto define annotations and tolerations for envoy fleet so I guess that this is in a way solved. However I would be curious to know whether the behavior was intentional to revert the annotations ?
xref https://github.com/projectcontour/contour/issues/4473
I would say the behavior for this scenario is underspecified; however, I think it would be reasonable for the provisioner to not remove annotations that were set on the service out-of-band, and to only ensure that the annotations the provisioner owns are present and set correctly.
What steps did you take and what happened: [A clear and concise description of what the bug is.]
After the service envoy-xxx-gateway is created I patched it as indicated as the doc so that my cloud provider creates the LB. However, I notice that those annotations are overriden with the default ones after a certain amount of time.
What did you expect to happen:
I expect the annotations to remain in the envoy service (they are crucial as they enable the registration of new eks nodes)
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): 1.29/etc/os-release
): linux amazon