5 ms·

FWIW, if you create a GKE cluster and create an nginx deployment: kubectl apply -f https://k8s.io/docs/tasks/run-application/deployment.yaml https://k8s.io/doc

FWIW, if you create a GKE cluster and create an nginx deployment: kubectl apply -f https://k8s.io/docs/tasks/run-application/deployment.yaml https://k8s.io/docs/tasks/run-application/deployment.yaml And simply create a Load Balancer: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/ https://kubernetes.io/docs/tasks/access-application-cluster/... You have nginx exposed via an external IP address in about two minutes. Once you're comfortable with that, you can start working in Ingress and such to get more sophisticated. I agree the IRC/Slack channel communication isn't the best. I prefer the Kubernetes User Group. You can usually get a great response in less than a day. I've used it a lot.

linkmotif 9y ago
I was going to suggest this. Create a GKE cluster and play with it for a while to see what you’re supposed to have. Then you can create one yourself from scratch once you understand the target.
- merb 9y ago
  well that's what I tried. and basically I get: > gcloud container clusters get-credentials cluster-1 ...trimmed > Fetching cluster endpoint and auth data. > ERROR: (gcloud.container.clusters.get-credentials) ResponseError: code=404, message=The resource "projects/infinite-alcove-164114/zones/europe-west3-c/clusters/cluster-1" was not found. > Could not find [cluster-1] in [europe-west3-c]. > Did you mean [cluster-1] in [europe-west3]? note that neither gcloud alpha, nor glcoud beta nor europe-west3-(a|b|c) worked. prolly a bug when using `Regional (Beta)`.
  - thesandlord 9y ago
    Try: gcloud beta clusters get-credentials cluster-1 --region europe-west3 You need the beta command, and you need to set the region flag instead of the zone flag. Looks like there are some documentation and UX gaps, I'm opening tickets to get them fixed (I work for Google).
    - merb 9y ago
      hm... thanks. I also needed to set `gcloud beta config set container/use_v1_api_client false`. well I also was to lazy to just copy & past from the connect window.
  - swozey 9y ago
    I was in the Regional Alpha so I'm familiar with this but it's been awhile since I had the issue. The fix I believe was;; export CLOUDSDK_CONTAINER_USE_V1_API_CLIENT=false Note; It's in beta now and I believe --region was added to the recent gcloud command but I could be incorrect. If you have problems msg me on k8s slack, mikej, I can run through it with you. I don't believe you need this at all now that it's beta, but I set up my beta regional cluster a few weeks ago. Also, re: IRC, there are 27k people on the k8s slack. I've used k8s for years and never gone into irc. I just don't use irc anymore.
    - merb 9y ago
      thanks for your help, but I guess I'm fine now (just trying out stuff) well the ENV probably would have helped but there is also a config: `gcloud beta config set container/use_v1_api_client false` and I needed the --region (I always used --zone, since that was what the GUI suggested).
  - linkmotif 9y ago
    Make sure you setup gcloud and kubectl bash autocomplete. Kind of essential to me, especially kubectl.

linkmotif 9y ago

I was going to suggest this. Create a GKE cluster and play with it for a while to see what you’re supposed to have. Then you can create one yourself from scratch once you understand the target.

merb 9y ago
well that's what I tried. and basically I get: > gcloud container clusters get-credentials cluster-1 ...trimmed > Fetching cluster endpoint and auth data. > ERROR: (gcloud.container.clusters.get-credentials) ResponseError: code=404, message=The resource "projects/infinite-alcove-164114/zones/europe-west3-c/clusters/cluster-1" was not found. > Could not find [cluster-1] in [europe-west3-c]. > Did you mean [cluster-1] in [europe-west3]? note that neither gcloud alpha, nor glcoud beta nor europe-west3-(a|b|c) worked. prolly a bug when using `Regional (Beta)`.
- thesandlord 9y ago
  Try: gcloud beta clusters get-credentials cluster-1 --region europe-west3 You need the beta command, and you need to set the region flag instead of the zone flag. Looks like there are some documentation and UX gaps, I'm opening tickets to get them fixed (I work for Google).
  - merb 9y ago
    hm... thanks. I also needed to set `gcloud beta config set container/use_v1_api_client false`. well I also was to lazy to just copy & past from the connect window.
- swozey 9y ago
  I was in the Regional Alpha so I'm familiar with this but it's been awhile since I had the issue. The fix I believe was;; export CLOUDSDK_CONTAINER_USE_V1_API_CLIENT=false Note; It's in beta now and I believe --region was added to the recent gcloud command but I could be incorrect. If you have problems msg me on k8s slack, mikej, I can run through it with you. I don't believe you need this at all now that it's beta, but I set up my beta regional cluster a few weeks ago. Also, re: IRC, there are 27k people on the k8s slack. I've used k8s for years and never gone into irc. I just don't use irc anymore.
  - merb 9y ago
    thanks for your help, but I guess I'm fine now (just trying out stuff) well the ENV probably would have helped but there is also a config: `gcloud beta config set container/use_v1_api_client false` and I needed the --region (I always used --zone, since that was what the GUI suggested).
- linkmotif 9y ago
  Make sure you setup gcloud and kubectl bash autocomplete. Kind of essential to me, especially kubectl.