diff --git a/content/en/docs/private-platform/secret-management/pmp-key-vault-integration.md b/content/en/docs/private-platform/secret-management/pmp-key-vault-integration.md index 5ff9f28fe90..29e617d0c57 100644 --- a/content/en/docs/private-platform/secret-management/pmp-key-vault-integration.md +++ b/content/en/docs/private-platform/secret-management/pmp-key-vault-integration.md @@ -59,6 +59,47 @@ Verify the configuration by using the following command: kubectl auth can-i create secretproviderclasses --as=system:serviceaccount:kube-system:mxplatform-cicd -n ``` +#### Example Manifest + +The following manifest is an example showing how to create roles and role bindings for each namespace where you wish to deploy apps using the automatic Key Vault feature. + +{{% alert color="warning" %}} +The examples are intended to show the range of available options. No rights can be derived from them, as they are presented as examples only, and may require significant adaptation to work in your own environment. It is your responsibility to interpret and adjust them to fit real-world scenarios. +{{% /alert %}} + +```text +Key Vault permissions for app namespace ns-apps-1 (Role + RoleBinding pointing to mxplatform-cicd SA) +NS=ns-apps-1 +kubectl apply -f - <