Skip to content

Conversation

vriabyk
Copy link

@vriabyk vriabyk commented Aug 8, 2025

This PR introduces a new controller configuration flag. When enabled, this flag prevents the controller from updating the status field of Ingress resources. By default, status updates remain enabled.

New flag:

--disable-ingress-status-update (boolean, default: false)

When set, the controller will skip updating the LoadBalancer status field in managed Ingress resources.
Useful for scenarios where another controller or external process manages Ingress status, or when status updates are not desired. It won't set status field and it will be just empty:

$ k get ingress test-ingress-99999 -o jsonpath='{.status}' | jq . -r
{
  "loadBalancer": {}
}

Code changes:

  • Added the DisableIngressStatusUpdate field to the configuration struct.
  • Passed the flag through the controller and status update logic.
  • Updated the UpdateStatus method to respect the flag.
  • Updated documentation

The flag is now listed in the arguments table and has a dedicated section describing its usage and example. If the flag is not specified, status updates are enabled by default.

Copy link

stale bot commented Sep 18, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 18, 2025
@oktalz oktalz removed the stale label Sep 18, 2025
Copy link

stale bot commented Oct 18, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 18, 2025
@Sea-you
Copy link

Sea-you commented Oct 20, 2025

This is certainly a feature, I'm interested in!

@stale stale bot removed the stale label Oct 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants