Rework documentation to use kcp in kind #5
Conversation
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
On-behalf-of: @SAP marko.mudrinic@sap.com Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes https://github.com/platform-mesh/backlog/issues/113
The script is based on https://github.com/kcp-dev/helm-charts/blob/5bb3b1d025e8cae6f9d974712e56d518718a9957/hack/kind-setup.sh but modified to better suit our use case and to make it more user friendly.
The documentation is updated to use kcp in kind setup, as controller running in a kind cluster can't (easily) communicate with a kcp instance running locally (outside the cluster).
The provided sample Deployment is generally universal, but has
hostAliaseswhich works only in this setup. Users who want to use this Deployment in other setups should manually removehostAliases. There's a note about this in README.