1- # [ Unified Openshift Deployment Process ] ( https://docs.google.com/presentation/d/1MlLuuawzxJg6U15zbPby6JAtNNEWZAhfGEWNcpYSWeo )
1+ # Helm Charts
22
3- for the [ Packit Service Validation] ( https://github.com/packit/deployment/tree/main/cron-jobs/packit-service-validation ) .
3+ for
4+ * [ Packit Service Validation cron job] ( https://github.com/packit/deployment/tree/main/cron-jobs/packit-service-validation )
5+ * [ Import-images cron job] ( https://github.com/packit/deployment/tree/main/cron-jobs/import-images )
46
5- To deploy the * Packit Service Validation * through * Helm * follow this steps:
7+ ## Deployment
68
7- ### Setup deployment
9+ All charts are deployed automatically via GitHub/Gitlab CI/CI.
810
9- Helm uses an ** image** created through a GitHub action and pushed to Quay.io,
10- the ** tag** for this image is the first * 7 digit for the commit SHA* of the packit/deployment repo.
11+ For instructions how to do it manually, see
12+ * [ packit-service-validation/README.md] ( values/packit-service-validation/README.md )
13+ * [ import-images/README.md] ( values/import-images/README.md )
1114
12- To use a new image update the referenced tag
13- [ here] ( https://github.com/packit/udp/blob/main/ocp-deployments/packit-service-validation-prod.yaml#L18 ) .
15+ ## Releases
1416
15- ### Install Helm Chart
16-
17- Login to OpenShift cluster and switch to proper project. In case of packit-service validation
18- it's ` cyborg ` project @ [ PSI Cluster] ( https://ocp4.psi.redhat.com ) .
19-
20- oc login --token=sha256~.... --server= ....
21- oc project cyborg
22-
23- Get secrets from Bitwarden.
24- Sentry from ` extra-vars.yml ` in ` secrets-packit-[prod|stg] ` item and
25- GitHub token from ` Release/usercont bot ` item.
26-
27- export SENTRY=$( echo -n 'token from bitwarden' | base64 )
28- export GITHUB=$( echo -n 'token from bitwarden' | base64 )
29-
30- #### Install from this repo
31-
32- make packit-service-validation-install DEPLOYMENT=[production|staging]
33-
34- #### Install from chart repository
35-
36- If you're going to use the chart from outside (without having this repo cloned),
37- you can install the chart from our chart repository. You just need to have a file
38- with keys overriding those defined in ` values.yaml ` with ` ~ ` value.
39-
40- helm repo add packit https://helm.packit.dev
41- helm repo update
42- helm upgrade --install --cleanup-on-fail packit-service-validation packit/packit-service-validation --set secrets.sentry=${SENTRY} --set secrets.github=${GITHUB} --values your-values-file.yaml
43-
44- ### Render templates
45-
46- If you just want to see how the rendered templates would look like:
47-
48- make packit-service-validation-dryrun DEPLOYMENT=[production|staging]
49-
50- ### Releases
5117There's a [ release workflow] ( https://github.com/packit/udp/blob/main/.github/workflows/release.yml )
5218to automate releasing the Helm charts. It uses
5319[ Helm Chart Releaser Action] ( https://github.com/marketplace/actions/helm-chart-releaser )
@@ -57,3 +23,8 @@ and whenever there's a new chart version, creates a corresponding GitHub release
5723named for the chart version, adds Helm chart artifacts to the release,
5824and creates or updates an ` index.yaml ` file with metadata about those releases,
5925which is then hosted on GitHub Pages at [ helm.packit.dev] ( https://helm.packit.dev ) .
26+
27+ ## [ Unified Openshift Deployment Process] ( https://docs.google.com/presentation/d/1MlLuuawzxJg6U15zbPby6JAtNNEWZAhfGEWNcpYSWeo )
28+
29+ We use images created by a GitHub workflow and pushed to Quay.io,
30+ the ** tag** for an image is the first * 7 digit for the commit SHA* .
0 commit comments