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 issues in k8s yaml files #3403

Merged
merged 1 commit into from
Oct 26, 2018

Conversation

qiell
Copy link
Contributor

@qiell qiell commented Oct 23, 2018

  • Change apigroups to apiGroups in cluster-role.yaml
  • Change resourcenames to resourceNames in cluster-role.yaml
  • Add selector in deploy.yaml and ds.yaml

Signed-off-by: Akash Srivastava akash.srivastava@openebs.io

fixes: #3400

- Change apigroups to apiGroups in cluster-role.yaml
- Change resourcenames to resourceNames in cluster-role.yaml
- Add selector in deploy.yaml and ds.yaml

Signed-off-by: Akash Srivastava <akash.srivastava@openebs.io>
Copy link
Contributor

@satyamz satyamz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@dholbach
Copy link
Contributor

Looks like the namespace 'weave' needs to be created still:

daniel@reef examples (⎈ |minikube:default)]$ kubectl apply -f k8s/
clusterrolebinding.rbac.authorization.k8s.io/weave-scope created
clusterrole.rbac.authorization.k8s.io/weave-scope created
namespace/weave created
podsecuritypolicy.extensions/weave-scope created
serviceaccount/weave-scope created
service/weave-scope-app created
Error from server (NotFound): error when creating "k8s/deploy.yaml": namespaces "weave" not found
Error from server (NotFound): error when creating "k8s/ds.yaml": namespaces "weave" not found
[daniel@reef examples (⎈ |minikube:default)]$

@satyamz
Copy link
Contributor

satyamz commented Oct 25, 2018

Hi @dholbach !
Looks like, K8s is taking time to create the namespace. Can you please create namespace first and then apply rest yaml files? This also demands for having single yaml with all the yaml together and in sequence.

@dholbach
Copy link
Contributor

Yes, looks like running the same command again made it work.

@dholbach
Copy link
Contributor

Only slightly related to this PR: is this the best way to spin up Scope in a kubernetes environment (asking for the contributor in 3149 for example).

Shall we document this somewhere? E.g.

  • spin up minikube
  • apply example/k8s
  • port-forward to access weave-scope-app

Or is there a better way?

(And thanks Akash for looking into this issue!)

@satyamz
Copy link
Contributor

satyamz commented Oct 25, 2018

@dholbach steps look good to me. Minor feedback on the above steps,

  • We need to include installation of Docker.
  • Scope app service can be exposed as a NodePort on the local setup. (Sometimes, namespace & other filters doesn't work behind kube-proxy and port-forward)

It'd be good if you can file an issue containing this info. I will have someone to send PR for the same.

Thanks.

@qiell
Copy link
Contributor Author

qiell commented Oct 25, 2018

I think for the local setup, NodePort is a good idea to access the Scope.

@dholbach
Copy link
Contributor

I filed #3406 for this. Thanks a lot.

@dholbach
Copy link
Contributor

Are we happy with this PR now or do we want to change something here?

@satyamz satyamz merged commit 296c6f2 into weaveworks:master Oct 26, 2018
@satyamz
Copy link
Contributor

satyamz commented Oct 26, 2018

Thanks!

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.

Error validating examples/k8s/cluster-role.yaml
3 participants