Skip to content
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 install docs #2257

Merged
merged 6 commits into from
Mar 29, 2017
Merged

Conversation

errordeveloper
Copy link
Contributor

@2opremio PTAL

@@ -240,14 +240,40 @@ Allowable parameters for the launcher URL:

To download and read the Scope manifest run:

curl --silent -L --remote-name https://cloud.weave.works/launch/k8s/weavescope.yaml
curl --silent --remote-name https://cloud.weave.works/k8s/scope.yaml

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

@2opremio
Copy link
Contributor

LGTM (modulo optional minor knit) assuming it was tested for OS re-tested for kubernetes

@@ -220,15 +218,15 @@ Weave Cloud hosts the Scope UI for you, provides secure access control for your

Sign up for a [Weave Cloud account](https://cloud.weave.works/) and obtain a token. Replace `<token>` with your token by running this on the master node or on whatever machine that has `kubectl` configured to authenticate to your Kubernetes cluster:

$ kubectl apply -f 'https://cloud.weave.works/launch/k8s/weavescope.yaml?service-token=<token>'
kubectl apply -n kube-system -f 'https://cloud.weave.works/k8s/scope.yaml?service-token=<token>'

This comment was marked as abuse.

This comment was marked as abuse.

@@ -83,25 +83,23 @@ Suppose you have the following nodes in a cluster:
Using the IP addresses, you will manually peer each node with all of the other nodes during Scope launch.

**1. Run the following on each node:**
=======

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.


In the steps that follow, you will manually peer each node with all of the other nodes during Scope launch.

**1. To begin run the following on each node:**
>>>>>>> Docs update with new version

This comment was marked as abuse.

@@ -220,15 +218,15 @@ Weave Cloud hosts the Scope UI for you, provides secure access control for your

Sign up for a [Weave Cloud account](https://cloud.weave.works/) and obtain a token. Replace `<token>` with your token by running this on the master node or on whatever machine that has `kubectl` configured to authenticate to your Kubernetes cluster:

$ kubectl apply -f 'https://cloud.weave.works/launch/k8s/weavescope.yaml?service-token=<token>'
kubectl apply -n kube-system -f 'https://cloud.weave.works/k8s/scope.yaml?service-token=<token>'

This comment was marked as abuse.

##<a name="ose"></a>Installing Scope on OpenShift

To install Weave Scope on OpenShift, you first need to login as `admin` user:

This comment was marked as abuse.

oc login -u admin

Next, create a dedicated project for Weave Scope and apply policy permissions to allow Weave Scope to access Kubernetes API:

This comment was marked as abuse.


The installation method for Scope on OpenShift is very similar to the one described above for Kubernetes, but instead of `kubectl apply -n kube-system ...` you need to use
`oc apply ...` and install it into the namespace of the `weave-scope` project you have just created, and not the `kube-system` namesapce, i.e.:

This comment was marked as abuse.

This comment was marked as abuse.

@errordeveloper
Copy link
Contributor Author

@abuehrle I've addressed you comments above, please take another look 👍

@2opremio
Copy link
Contributor

Ping

@errordeveloper
Copy link
Contributor Author

I've tested it, but after seeing #2258 I'm puzzled if we should publicise the OpenShift instructions... I will need to test on a different installation.

@errordeveloper
Copy link
Contributor Author

However, I must that these instructions are functional as such.

@errordeveloper
Copy link
Contributor Author

@2opremio @abuehrle I've commented out OpenShift part for the time being, as it's more critical to ensure that general Kubernetes instructions are correct.

@2opremio 2opremio merged commit c3a4496 into weaveworks:master Mar 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants