From 333b0821d8a8b17ced3c95612a117794a34d2f4e Mon Sep 17 00:00:00 2001 From: Anish Ramasekar Date: Tue, 20 Dec 2022 12:00:36 -0800 Subject: [PATCH] release: bump version to v0.4.0 (#194) Signed-off-by: Anish Ramasekar --- Makefile | 4 ++-- docs/manual-install.md | 10 +++++----- docs/rotation.md | 2 +- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/Makefile b/Makefile index 7ed214e4..dbaed817 100644 --- a/Makefile +++ b/Makefile @@ -8,7 +8,7 @@ REGISTRY ?= $(REGISTRY_NAME).azurecr.io/$(REPO_PREFIX) LOCAL_REGISTRY_NAME ?= kind-registry LOCAL_REGISTRY_PORT ?= 5000 IMAGE_NAME ?= keyvault -IMAGE_VERSION ?= v0.3.0 +IMAGE_VERSION ?= v0.4.0 IMAGE_TAG := $(REGISTRY)/$(IMAGE_NAME):$(IMAGE_VERSION) CGO_ENABLED_FLAG := 0 @@ -79,7 +79,7 @@ docker-build: --output=$(OUTPUT_TYPE) \ -t $(REGISTRY)/$(IMAGE_NAME):$(IMAGE_VERSION)-linux-$(ARCH) . \ --progress=plain; \ - + @if [ "$(ARCH)" = "amd64" ] && [ "$(OUTPUT_TYPE)" = "type=docker" ]; then \ docker tag $(REGISTRY)/$(IMAGE_NAME):$(IMAGE_VERSION)-linux-$(ARCH) $(REGISTRY)/$(IMAGE_NAME):$(IMAGE_VERSION); \ fi diff --git a/docs/manual-install.md b/docs/manual-install.md index a615f244..3ad27658 100644 --- a/docs/manual-install.md +++ b/docs/manual-install.md @@ -37,10 +37,10 @@ This guide demonstrates steps required to enable the KMS Plugin for Key Vault in After your cluster is provisioned, depending on your cluster identity configuration, run one of the following commands to retrieve the **ID** of your managed identity or service principal, which will be used for role assignment to access Keyvault: - | Cluster configuration | Command | - | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | AKS cluster with service principal | `az aks show -g -n --query servicePrincipalProfile.clientId -otsv` | - | AKS cluster with managed identity | `az aks show -g -n --query identityProfile.kubeletidentity.clientId -otsv` | + | Cluster configuration | Command | + | ---------------------------------- | -------------------------------------------------------------------------------------------------------------- | + | AKS cluster with service principal | `az aks show -g -n --query servicePrincipalProfile.clientId -otsv` | + | AKS cluster with managed identity | `az aks show -g -n --query identityProfile.kubeletidentity.clientId -otsv` | Assign the following permissions: @@ -66,7 +66,7 @@ This guide demonstrates steps required to enable the KMS Plugin for Key Vault in hostNetwork: true containers: - name: azure-kms-provider - image: mcr.microsoft.com/oss/azure/kms/keyvault:v0.3.0 + image: mcr.microsoft.com/oss/azure/kms/keyvault:v0.4.0 imagePullPolicy: IfNotPresent args: - --listen-addr=unix:///opt/azurekms.socket # [OPTIONAL] gRPC listen address. Default is unix:///opt/azurekms.socket diff --git a/docs/rotation.md b/docs/rotation.md index 5fd39522..10fb9ad1 100644 --- a/docs/rotation.md +++ b/docs/rotation.md @@ -29,7 +29,7 @@ spec: hostNetwork: true containers: - name: azure-kms-provider - image: mcr.microsoft.com/oss/azure/kms/keyvault:v0.3.0 + image: mcr.microsoft.com/oss/azure/kms/keyvault:v0.4.0 imagePullPolicy: IfNotPresent args: - --listen-addr=unix:///opt/azurekms2.socket # unix:///opt/azurekms.socket is used by the primary kms plugin pod. So use a different listen address here for the new kms plugin pod.