From ed5ae7c278dde0a65b6d9ffb8e2c612a2d9725f6 Mon Sep 17 00:00:00 2001
From: Andrew Azores <aazores@redhat.com>
Date: Thu, 6 Jun 2024 13:43:50 -0400
Subject: [PATCH] chore(release): set images to use 3.0 pre-release branch tags

---
 charts/cryostat/values.yaml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/charts/cryostat/values.yaml b/charts/cryostat/values.yaml
index 9efb1eb3..085f080c 100644
--- a/charts/cryostat/values.yaml
+++ b/charts/cryostat/values.yaml
@@ -87,7 +87,7 @@ db:
     ## @param db.image.pullPolicy Image pull policy for the database container image
     pullPolicy: Always
     ## @param db.image.tag Tag for the database container image
-    tag: "latest"
+    tag: "cryostat-v3.0"
   ## @param db.resources Resource requests/limits for the database container. See: [ResourceRequirements](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#resources)
   resources: {}
   ## @param db.securityContext [object] Security Context for the database container. Defaults to meet "restricted" [Pod Security Standard](https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted). See: [SecurityContext](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context-1)
@@ -108,7 +108,7 @@ storage:
     ## @param storage.image.pullPolicy Image pull policy for the storage container image
     pullPolicy: Always
     ## @param storage.image.tag Tag for the storage container image
-    tag: "latest"
+    tag: "cryostat-v3.0"
   ## @param storage.resources Resource requests/limits for the storage container. See: [ResourceRequirements](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#resources)
   resources: {}
   ## @param storage.securityContext [object] Security Context for the storage container. Defaults to meet "restricted" [Pod Security Standard](https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted). See: [SecurityContext](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context-1)
@@ -129,7 +129,7 @@ grafana:
     ## @param grafana.image.pullPolicy Image pull policy for the Grafana container image
     pullPolicy: Always
     ## @param grafana.image.tag Tag for the Grafana container image
-    tag: "latest"
+    tag: "3.0-dev"
   service:
     ## @param grafana.service.type Type of Service to create for Grafana
     type: ClusterIP
@@ -155,7 +155,7 @@ datasource:
     ## @param datasource.image.pullPolicy Image pull policy for the JFR Data Source container image
     pullPolicy: Always
     ## @param datasource.image.tag Tag for the JFR Data Source container image
-    tag: "latest"
+    tag: "3.0.0-snapshot"
   ## @param datasource.resources Resource requests/limits for the JFR Data Source container. See: [ResourceRequirements](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#resources)
   resources: {}
   ## @param datasource.securityContext [object] Security Context for the JFR Data Source container. Defaults to meet "restricted" [Pod Security Standard](https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted). See: [SecurityContext](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context-1)
@@ -208,11 +208,11 @@ oauth2Proxy:
 openshiftOauthProxy:
   image:
     ## @param openshiftOauthProxy.image.repository Repository for the OpenShift OAuth Proxy container image
-    repository: "quay.io/openshift/origin-oauth-proxy"
+    repository: "quay.io/cryostat/openshift-oauth-proxy"
     ## @param openshiftOauthProxy.image.pullPolicy Image pull policy for the OpenShift OAuth Proxy container image
     pullPolicy: Always
     ## @param openshiftOauthProxy.image.tag Tag for the OpenShift OAuth Proxy container image
-    tag: "latest"
+    tag: "cryostat-v3.0"
   accessReview:
     ## @param openshiftOauthProxy.accessReview.enabled Whether the SubjectAccessReview/TokenAccessReview role checks for users and clients are enabled. If this is disabled then the proxy will only check that the user has valid credentials or holds a valid token.
     enabled: true