OPSEXP-1199 Adds and documents a license installation mechanism #674
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
gionn
reviewed
Mar 18, 2022
alxgomz
force-pushed
the
opsexp-1199-alflicense
branch
from
712ed6c
to
7d81593
Compare
gionn
approved these changes
Mar 18, 2022
alxgomz
added a commit
that referenced
this pull request
Jan 23, 2024
* Adds and document a license installation mechanism
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.
introduces the value
repository.licenseSecretto point to the kubernetes secret where a license has previously been deployed (choice made to stick toRegistryPullSecret).Doing so it is possible to deploy from start an ACS environment with its license (without uploading through the UI), and more importantly the renewal of the license can be done on the fly and triggers pods' updates so it is taken into account immediately