Configurer Monitoring et Logging en natif sur GKE avis
16431 avis
unable to recognize "hello-v2.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"
Ramnath G. · Examiné il y a presque 6 ans
Mohanakrishnan S. · Examiné il y a presque 6 ans
first part of lab not working
joby d. · Examiné il y a presque 6 ans
Junaid K. · Examiné il y a presque 6 ans
the infromation is obsolete it is not possible to launch the example on the latest version of GKE it is necesary to usea cluster with kubernetes 1.15 since with 1.16 it is not possible continnue the lab
Jorge H. · Examiné il y a presque 6 ans
as always this labs are not working as is expected
Jorge H. · Examiné il y a presque 6 ans
unable to recognize "hello-v2.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"
Ramnath G. · Examiné il y a presque 6 ans
Steven A. · Examiné il y a presque 6 ans
Gabriel V. · Examiné il y a presque 6 ans
Kevin S. · Examiné il y a presque 6 ans
kubectl create -f hello-v2.yaml error: unable to recognize "hello-v2.yaml": no matches for kind "Deployment" in version "extensions/v1beta1" if cluster version is higher then --cluster-version=1.15.12-gke.4000 If you try to change "extensions/v1beta1" in hello-v2.yaml to more convenient api for default cluster 16.xx lab checks won't work.
Stanislav S. · Examiné il y a presque 6 ans
Saurabh S. · Examiné il y a presque 6 ans
The first task was completed successfully. But "Check my Progress" did not recognized the completion
Bharath Kumar B. · Examiné il y a presque 6 ans
Predrag M. · Examiné il y a presque 6 ans
there is a error when to create pods for hello-v2. error: unable to recognize "hello-v2.yaml": no matches for kind "Deployment" in version "app/v1" If I use "apps/v1", then pods is successfully created, but task point was not recognized.
Kim J. · Examiné il y a presque 6 ans
Lara Z. · Examiné il y a presque 6 ans
srinivas v. · Examiné il y a presque 6 ans
Fagner M. · Examiné il y a presque 6 ans
hello-v2.yaml not working, first checkpoint not working
Even -. · Examiné il y a presque 6 ans
Mohanakrishnan S. · Examiné il y a presque 6 ans
Using the latest version of Kubernetes for GKE causes task 1 not be completd as it cannot create the hello world deployment object.
Arthur R. · Examiné il y a presque 6 ans
- The manifest to create the deployment didn't work because of the API version is used in it, v1beta1. Currently, 1.16 is the default version of GKE cluster, and therefore the manifest should be updated for apps/v1. - The cluster creation in the steps didn't work due to a quota limit related to the number of External IP addresses.
Shuji W. · Examiné il y a presque 6 ans
The hello-v2.yaml app has fails and cant be deployed. When i modify it to deploy cant check my progress.... REFER TO THIS ISSUE: https://github.com/GoogleCloudPlatform/training-data-analyst/issues/1250 I had to change the k8s cluster creation command to gcloud container clusters create $my_cluster \ --num-nodes 3 --enable-ip-alias --zone $my_zone \ --cluster-version "1.14.10-gke.50" --enable-stackdriver-kubernetes
Luis V. · Examiné il y a presque 6 ans
The hello-v2.yaml app has fails and cant be deployed. When i modify it to deploy cant check my progress.... REFER TO THIS ISSUE: https://github.com/GoogleCloudPlatform/training-data-analyst/issues/1250
Luis V. · Examiné il y a presque 6 ans
The first part appears broken.
Earl D. · Examiné il y a presque 6 ans
Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.