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

How to deploy to GCE? #168

Open
Zhomart opened this issue Sep 11, 2016 · 1 comment
Open

How to deploy to GCE? #168

Zhomart opened this issue Sep 11, 2016 · 1 comment

Comments

@Zhomart
Copy link

Zhomart commented Sep 11, 2016

I've read the documentations, but couldn't understand how to deploy my app. Currently it asks Username/Password twice.

I Google's GCE kubernetes. I've already logged in to gcloud on my computer and got cluster credentials using $ gcloud container clusters get-credentials cluster-name.

My app consists of multiple my own services and mongodb, redis.

I'm creating separate spread repo for each service. Currently trying to deploy redis. Here is the structure:

$ tree -a
.
├── .spread
│   ├── .gitignore
│   └── git .....
├── redis.rc.yml
└── rs
    └── svc.yml

11 directories, 8 files

When I do spread deploy . it asks Username and Password. I don't understand what username/password it asks.

$ spread deploy .
Please enter Username: asd
Please enter Password: asd
Please enter Username: asd
Please enter Password: asd
Deploying 2 objects using the default context.
Did not deploy.: could not get 'default/redis-svc' (Service): the server has asked for the client to provide credentials (get services redis-svc)

Command kubectl works fine.

@onbjerg
Copy link

onbjerg commented Sep 26, 2016

Seems like it doesn't detect the credentials for some reason.

The username/password is likely the username/password for the k8s API.

You can find this in GKE under GKE > Your cluster and then by clicking "Show credentials" on your master node.

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

No branches or pull requests

2 participants