-
Notifications
You must be signed in to change notification settings - Fork 712
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
Simplify k8s instructions #1886
Conversation
…odern clusters, and recommend Weave Cloud usage.
|
||
**Before You Begin** | ||
Weave Cloud runs the Scope UI for you, so you don't have to configure exposing and securing it for your team. |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
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.
Rewording, on the WithWeaveCloud section, but other than that, instructions all work, so LGTM.
|
||
The simplest way to get the latest release of Scope deployed onto a Kubernetes cluster is by running the following: | ||
|
||
kubectl create -f 'https://cloud.weave.works/launch/k8s/weavescope.yaml' --validate=false | ||
$ kubectl apply -f 'https://cloud.weave.works/launch/k8s/weavescope.yaml' |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
@paulbellamy I've updated this with the wording you have suggested, PTAL. |
Removing workarounds no longer needed in modern clusters, streamline/simplify the instructions, and recommend Weave Cloud usage.
PTAL @paulbellamy. Thanks!