Using Role-based Access Control in Kubernetes Engine Ulasan

debian-9 missing

iONUT D. · Diulas sekitar 4 tahun lalu

terraform/modules/instance/main.tf で image = "debian-cloud/debian-9" となっており、 debian-9 を参照しています。

Takanori S. · Diulas sekitar 4 tahun lalu

REEJAL C. · Diulas sekitar 4 tahun lalu

SANI M. · Diulas sekitar 4 tahun lalu

The first "make create" step failed with the following error message: │ Error: Error resolving image name 'debian-cloud/debian-9': Could not find image or family debian-cloud/debian-9 │ │ with module.bastion.google_compute_instance.instance, │ on modules/instance/main.tf line 66, in resource "google_compute_instance" "instance": │ 66: resource "google_compute_instance" "instance" {

Maggie T. · Diulas sekitar 4 tahun lalu

Jonatas C. · Diulas sekitar 4 tahun lalu

Dipak B. · Diulas sekitar 4 tahun lalu

Andrii B. · Diulas sekitar 4 tahun lalu

Vineet S. · Diulas sekitar 4 tahun lalu

Roshan M. · Diulas sekitar 4 tahun lalu

failed to provision kubernetes engine cluster

Duy N. · Diulas sekitar 4 tahun lalu

Debian version in "instance" module needs to be updated. Also, teardown process spent too much time, because of that I couldn't get 100 points.

Andika B. · Diulas sekitar 4 tahun lalu

Chethan K. · Diulas sekitar 4 tahun lalu

Cláudia P. · Diulas sekitar 4 tahun lalu

Maximiliano P. · Diulas sekitar 4 tahun lalu

Maximiliano P. · Diulas sekitar 4 tahun lalu

Needed to fix the terraform sources (to change unsupported debian-9 image): ./terraform/modules/instance/main.tf:76:image = "debian-cloud/debian-9"

Jan F. · Diulas sekitar 4 tahun lalu

Please update the main.tf file regarding the debian's version

Muhammad F. · Diulas sekitar 4 tahun lalu

you need to change your terraform code(instance image - current : debian-cloud/debian-9)

Kyuhwan C. · Diulas sekitar 4 tahun lalu

Demo contains out of date elements. Other than that it was a pretty in depth tutorial

Shane F. · Diulas sekitar 4 tahun lalu

This lab contains error and could not performed.

LEONID C. · Diulas sekitar 4 tahun lalu

Awaiting teardown before allocating 100/100 completion marks wasn't fair.... It took several minutes (Fortunately i had enough to spare). It also failed first run, but then completed successfully second attempt.

Jamie T. · Diulas sekitar 4 tahun lalu

Again same issue with this LAB as well as with previous 2, kindly check your script on main.tf folder or check your resource folder "google_compute_instance", this is the one that causing issues in all LABs of this module of LAB Quest. Error: Error resolving image name 'debian-cloud/debian-9': Could not find image or family debian-cloud/debian-9 │ │ with module.owner_instance.google_compute_instance.instance, │ on modules/instance/main.tf line 66, in resource "google_compute_instance" "instance": │ 66: resource "google_compute_instance" "instance" { │ ╵ ╷ │ Error: Error resolving image name 'debian-cloud/debian-9': Could not find image or family debian-cloud/debian-9 │ │ with module.bastion.google_compute_instance.instance, │ on modules/instance/main.tf line 66, in resource "google_compute_instance" "instance": │ 66: resource "google_compute_instance" "instance" { │ ╵ ╷ │ Error: Error resolving image name 'debian-cloud/debian-9': Could not find image or family debian-cloud/debian-9 │ │ with module.auditor_instance.google_compute_instance.instance, │ on modules/instance/main.tf line 66, in resource "google_compute_instance" "instance": │ 66: resource "google_compute_instance" "instance" {

Vivek W. · Diulas sekitar 4 tahun lalu

Godfrey M. · Diulas sekitar 4 tahun lalu

make create command errors out

Jim W. · Diulas sekitar 4 tahun lalu