* Update go dependencies
Signed-off-by: Manuel de Brito Fontes <aledbf@gmail.com>
* Update runc to v1.1.5
* Update docker cli to v23.0.2+incompatible
---------
Signed-off-by: Manuel de Brito Fontes <aledbf@gmail.com>
* Add trust.cert-manager.io for to bundle CA certificates
Signed-off-by: Manuel de Brito Fontes <aledbf@gmail.com>
* Configure CA volume and volumemount in components
* Update ws-manager golden files
* Deploy trust manager in preview
* Remove duplicated volume
* Update installer golden files
* Generate a bundle only for registry-facade
* Update golden files
* Fix initcontainer volume mounts
* Update golden files
* Fix registry-facade certificate
* Update golden files
* Disable skip_verify
* Enable force conflict with apply server side
Signed-off-by: Manuel de Brito Fontes <aledbf@gmail.com>
* Avoid random werft namespace errors
Signed-off-by: Manuel de Brito Fontes <aledbf@gmail.com>
---------
Signed-off-by: Manuel de Brito Fontes <aledbf@gmail.com>
* Simplify image-builder-mk3 and registry-facade init containers
* Include new image-builder-mk3-wsman deployment
* Wait before updating node labels
* Ensure the loop runs more than once
* Switch registry-facade and ws-daemon from hostPort to nodePort
* Update golden files
* Update ports
* Remove old setting
* Remove $WS_DAEMON_PORT
* Switch to podIP
* Tune GCE VM
* Use withObservability flag
For some reason, the pod is killed with unknown container status and no taints on the underlying node.
Therefore, we skip extracting the failure from the terminated message.
Signed-off-by: JenTing Hsiao <hsiaoairplane@gmail.com>
Increase the metric workspace_starts_failure_total when the workspace stops and
the pod's annotation "gitpod/never-ready" exist. It means the workspace pod never
went into the running state, probably because
- the workspace pod can't allocate to the workspace node
- content initialization failure
- the workspace pod is never ready
Increase the metric workspace_stop_total when the workspace stops and
the pod's annotation "gitpod/never-ready" does not exist. So, the metric
workspace_stop_total does not increase on the start failure.
Signed-off-by: JenTing Hsiao <hsiaoairplane@gmail.com>
If dryRun enables on StartWorkspace/StopWorkspace/TakeSnapshot,
return gRPC FailedPrecondition status code and error message
`under maintenance mode`.
Signed-off-by: JenTing Hsiao <hsiaoairplane@gmail.com>