📖 [release-0.23.0] Remove the report of deploying on k3d #2237
+0
−168
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.
Summary
This PR deletes the report of how to run KubeStellar release 0.22.0 on three new k3d clusters. This is good because nobody wanted to maintain it and nobody wanted to see a non-maintained document. This is bad because it is deleting information that took time to develop and we do not want to lose. The good news is that Git remembers and we have it published at https://docs.kubestellar.io/release-0.22.0/direct/deploy-on-k3d/ , and with all the stress over it, we are not likely to soon forget that we had it.
Preview at https://mikespreitzer.github.io/kcp-edge-mc/doc-delete-k3d-report/readme/
Related issue(s)
This is one way to resolve issue #2230 in one specific branch,
release-0.23.0
--- which is the one that currently drives the default version of the website. PR #2234 is another. I hope that the website work inmain
will distribute the interesting content from this report into the user guide material about how to set up KubeStellar.