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

Fix Kubernetes docs #1479

Merged
merged 3 commits into from
May 11, 2016
Merged

Fix Kubernetes docs #1479

merged 3 commits into from
May 11, 2016

Conversation

errordeveloper
Copy link
Contributor

No description provided.


The simplest way to get the latest release of Scope deployed onto a Kubernetes cluster is the following:

kubectl create -f 'https://scope.weave.works/launch/k8s/weavescope.json' --validate=false
kubectl --namespace=kube-system create -f 'https://scope.weave.works/launch/k8s/weavescope.json' --validate=false

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

@errordeveloper
Copy link
Contributor Author

One takeaway I thin is to consider that Scope simply deserves it's own namespace.

Also, do consider what if we did infer the namespace, and user specifies --namespace=myscope-namespace?

@2opremio
Copy link
Contributor

2opremio commented May 11, 2016

@errordeveloper Again, Scope needs to run in the same namespace as kube-dns for #1433 to work

@errordeveloper
Copy link
Contributor Author

For the record, the service doesn't depend on DNS and simply uses:

$(WEAVESCOPE_APP_SERVICE_HOST):$(WEAVESCOPE_APP_SERVICE_PORT)

I will switch all the things default namespace, which was what I was thinking to do eventually anyway, but did this due to the lack of input on #1475.

@errordeveloper errordeveloper merged commit 99e03ce into master May 11, 2016
@errordeveloper errordeveloper deleted the docs branch May 11, 2016 17:49
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.

2 participants