关于“构建 Docker 映像并将其部署到 Kubernetes 集群:实验室挑战赛”的评价
30672 条评价
Aditya N. · 已于 5 months前审核
Mir Saheed M. · 已于 5 months前审核
Haydar Dzaky B. · 已于 5 months前审核
Sumanta M. · 已于 5 months前审核
Jayesh J. · 已于 5 months前审核
Deepti T. · 已于 5 months前审核
Animesh G. · 已于 5 months前审核
Rahul K. · 已于 5 months前审核
i'm having problems for the last 2 task... i've changed the name of the deployment yaml in echo-web and when i try ( kubectl apply -f the deploymentname.yaml) it returns this error: error: resource mapping not found for name: "echo-web" namespace: "" from "echoweb-deployment.yaml": no matches for kind "Deployment" in version "apps/v1beta" ensure CRDs are installed first
Ilia B. · 已于 5 months前审核
Soumyadip M. · 已于 5 months前审核
Taiwo O. · 已于 5 months前审核
Jukka N. · 已于 5 months前审核
Rofiat O. · 已于 5 months前审核
Zaid A. · 已于 5 months前审核
Aymen R. · 已于 5 months前审核
The kubernetes cluster GUI tries to create the cluster using autopilot which doesn't allow changing things like the number of nodes in the node pool or the machine type. The docker repo naming is confusing challenge ask to use gcr but does not state exactly how to form the repo URL and the artifact registry uses a different URL. found on stack overflow that the repo url using GCR is gcr.io/<project-id>/echo-app:v1 artifact registry tells to use this URL us-east4-docker.pkg.dev/<project-id>/<repo-name>/echo-app:v1 pushing to this repo makes the challenge check fail. Deployment files is broken, it does not state to change the image to the one just pushed, spec.selector.matchingLabels API version is beta when it should be v1. The service yaml file mentions a load balancer static IP but that IP is never mentioned on the challenge and the assesment will be completed even if the IP is generated dynamically by GCP.
Salvatore F. · 已于 5 months前审核
Kashif J. · 已于 5 months前审核
Laxmi D. · 已于 5 months前审核
Federico S. · 已于 5 months前审核
Aishwarya A. · 已于 5 months前审核
Abiodun I. · 已于 5 months前审核
Chris H. · 已于 5 months前审核
Pranesha K. · 已于 5 months前审核
Darren M. · 已于 5 months前审核
Reetesh C. · 已于 5 months前审核
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。