This repository was archived by the owner on Mar 31, 2023. It is now read-only.
Experimental installation of addon components via kpt#297
Draft
Experimental installation of addon components via kpt#297
Conversation
Implementation is now similar to BuildAddonPlan()
Contributor
Author
|
Further musing:
|
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I created a
profilespackage structured a bit likeaddons, that uses thekptcommand to fetch and manipulate manifests.(
kptmust be already on your path for this to work)As a demonstration, re-do the Weave Net installation and CIDR setting using
kpt.A PR to add the
Kptfilefor parameter setting is at weaveworks/weave#3853