gcloud container clusters create --cluster-version 1.10 --zone us-east1-d ... returns with the error message ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=No valid versions with the prefix "1.10" found..
The GKE release notes https://cloud.google.com/kubernetes-engine/release-notes#february-11-2019, indicates the specific kubernetes version is still supported.
Does anyone know what's going on?
The syntax you are using looks correct, but support for k8s 1.10 is being phased out on GKE, as per the GKE release notes entry of February 11, 2019:
Coming soon
We expect the following changes in the coming weeks. This information is not a guarantee, but is provided to help you plan for upcoming changes.
25% of the upgrades from 1.10 to 1.11.6-gke.2 will be complete.
Version 1.11.6-gke.8 will be made available.
Version 1.10 will be made unavailable.
Have you tried with the full version, say 1.10.12-gke.7?
gcloud container clusters create --cluster-version 1.10.12-gke.7 --zone us-east1-d ...
Alternatively, use 1.11, because it looks like GKE is moving that way anyhow.
Related
The page on server-side apply in the Kubernetes docs suggests that it can be enabled or disabled (e.g., the docs say, "If you have Server Side Apply enabled ...").
I have a GKE cluster and I would like to check if server-side apply is enabled. How can I do this?
You can try creating any object like namespace or so and try checking the YAML output using the command you will get an idea if SSA is enabled or not.
Command :
kubectl create ns test-ssa
Get the created namespace
kubectl get ns test-ssa -o yaml
If there is managedFields existing in output SSA is working.
Server-side-apply i think introduced around K8s version 1.14 and now it's in GA with k8s version 1.22. Wiht GKE i have noticed it's already been part of it alpha or beta.
If you are using the HELM on your GKE you might have noticed the Service Side Apply.
I am trying to install JanusGraph on google cloud using the tutorial available at the https://cloud.google.com/architecture/running-janusgraph-with-bigtable
But i am getting an error unable to recognize "": no matches for kind "Deployment" in version "apps/v1beta1", and getting the chart deprecated error . Let me know if any one is able to install the same,
With as per the documentation
gcloud container clusters create janusgraph-tutorial \
--cluster-version=1.15 \
--machine-type=n1-standard-4 \
--scopes=\
"https://www.googleapis.com/auth/bigtable.admin",\
"https://www.googleapis.com/auth/bigtable.data"
The error was ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=No valid versions with the prefix "1.15" found.
So i tried:
gcloud container ...
--cluster-version=1.20 \ ..
and i was able to create the container
later janus graph installation
helm upgrade --install --wait --timeout 600s janusgraph stable/janusgraph -f values.yaml
Release "janusgraph" does not exist. Installing it now.
WARNING: This chart is deprecated
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Deployment" in version "apps/v1beta1", unable to recognize "": no matches for kind "StatefulSet" in version "apps/v1beta1"]
Kubernetes versions resources like Deployment. Until recently (<=1.16), Deployment was available under the apps/v1beta1 API (version). Since Kubernetes 1.16 this is deprecated and removed. You must now use apps/v1.
See:
Deprecated APIs Removed in 1.16
Kubernetes API Reference 1.21
If you're able to revise these references in the tutorial, then you should do so. You may encounter other APIs that are deprecated and|or removed but only the latter should cause similar problems.
It may be preferable to "Send feedback" (bottom of tutorial) to Google asking that someone there upgrade the tutorial or provide caveats.
Curiously, I noticed that the tutorial includes creating a Kubernetes v1.15 cluster:
gcloud container clusters create janusgraph-tutorial \
--cluster-version=1.15 \
...
Per the above, that version should still support apps/v1beta1/Deployment did that not work?
Your question would benefit from additional context|detail. You write "I am getting an error" but you do not include the specific step that cause this issue. I assume it was when you attempted to deploy JanusGraph to the cluster using Helm?
helm upgrade --install ... 600s janusgraph stable/janusgraph -f values.yaml
I am trying to install Greenplum on GKE using the directions here
I make it to step 12: but my operator pod is failing because it cannot pull the secret:
kubectl logs -l app=greenplum-operator -n greenplum
{"level":"INFO","ts":"2020-03-10T18:20:50.803Z","logger":"operator-setup","msg":"Go Info","Version":"go1.13.7","GOOS":"linux","GOARCH":"amd64"}
{"level":"INFO","ts":"2020-03-10T18:20:50.803Z","logger":"operator-setup","msg":"creating operator"}
W0310 18:20:50.803978 1 client_config.go:541] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
W0310 18:20:50.804036 1 client_config.go:546] error creating inClusterConfig, falling back to default config: open /var/run/secrets/kubernetes.io/serviceaccount/token: permission denied
It looks like a permissions issue pulling the image, but the image pull test earlier in the instructions succeeded:
job.batch/greenplum-operator-fetch-test created
GREENPLUM-OPERATOR TEST OK
job.batch "greenplum-operator-fetch-test" deleted
Has anyone else run into this issue?
There's a bug the current documentation. You most likely did everything right. However, creating a GKE cluster with "Enable Kubernetes alpha features in this cluster" as listed on the prerequisites page (https://greenplum-kubernetes.docs.pivotal.io/1-12/prepare-gke.html) is no longer necessary. In fact, it's currently causing the exact issue you seem to be having. Try creating a GKE cluster following all of the documentation except make sure to NOT enable GKE "alpha features".
There was recently a Kubernetes security hole that was patched in v1.10.11 (among other versions), so I would like to upgrade to that version. I am currently on v1.10.9. However, when running the command gcloud container get-server-config to get the list of valid node versions, v1.10.11 doesn't show up. Instead, it jumps straight from v1.10.9 to v1.11.2.
Does anyone have any idea why I cannot seem to use the usual gcloud container clusters upgrade [CLUSTER_NAME] --cluster-version [CLUSTER_VERSION] to upgrade to this version?
Thanks in advance!
Based on:
https://cloud.google.com/kubernetes-engine/docs/security-bulletins#december-3-2018
If you have Kubernetes in v1.10.9 you should (to patch this security hole) update your GKE Cluster to 1.10.9-gke.5.
The following Kubernetes versions are now available for new clusters and for opt-in master upgrades for existing clusters:
1.9.7-gke.11,
1.10.6-gke.11,
1.10.7-gke.11,
1.10.9-gke.5,
1.11.2-gke.18
Please validate your Scheduled master auto-upgrades option in GKE.
If it's enabled your cluster masters were auto-upgraded by Google and the next possible version to update is further version so v1.11.2, what is showing by GKE for you.
I am running a kubernetes cluster on google cloud(version 1.3.5) .
I found a redis.yaml
that uses petset to create a redis cluster but when i run kubectl create -f redis.yaml i get the following error :
error validating "redis.yaml": error validating data: the server could not find the requested resource (get .apps); if you choose to ignore these errors, turn validation off with --validate=false
i cant find why i get this error or how to solve this.
PetSet is currently an alpha feature (which you can tell because the apiVersion in the linked yaml file is apps/v1alpha1). It may not be obvious, but alpha features are not supported in Google Container Engine.
As described in api_changes.md, alpha level API objects are disabled by default, have no guarantees that they will exist in future versions, can break compatibility with older versions at any time, and may destabilize the cluster.
I'm using PetSet with some success, for example https://github.com/Yolean/kubernetes-mysql-cluster, in zone europe-west1-d but when I tried europe-west1-c I got the aforementioned error.
Google just enabled Alpha Clusters for GKE as announced here: https://cloud.google.com/container-engine/docs/alpha-clusters
Now you are able (but not SLA covered) to use all alpha features within an alpha cluster, what was disable previously.