release: bump version to v0.2.0 (#120)

Signed-off-by: Anish Ramasekar <anish.ramasekar@gmail.com>

Author: aramase

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.1.0
+IMAGE_VERSION ?= v0.2.0
 IMAGE_TAG := $(REGISTRY)/$(IMAGE_NAME):$(IMAGE_VERSION)
 CGO_ENABLED_FLAG := 0
 

docs/manual-install.md

@@ -69,7 +69,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.1.0
+        image: mcr.microsoft.com/oss/azure/kms/keyvault:v0.2.0
         imagePullPolicy: IfNotPresent
         args:
           - --listen-addr=unix:///opt/azurekms.socket             # [OPTIONAL] gRPC listen address. Default is unix:///opt/azurekms.socket

docs/rotation.md

@@ -29,7 +29,7 @@ spec:
   hostNetwork: true
   containers:
     - name: azure-kms-provider
-      image: mcr.microsoft.com/oss/azure/kms/keyvault:v0.1.0
+      image: mcr.microsoft.com/oss/azure/kms/keyvault:v0.2.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.