Skip to content

PMP Key Vault updates - #12079

Open
katarzyna-koltun-mx wants to merge 6 commits into
developmentfrom
kk-pmp-keyvault-updates
Open

katarzyna-koltun-mx wants to merge 6 commits into
developmentfrom
kk-pmp-keyvault-updates

Conversation

@katarzyna-koltun-mx

Copy link
Copy Markdown
Collaborator

No description provided.

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**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [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**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Mendix.CompoundWords] Use 'checkbox' instead of 'check box'

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you fix this sentence

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did u checked with Shreyas for this option under Configuring Azure AD Workload Identity

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants