Add more support for self-hosting inside an existing Kubernetes cluster #1734
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
jnfrati
reviewed
Mar 9, 2022
Co-authored-by: Nicolas Frati <nicofrati@gmail.com>
mnafees
suggested changes
Mar 9, 2022
Co-authored-by: Mohammed Nafees <hello@mnafees.me>
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.
Pull request type
Please check the type of change your PR introduces:
Pull request checklist
Please check if your PR fulfills the following requirements:
go test ./...runs successfully from the root folder.What is the current behavior?
At the moment there's no in-cluster authentication option and no support for external Helm registries.
What is the new behavior?
Technical Spec/Implementation Notes
For now Helm registries can only be linked through
porter connect helm.