Deployment to Kubernetes
You may trigger staging release at any point of time from the
master
branch by:cd podkrepi.bg/frontend
kubectl apply -k manifests/overlays/development
This will update the deployment using
ghcr.io/podkrepi-bg/frontend:master
imageThe following command will:
- Bump the version in
package.json
- Tag the
latest
master branch - [
postversion
] Push local tags to the remote origin - Update the image
newTag
version infrontend/manifests/overlays/production/kustomization.yaml
- Commit and push the manifest update
cd podkrepi.bg/frontend
kubectl apply -k manifests/overlays/production
Once the image has been built by the GitHub Actions and is present in the Docker image repository you may trigger the actual deployment to the cluster.
cd podkrepi.bg/frontend
kubectl apply -k manifests/overlays/production
You may trigger staging release at any point of time from the
master
branch by:cd podkrepi.bg/backend
kubectl apply -k manifests/overlays/development
This will update the deployment using
ghcr.io/podkrepi-bg/api:master
imageThe following command will:
- Bump the version in
package.json
- Tag the
latest
master branch - [
postversion
] Push local tags to the remote origin - Update the image
newTag
version inbackend/manifests/overlays/production/kustomization.yaml
- Commit and push the manifest update
cd podkrepi.bg/backend
kubectl apply -k manifests/overlays/production
Once the image has been built by the GitHub Actions and is present in the Docker image repository you may trigger the actual deployment to the cluster.
cd podkrepi.bg/backend
kubectl apply -k manifests/overlays/production
If you want to set a specific version for the deployment image you can do that by editing
backend/manifests/overlays/production/kustomization.yaml
images:
- name: ghcr.io/podkrepi-bg/api/migrations
newTag: v0.3.3
- name: ghcr.io/podkrepi-bg/api
newTag: v0.3.3
Last modified 1yr ago