feat: Use annotation to skip ApiServer LoadBalancer reconciliation #417
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
When trying to import a cluster that is already running and fully functional, we want API LoadBalancer to be unmanaged, the same way as
SkipNetworkManagement
does for other networkingIf using the annotation suggested by the documentation:
CAPOCI does nothing and the
Cluster
resource never gets fullyProvisioned
in CAPII think a more elegant solution to my PR would be to include an
SkipApiserverManagement
toSpec.NetworkSpec.APIServerLB
, but I thought it would be less intrusive to do it as an annotationFeel free to suggest or change the proposed solution
The context of all this is trying to enable cluster-autoscaler in cluster already running in Oracle Cloud, that was not deployed via CAPI
You can find the whole PoC in https://github.com/javipolo/openshift-oci-capi-autoscaling