-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Kubernetes docs to point to install pages. #10293
Conversation
Adds more clear indicators that the collections on the learn.hashicorp.com sites have specific instructions for single node deployments. Co-Authored by: soonoo <qpseh2m7@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I agree this makes the install a bit more generic and gives the practitioner the ability to choose their platform
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/374360. |
🍒✅ Cherry pick of commit 835bf26 onto |
Adds more clear indicators that the collections on the learn.hashicorp.com sites have specific instructions for single node deployments. Co-Authored by: soonoo <qpseh2m7@gmail.com>
🍒✅ Cherry pick of commit 835bf26 onto |
Adds more clear indicators that the collections on the learn.hashicorp.com sites have specific instructions for single node deployments. Co-Authored by: soonoo <qpseh2m7@gmail.com>
Adds more clear indicators that the collections on the learn.hashicorp.com sites have specific instructions for single node deployments.
Closes #8260 as the docs pages have since been moved.
Co-Authored by: soonoo qpseh2m7@gmail.com