A native amd64
/arm64
utility container image for Helm and the Google Cloud SDK.
- Install Podman or Docker.
- In the commands below,
podman
may be interchanged withdocker
depending on your choice.
-
Check out one of the SLATE repositories with a Helm chart and change directories to its location on your machine.
-
Run the image and mount the present working directory. The container will present a series of prompts to be completed.
$ podman run -it -v ${PWD}:/work:Z ghcr.io/slateci/container-helm-gcloudsdk:latest Go to the following link in your browser: https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=XXXX&...&code_challenge_method=S256 Enter authorization code: <input> ... ... Fetching cluster endpoint and auth data. kubeconfig entry generated for <cluster name>.
-
Verify your configuration by getting the pods in the
development
namespace.[root@454344d8c4ca work]# kubectl get pods --namespace development W1010 18:37:49.154648 133 gcp.go:119] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.26+; use gcloud instead. To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke NAME READY STATUS RESTARTS AGE slate-api-dev-deployment-5d87f5ddf4-wc2pg 1/1 Running 0 2d23h slate-portal-dev-deployment-6d7874944d-8gl8c 1/1 Running 0 2d21h ... ...
-
Try decrypting a secrets file to stdout.
[root@454344d8c4ca work]# cd resources/chart/vars/dev/ [root@454344d8c4ca dev]# helm secrets decrypt secrets.yml
-
Try other commands described in the internal documentation
- Submit a pull request against
master
. - Once the automated status checks pass, complete the pull request by squash-merging with
master
. - Apply a semantic version tag to the resulting commit (e.g.
v1.0.1
). - At this point the automatic image build on GitHub will trigger, tagging the new image with the semantic version and
latest
.
See Helm Commands.