Post-Release Helm/Kubectl Deployment Instructions

[alehechka]

So far, the deployment process is entirely automated for all environments and has continued to be successful. Currently, when a tagged release is created, the Helm chart will be templated and packaged the resulting files will be uploaded to the release as assets. However, there are no deployment instructions, so these files essentially become useless without intimate knowledge of helm or kubectl to run them.

This issue proposes that along with the prepared file asset uploads, the release descriptions also get automatically updated with appended deployment instructions that are tailored directly to that release in question so commands can easily be copied/pasted to deploy the application.

The below comments will be the proposed descriptions for these deployment instructions.

[alehechka]

Manual Deployment Instructions (for deployment from centralized Helm chart)

Below commands assume the following:

• gh is installed and authenticated with GitHub.
• kubectl is installed and authenticated with the proper cluster.
  • Run kubectl config get-contexts to check which cluster is authenticated.
• If using helm, helm is installed and authenticated with ghcr.io.

helm

gh release download v0.5.0 \
	--repo lockerstock/organizations-api \
	-p values.yaml

helm upgrade --install organizations-api oci://ghcr.io/lockerstock/helm-charts/microservice 
	--version v0.1.0 \
	-f values.yaml \
	--namespace production

kubectl

gh release download v0.5.0 \
	--repo lockerstock/organizations-api \
	-p lockerstock-landing.yaml

kubectl apply \
	-f lockerstock-landing.yaml \
	--namespace production

[alehechka]

Deployment Instructions

Download the values.yaml file to your local machine in the current working directory of your terminal.

Upgrade/install Helm chart

helm upgrade --install organizations-api lockerstock/microservice
	--version v0.1.0 \
	-f values.yaml \
	--namespace production