Revert CAPO to v0.10.5 #725
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JohnGarbutt
previously approved these changes
Dec 18, 2024
sd109
force-pushed
the
revert/capo-v0.11
branch
from
dca7483 to
c40a9e0
Compare
This reverts commit 56465ee and is required for the rollback to CAPO v0.10.5
sd109
force-pushed
the
revert/capo-v0.11
branch
from
5d5d0ee to
717c7ef
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CAPO version 0.11.0 introduced a regression which causes OVN Octavia load balancers (e.g. those provisioned for ingress controllers and other services of type LoadBalancer) to stop working due to overly restrictive security groups. Until the issue is resolved we need cannot use any CAPO version after v0.10.5.