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

[doc] more tutorial for gcloud? #833

Closed
u007 opened this issue Sep 28, 2017 · 5 comments
Closed

[doc] more tutorial for gcloud? #833

u007 opened this issue Sep 28, 2017 · 5 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@u007
Copy link

u007 commented Sep 28, 2017

Hi,

it would be nice if there is a doc for kompose and kubectl with gcloud
this is my configuration, but i could not get external ip from gcloud container.
Any help on external ip?

gcloud auth login
gcloud auth application-default login
gcloud components install kubectl

setup google compute container on google cloud
click on connect to get instruction

...
kubectl proxy
kompose convert
kompose up
kompose replace ...yaml # to update

and never ever kompose down as it will delete off volumes

thank you

@u007
Copy link
Author

u007 commented Sep 28, 2017

okay i found the solution, after kompose up, i have to

kubectl delete service web
kubectl expose deployment web --type="LoadBalancer" 

assumed web is the service name

but some how it takes a long time to obtain ip

@cdrage
Copy link
Member

cdrage commented Sep 28, 2017

@u007 Hey James! thanks for leeting us know the problems with using gcloud. I am going to add a note in our tutorials / user guide for adding kubectl expose deployment web --type="LoadBalancer"

@u007
Copy link
Author

u007 commented Sep 29, 2017

@cdrage nice, that will be awesome 👍
btw, i my ip was pending because my google cloud is on free trial...

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 10, 2018
@cdrage cdrage closed this as completed Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants