Add support for creation of registry secret using RKE auth config type #13153
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.
Summary
Fixes #13116
Technical notes summary
This PR adds support for creation of the
rke.cattle.io/auth-config
(RKE Auth Config) when setting a secret for the registry configuration on cluster creation.Note we already showed RKE Auth config secrets in the drop-down, but we did not offer the user the ability to create them from the cluster creation screen - this has now been addded.
The changes are all in the
SelectOrCreateAuthSecret
component. The remaining code is to add a new E2E test for these changes.Note the relevant e2e tests are also updated to delete the secrets and clusters that they create.
I also create the grammar on the create labels - I believe it should be 'an' and not 'a' for the options we have.
Areas or cases that should be tested
Cluster creation with registry configuration and RKE auth config secret auth.
Screenshot/Video
New option is added to the drop-down - see below:
Checklist