Utiliser le contrôle des accès basé sur les rôles dans Kubernetes Engine avis
Chargement...
Aucun résultat.

    Utiliser le contrôle des accès basé sur les rôles dans Kubernetes Engine avis

    13692 avis

    Nikhil Francis P. · Examiné il y a environ 2 mois

    Terry C. · Examiné il y a environ 2 mois

    The lab worked fine in the second attempt

    Bikram S. · Examiné il y a environ 2 mois

    The lab does not work. I see it was last tested more than a year ago. Here are the error details on issuing the "make create" command to create the kubernetes cluster: Warning: Deprecated Resource │ │ with module.auditor_instance.data.null_data_source.grant_admin, │ on modules/instance/main.tf line 19, in data "null_data_source" "grant_admin": │ 19: data "null_data_source" "grant_admin" { │ │ The null_data_source was historically used to construct intermediate values to re-use elsewhere in configuration, the same can now be achieved using locals │ │ (and 5 more similar warnings elsewhere) ╵ ╷ │ Error: Error creating service account: googleapi: Error 409: Service account gke-tutorial-admin-rbac already exists within project projects/qwiklabs-gcp-03-78ecbdbcc271. │ Details: │ [ │ { │ "@type": "type.googleapis.com/google.rpc.ResourceInfo", │ "resourceName": "projects/qwiklabs-gcp-03-78ecbdbcc271/serviceAccounts/gke-tutorial-admin-rbac@qwiklabs-gcp-03-78ecbdbcc271.iam.gserviceaccount.com" │ } │ ] │ , alreadyExists │ │ with google_service_account.admin, │ on iam.tf line 59, in resource "google_service_account" "admin": │ 59: resource "google_service_account" "admin" { │ ╵ make: *** [Makefile:27: create] Error 1

    Bikram S. · Examiné il y a environ 2 mois

    QUE VERGUENZA DE LABORATORIO!!!!!! aboratio "Using role-based access control in the Kubernetes engine". Error in ckeck : "Create a server in each namespace". It is done, but it does not recognize it, this and in the English version, it is the 3rd time it fails me, I request a solution. reported to technician by chat, they will check -------------- fallo en failure when trying the make create, it doesn't even get to the minute of execution and fails

    Javier B. · Examiné il y a environ 2 mois

    QUE VERGUENZA DE LABORATORIO!!!!!! aboratio "Using role-based access control in the Kubernetes engine". Error in ckeck : "Create a server in each namespace". It is done, but it does not recognize it, this and in the English version, it is the 3rd time it fails me, I request a solution. reported to technician by chat, they will check -------------- fallo en failure when trying the make create, it doesn't even get to the minute of execution and fails

    Javier B. · Examiné il y a environ 2 mois

    laboratio "Using role-based access control in the Kubernetes engine". Error in ckeck : "Create a server in each namespace". It is done, but it does not recognize it, this and in the English version, it is the 3rd time it fails me, I request a solution. reported to technician by chat, they will check -------------- fallo en failure when trying the make create, it doesn't even get to the minute of execution and fails

    Javier B. · Examiné il y a environ 2 mois

    Jaimin T. · Examiné il y a environ 2 mois

    ANTONIO M. · Examiné il y a environ 2 mois

    Samuel T. · Examiné il y a environ 2 mois

    Lizbeth Berenice M. · Examiné il y a environ 2 mois

    Vaibhav S. · Examiné il y a environ 2 mois

    Lizbeth Berenice M. · Examiné il y a environ 2 mois

    Lab is bugged, namespace section will not show completed despite later steps in the lab working as intended

    Daniel K. · Examiné il y a environ 2 mois

    laboratio "Using role-based access control in the Kubernetes engine". Error in ckeck : "Create a server in each namespace". It is done, but it does not recognize it, this and in the English version, it is the 3rd time it fails me, I request a solution. reported to technician by chat, they will check -------------- fallo en failure when trying the make create, it doesn't even get to the minute of execution and fails

    Javier B. · Examiné il y a environ 2 mois

    Anil S. · Examiné il y a environ 2 mois

    Monika K. · Examiné il y a environ 2 mois

    Trisha C. · Examiné il y a environ 2 mois

    Unable to finish task 1, terraform script failed

    Jieqing O. · Examiné il y a environ 2 mois

    Unable to finish task 1, terraform script failed

    Jieqing O. · Examiné il y a environ 2 mois

    Amruth P. · Examiné il y a environ 2 mois

    Pablo S. · Examiné il y a environ 2 mois

    laboratio "Using role-based access control in the Kubernetes engine". Error in ckeck : "Create a server in each namespace". It is done, but it does not recognize it, this and in the English version, it is the 3rd time it fails me, I request a solution. reported to technician by chat, they will check -------------- fallo en failure when trying the make create, it doesn't even get to the minute of execution and fails.

    Javier B. · Examiné il y a environ 2 mois

    good

    VeeraVenkata N. · Examiné il y a environ 2 mois

    Error in make command module.auditor_instance.google_compute_instance.instance: Creation complete after 50s [id=projects/qwiklabs-gcp-04-78e147b36c8e/zones/us-west1-a/instances/gke-tutorial-auditor] ╷ │ Warning: Deprecated Resource │ │ with module.bastion.data.null_data_source.grant_admin, │ on modules/instance/main.tf line 19, in data "null_data_source" "grant_admin": │ 19: data "null_data_source" "grant_admin" { │ │ The null_data_source was historically used to construct intermediate values to re-use elsewhere in configuration, the same can now be achieved using locals │ │ (and 5 more similar warnings elsewhere) ╵ ╷ │ Error: Provider produced inconsistent result after apply │ │ When applying changes to google_service_account.admin, provider "provider[\"registry.terraform.io/hashicorp/google\"]" produced an unexpected new value: Root resource was present, but now absent. │ │ This is a bug in the provider, which should be reported in the provider's own issue tracker. ╵ make: *** [Makefile:27: create] Error 1

    YANNICK D. · Examiné il y a environ 2 mois

    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.