search

gameontext / gameon

The root repository provides mechanics to set up a local environment for building and testing rooms.
http://gameontext.org
Apache License 2.0
58 stars 37 forks source link

kubectl doesn't show gameon deployments by default #134

Closed evie-lau closed 6 years ago

evie-lau commented 6 years ago

The go-run.sh setup script sets the deployments' namespace to gameon-system. By default, kubectl commands will run with the default namespace, so the commands (and minikube dashboard) show nothing about the gameon deployments.

Fix: Switch the namespace to gameon-system either by:

  1. Changing the default namespace in the kubectl config with kubectl config set-context minikube --namespace=gameon-system

    • or making a new config? kubectl config set-context minikube-gameon --cluster=minikube --user=minikube --namespace=gameon-system

  2. Appending --namespace=gameon-system to every kubectl and minikube commands

Alternatively, change the gameon namespace to use the default namespace instead of having its own namespace

dshimo commented 6 years ago

Messing with 1) seemed to mess up how helm finds its charts.

Could add to docs: to view these items on the kubernetes dashboard you must switch namespace to gameon-system in the left menu

ebullient commented 6 years ago

The intention was that you, the intrepid developer, would be writing your own additional services, which would then be in the default namespace for you to control.

If you could try the iterate branch (beware, I force-push that thing.. so you need to be prepared to hard reset periodically) , go-run k .... will do the kubectl command with the gameon-system namespace

(it is mostly where I want -- there is some fiddling left with Istio, specifically chaining the gateway)

(I am unwilling to forego the namespace -- it makes it so much easier for me to completely bring up / down / purge the GO system content without corrupting whatever else they may have running.. )

dshimo commented 6 years ago

The main issue was that we didn't know why Kubernetes didn't list our deployments and services when helm did. When the script handled these automatically we weren't aware it had neatly organized them for us. It's nice and I can agree now but the docs should at least mention this

ebullient commented 6 years ago

I can add that. Thanks for the feedback. I will add to the iterate branch, and you can close this once I've done the job to your liking. =)

ebullient commented 6 years ago

PR updated. Let me know what you think.

dshimo commented 6 years ago

looks good! 👍