Add OfflineLicense to cluster ImportOptions - #143
Merged
Conversation
Offline installers can't reach the licensor, so the license of the cluster being imported is supplied by the user in the import request. Signed-off-by: Arnob kumar saha <arnob@appscode.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Offline (air-gapped) installers can't reach the licensor, so the license for the cluster being imported has to be supplied by the user in the import request.
Adds
offlineLicense(raw PEM) toImportOptions. b3 consumes it in the cluster import flow: for a self-managed cluster it goes into the license-proxyserver HelmRelease values, and for a spoke it goes into thelicense-proxyserver-licensessecret in the spoke's hub namespace.