You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Removing uses-proxyprotocol does not remove the "Proxy protocol" checkmark on Loadbalancer #876
When setting the load-balancer.hetzner.cloud/uses-proxyprotocol: "true" annotation on a loadbalancer service, the "Proxy protocol" checkmark is correctly set on a loadbalancer.
However, removing that same annotation does not unset the checkmark. The loadbalancer remains with the proxyprotocol feature enabled.
Expected behavior
The cloud controller should disable the "Proxy protocol" feature, since that is the default, and the annotation is no longer specified.
Observed behavior
The cloud controller leaves the "Proxy protocol" feature enabled.
We have discussed this issue internally and came to the conclusion, that this would a breaking change as users might have removed the annotation without setting the configured value back to its default.
Furthermore, I have checked and there are other annotations, for example the algorithm type, which keep the last configured value. To be consistent we should make this the default behavior for all annotations with a default value.
We put this task on our roadmap for a v2.0.0 release of HCCM, but I can't provide a timeframe estimate.
For now, I would ask you to configure the default value manually via the annotation and remove it once the changes have propagated.
Best Regards
Lukas
Reacted by Anders, benedikt-bartscher, Oleg Klyuchkin and M4t7e
Activity
lukasmetzner commentedon Mar 4, 2025
Hey,
I agree, this should be the expected behavior.
We have discussed this issue internally and came to the conclusion, that this would a breaking change as users might have removed the annotation without setting the configured value back to its default.
Furthermore, I have checked and there are other annotations, for example the algorithm type, which keep the last configured value. To be consistent we should make this the default behavior for all annotations with a default value.
We put this task on our roadmap for a v2.0.0 release of HCCM, but I can't provide a timeframe estimate.
For now, I would ask you to configure the default value manually via the annotation and remove it once the changes have propagated.
Best Regards
Lukas
github-actions commentedon Aug 4, 2025
This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.