From f17801753dd1b2a9cb6edcce114e9ad5d8741e03 Mon Sep 17 00:00:00 2001 From: Kingdon Barrett <kingdon@weave.works> Date: Sun, 21 Mar 2021 13:50:23 -0400 Subject: [PATCH] Fixup a broken reference and a typo in Azure doc Signed-off-by: Kingdon Barrett <kingdon@weave.works> --- docs/guides/mozilla-sops.md | 2 +- docs/use-cases/azure.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/mozilla-sops.md b/docs/guides/mozilla-sops.md index 49e23556..6877b7d8 100644 --- a/docs/guides/mozilla-sops.md +++ b/docs/guides/mozilla-sops.md @@ -240,7 +240,7 @@ kubectl -n flux-system rollout restart deployment/kustomize-controller #### Azure -When using Azure Key Vault you need to authenticate kustomize-controller either with [add-pod-identity](../use-cases/azure.md#aad-pod-identity) +When using Azure Key Vault you need to authenticate kustomize-controller either with [aad-pod-identity](../use-cases/azure.md#aad-pod-identity) or by passing [Service Principal credentials as environment variables](https://github.com/mozilla/sops#encrypting-using-azure-key-vault). Create the Azure Key-Vault: diff --git a/docs/use-cases/azure.md b/docs/use-cases/azure.md index b1791102..9f08b6b5 100644 --- a/docs/use-cases/azure.md +++ b/docs/use-cases/azure.md @@ -91,7 +91,7 @@ If you want to use Managed Identities, install or enable [AAD Pod Identity](#aad Patch kustomize-controller with the proper Azure credentials, so that it may access your Azure Key Vault, and then begin committing SOPS encrypted files to the Git repository with the proper Azure Key Vault configuration. -See the [Mozilla SOPS Azure Guide](../guides/azure.md) for further detail. +See the [Mozilla SOPS Azure Guide](../../guides/mozilla-sops/#azure) for further detail. ## Image Updates with Azure Container Registry -- GitLab