Open capaca opened 6 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/kind bug
What steps did you take and what happened: The latest release so far, 0.9.0 has a bug that needs to be fixed. When setting the
OpenStackClusterSpec.APIServerLoadBalancer.AllowedCIDRs
property, the load balancer controller tries to read the router IP list to add to add to the list of allowedCIRs from the cluster status but if the router is not set the controller crashes.Related discussion on slack: https://kubernetes.slack.com/archives/CFKJB65G9/p1710773457623259
What did you expect to happen: The cluster controller to reconcile the load balancer and set the list of allowed CIDR ranges.
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] This issue is already solved on the main branch but we need a fix for the 0.9 release.
Environment:
git rev-parse HEAD
if manually built): v0.9.0kubectl version
): v1.29.2/etc/os-release
):