Pipeline Google Kubernetes Engine menggunakan Cloud Build Ulasan

Yuvi

Yuvraj T. · Diulas 6 hari lalu

Gunika A. · Diulas 6 hari lalu

creative t. · Diulas 6 hari lalu

Gurinder S. · Diulas 6 hari lalu

Sridhara R. · Diulas 6 hari lalu

Lakshit J. · Diulas 7 hari lalu

Bintang F. · Diulas 7 hari lalu

Archana S. · Diulas 7 hari lalu

Krishna Kumar S. · Diulas 7 hari lalu

Riswana A. · Diulas 7 hari lalu

I got the error when running the build: Your build failed to run: generic::invalid_argument: if 'build.service_account' is specified, the build must either (a) specify 'build.logs_bucket', (b) use the REGIONAL_USER_OWNED_BUCKET build.options.default_logs_bucket_behavior option, or (c) use either CLOUD_LOGGING_ONLY / NONE logging options And the fix is: straight under the steps, in cloudbuild.yaml options: logging: CLOUD_LOGGING_ONLY Please add it to the lab. Thanks.

Quan T. · Diulas 7 hari lalu

Nadia A. · Diulas 7 hari lalu

557-bharadwaj V. · Diulas 8 hari lalu

Lin L. · Diulas 8 hari lalu

28.06.2024 Scored 100 however, the build triggers did not succeed, need to do again,. 23.05.2024 The Kubernetes cluster did not get created in US-West1 region even after one hour.

Kanhaiya S. · Diulas 8 hari lalu

Yuki T. · Diulas 8 hari lalu

HARRISON B. · Diulas 9 hari lalu

Broken lab. Please include instructions for service account selection in Task 4.

Andrew S. · Diulas 9 hari lalu

Sairupesh G. · Diulas 9 hari lalu

khushi n. · Diulas 9 hari lalu

To get past the trigger errors select the service account and add "options:\n logging: CLOUD_LOGGING_ONLY" to every cloudbuild yaml file and commit and push them to the repos

Sean D. · Diulas 9 hari lalu

Animesh P. · Diulas 9 hari lalu

Siva S. · Diulas 9 hari lalu

Gines G. · Diulas 9 hari lalu

Deepesh W. · Diulas 9 hari lalu