Pre-release: v0.3.0-rc.1 (#362)

VSO 0.3.0 pre-release that brings in support for synchronizing HCP Vault
Secrets Apps.

CHANGELOG.md

@@ -1,4 +1,11 @@
 ## Unreleased
+## 0.3.0-rc.1 (September 19th, 2023)
+
+Improvements:
+* Add support for HCP Vault Secrets: [GH-315](https://github.com/hashicorp/vault-secrets-operator/pull/315)
+* Add new HCPVaultSecretsApp CRD and Controller: [GH-314](https://github.com/hashicorp/vault-secrets-operator/pull/314)
+* Add new HCPAuth CRD and Controller: [GH-313](https://github.com/hashicorp/vault-secrets-operator/pull/313)
+* Optionally revoke and purge all cached vault clients upon Operator deployment deletion: [GH-202](https://github.com/hashicorp/vault-secrets-operator/pull/202)
 
 ## 0.2.0 (August 16th, 2023)
 

chart/Chart.yaml

@@ -3,8 +3,8 @@
 
 apiVersion: v2
 name: vault-secrets-operator
-version: 0.2.0
-appVersion: "0.2.0"
+version: 0.3.0-rc.1
+appVersion: "0.3.0-rc.1"
 kubeVersion: ">=1.22.0-0"
 description: Official Vault Secrets Operator Chart
 type: application

chart/values.yaml

@@ -28,7 +28,6 @@ controller:
   #    effect: "NoSchedule"
   tolerations: []
 
-
   # Settings related to the kubeRbacProxy container. This container is an HTTP proxy for the
   # controller manager which performs RBAC authorization against the Kubernetes API using SubjectAccessReviews.
   kubeRbacProxy:
@@ -74,7 +73,7 @@ controller:
     # Image sets the repo and tag of the vault-secrets-operator image to use for the controller.
     image:
       repository: hashicorp/vault-secrets-operator
-      tag: 0.2.0
+      tag: 0.3.0-rc.1
 
     # Configures the client cache which is used by the controller to cache (and potentially persist) vault tokens that
     # are the result of using the VaultAuthMethod. This enables re-use of Vault Tokens

config/manager/kustomization.yaml

@@ -16,4 +16,4 @@ kind: Kustomization
 images:
 - name: controller
   newName: hashicorp/vault-secrets-operator
-  newTag: 0.2.0
+  newTag: 0.3.0-rc.1