Add private registry configuration to k3k clusters #570
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.
The PR adds new field to cluster spec:
The controller will read the secret if specified for the
privateRegistryand will addregistries.yamlfile in/opt/rancher/k3s/registrydirectory, the PR also adds the ability to upload certificates to be used by the registry configuration, eachtlsSecretsitem is expected to be a TLS type secret that hastls.crtandtls.keyfield, for each secret the controller will place two files in the directory:/opt/rancher/k3s/registry/ssl, for example with the configuration above, the controller will add the following files to the servers/agents pods: