From e4e492df3876a349fe2b34eebf656226cde7936c Mon Sep 17 00:00:00 2001 From: Tom Proctor Date: Mon, 20 Mar 2023 16:44:56 +0000 Subject: [PATCH] Fix changelog for #163 to be unreleased --- CHANGELOG.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index bde63c0..3a2f0a7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,13 @@ ## Unreleased +* Vault CSI Provider will use service account tokens passed from the Secrets Store CSI Driver instead of generating one if an appropriate token is provided. [[GH-163](https://github.com/hashicorp/vault-csi-provider/pull/163)] + * The Secrets Store CSI driver needs to be configured to generate tokens with the correct audience for this feature. Vault CSI Provider + will look for a token with the audience specified in the SecretProviderClass, or otherwise "vault". To configure the driver to generate + a token with the correct audience, use the + [`tokenRequests`](https://github.com/kubernetes-sigs/secrets-store-csi-driver/tree/main/charts/secrets-store-csi-driver#configuration) + option from the _driver_ helm chart via the flag `--set tokenRequests[0].audience="vault"`. See + [CSI TokenRequests documentation](https://kubernetes-csi.github.io/docs/token-requests.html) for further details. + ## 1.2.1 (November 21st, 2022) CHANGES: @@ -23,13 +31,6 @@ CHANGES: CHANGES: * Duplicate object names now trigger an error instead of silently overwriting files. [[GH-148](https://github.com/hashicorp/vault-csi-provider/pull/148)] -* Vault CSI Provider will use service account tokens passed from the Secrets Store CSI Driver instead of generating one if an appropriate token is provided. [[GH-163](https://github.com/hashicorp/vault-csi-provider/pull/163)] - * The Secrets Store CSI driver needs to be configured to generate tokens with the correct audience for this feature. Vault CSI Provider - will look for a token with the audience specified in the SecretProviderClass, or otherwise "vault". To configure the driver to generate - a token with the correct audience, use the - [`tokenRequests`](https://github.com/kubernetes-sigs/secrets-store-csi-driver/tree/main/charts/secrets-store-csi-driver#configuration) - option from the _driver_ helm chart via the flag `--set tokenRequests[0].audience="vault"`. See - [CSI TokenRequests documentation](https://kubernetes-csi.github.io/docs/token-requests.html) for further details. BUGS: