Implementar fluxos de trabalho de DevOps no Google Cloud: laboratório com desafio avaliações

Maksym V. · Revisado há over 1 year

Muskan k. · Revisado há over 1 year

disgusting

Siddharth B. · Revisado há over 1 year

Muhammad Saifullah N. · Revisado há over 1 year

Roshani M. · Revisado há over 1 year

Muhammad Saifullah N. · Revisado há over 1 year

Dadu P. · Revisado há over 1 year

Andi A. · Revisado há over 1 year

Sathyahan M. · Revisado há over 1 year

Antonio F. · Revisado há over 1 year

Muskan K. · Revisado há over 1 year

Mohamed Amine B. · Revisado há over 1 year

disgusting

Siddharth B. · Revisado há over 1 year

For the people that might read this comment. Don't do anything until the cluster is created, later maybe you could not get the approval of the task, it happened to me. The other problem is with cloud build: before creation of triggers, go to Settings and select the numberofproject-compute@dev.... as service account account and give it permissions for Kubernetes at least (I gave it some more), because the default cloud build account doesn't work and you won't be able to complete the lab. Mark this account as the default too. Later, in the cloudbuild.yaml and cloudbuild-dev.yaml add this at the end: options: logging: CLOUD_LOGGING_ONLY With all of this, you can create the triggers and the builds will work.

Pedro Jose S. · Revisado há over 1 year

Muskan K. · Revisado há over 1 year

Muskan K. · Revisado há over 1 year

Pedro Jose S. · Revisado há over 1 year

Siddharth B. · Revisado há over 1 year

Siddharth B. · Revisado há over 1 year

Costas C. · Revisado há over 1 year

Mohammad A. · Revisado há over 1 year