Repository navigation
PMP Key Vault updates - #12079
PMP Key Vault updates#12079katarzyna-koltun-mx wants to merge 6 commits into
Conversation
| For environments which do not use `azure-wi` plans, the managed identity (UAMI) must be manually created by the customer before enabling Key Vault. Since the | ||
| * **Cluster** and **Namespace** - Select the cluster and namespace where you previously enabled secret store support. | ||
| * **Database Plan** and **Storage Plan** - Select an azure-wi database and/or storage plan. | ||
| * **Secrets** - Select the check box **Use external secret store for environment configurations**. |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Mendix.CompoundWords] Use 'checkbox' instead of 'check box'
| Private Mendix Platform automatically determines the correct path. When you enable the secret store for an environment, Private Mendix Platform checks whether a Kubernetes ServiceAccount already exists for that environment. | ||
| * **Cluster** and **Namespace** - Select the cluster and namespace where you previously enabled secret store support. | ||
| * **Database Plan** and **Storage Plan** - Select a database and/or storage plan without `azure-wi`. | ||
| * **Secrets** - Select the check box **Use external secret store for environment configurations**. |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Mendix.CompoundWords] Use 'checkbox' instead of 'check box'
Updated formatting for clarity in prerequisites section.
| 2. Switch to Admin Mode by clicking the profile picture in the top right corner of the screen and selecting **Switch to Admin Mode**. | ||
| 3. In the left navigation menu, open the **Manage** section and go to **Deployment > Cluster Manager**. | ||
| 4. Edit the target environment and toggle **Enable Secret Store**. | ||
| 5. Select **Manual** as the mode. Private Mendix Platform detects that no ServiceAccount exists yet, and prompts the user to provide a Client ID. |
There was a problem hiding this comment.
@katarzyna-koltun-mx what is the purpose of writing this section. Ideally we need to write that the customer while creating the new environment should enable secret store in env creation flow.
| #### Modifying the Operation Configuration | ||
|
|
||
| {{% alert color="info" %}} | ||
| The steps in this section are not necessary if .your Managed Identity was already created by Mendix Operator. |
There was a problem hiding this comment.
Can you fix this sentence
There was a problem hiding this comment.
@katarzyna-koltun-mx kinldy fix this line
he steps in this section are not necessary if .your Managed Identity was already created by Mendix Operator.
|
|
||
| 1. Update the configuration to [use the service token](/developerportal/deploy/private-cloud-cluster/#advanced-deployment-settings). | ||
|
|
||
| Set `runtimeAutomountServiceAccountToken: true` to allow Mendix app pods to get a Kubernetes Service Account token. |
There was a problem hiding this comment.
Did u checked with Shreyas for this option under Configuring Azure AD Workload Identity
No description provided.