From 1a3551b139c4c2fe9a8361156be6c2eb3a4a779c Mon Sep 17 00:00:00 2001 From: Bruce MacDonald Date: Fri, 13 Aug 2021 11:24:47 -0700 Subject: [PATCH] Add note that Okta secrets should be deployed in the same namespace --- docs/okta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/okta.md b/docs/okta.md index 1d082253af..606b966e15 100644 --- a/docs/okta.md +++ b/docs/okta.md @@ -49,7 +49,7 @@ sources: ![okta_api_token](https://user-images.githubusercontent.com/5853428/124652864-787b5d00-de51-11eb-81d8-e503babfdbca.png) ### Add Okta secrets to the Infra registry deployment -The Okta client secret and API token are sensitive information which cannot be stored in the Infra configuration file. In order for Infra to access these secret values they must be stored in Kubernetes Secret objects. +The Okta client secret and API token are sensitive information which cannot be stored in the Infra configuration file. In order for Infra to access these secret values they must be stored in Kubernetes Secret objects **in the same namespace that the Infra registry is deployed in**. Create [Kubernetes Secret objects](https://kubernetes.io/docs/tasks/configmap-secret/) to store the Okta client secret and API token (noted in steps 4 and 5 of `Create an Okta App` respectively). You can name these Secrets as you desire, these names will be specified in the Infra configuration.