Manage Floaty IAMv3 credentials in Terraform via vshn-lbaas-exoscale v6.0.0 #91
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
simu
force-pushed
the
feat/floaty-iamv3
branch
from
f878176
to
8271bb5
Compare
haasad
approved these changes
Feb 15, 2024
simu
changed the title
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.
This is a breaking change for clusters that were setup with or upgraded to v3 of the Terraform module because migrating to the new Terraform-managed Floaty credentials will require manual steps to ensure that the migration takes place without outages. We'll provide detailed instructions for the upgrade in the openshift4-terraform Commodore component.
Replaces #90
Checklist
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog