|
@@ -4,7 +4,11 @@ External Secrets Operator integrates with [IBM Secret Manager](https://www.ibm.c
|
|
|
|
|
|
|
|
### Authentication
|
|
### Authentication
|
|
|
|
|
|
|
|
-At the moment, we only support API key authentication for this provider. To generate your key (for test purposes we are going to generate from your user), first got to your (Access IAM) page:
|
|
|
|
|
|
|
+We support API key and trusted profile container authentication for this provider.
|
|
|
|
|
+
|
|
|
|
|
+#### API key secret
|
|
|
|
|
+
|
|
|
|
|
+To generate your key (for test purposes we are going to generate from your user), first got to your (Access IAM) page:
|
|
|
|
|
|
|
|

|
|

|
|
|
|
|
|
|
@@ -24,16 +28,68 @@ You have created a key. Press the eyeball to show the key. Copy or save it becau
|
|
|
|
|
|
|
|

|
|

|
|
|
|
|
|
|
|
-
|
|
|
|
|
-
|
|
|
|
|
-#### API key secret
|
|
|
|
|
-
|
|
|
|
|
Create a secret containing your apiKey:
|
|
Create a secret containing your apiKey:
|
|
|
|
|
|
|
|
```shell
|
|
```shell
|
|
|
kubectl create secret generic ibm-secret --from-literal=apiKey='API_KEY_VALUE'
|
|
kubectl create secret generic ibm-secret --from-literal=apiKey='API_KEY_VALUE'
|
|
|
```
|
|
```
|
|
|
|
|
|
|
|
|
|
+#### Trusted Profile Container Auth
|
|
|
|
|
+
|
|
|
|
|
+To create the trusted profile, first got to your (Access IAM) page:
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+On the left, click "Access groups":
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+Pick a name and description for your group:
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+Click on "Access Policies":
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+Click on "Assign Access", select "IAM services", and pick "Secrets Manager" from the pick-list:
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+Scope to "All resources" or "Resources based on selected attributes", select "SecretsReader":
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+Click "Add" and "Assign" to save the access group.
|
|
|
|
|
+
|
|
|
|
|
+Next, on the left, click "Trusted profiles":
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+Press "Create":
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+Pick a name and description for your profile:
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+Scope the profile's access.
|
|
|
|
|
+
|
|
|
|
|
+The compute service type will be "Red Hat OpenShift on IBM Cloud". Additional restriction can be configured based on cloud or cluster metadata, or if "Specific resources" is selected, restriction to a specific cluster.
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+Click "Add" next to the previously created access group and then "Create", to associate the necessary service permissions.
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+
|
|
|
|
|
+To use the container-based authentication, it is necessary to map the API server `serviceAccountToken` auth token to the "external-secrets" and "external-secrets-webhook" deployment descriptors. Example below:
|
|
|
|
|
+
|
|
|
|
|
+```yaml
|
|
|
|
|
+{% include 'ibm-container-auth-volume.yaml' %}
|
|
|
|
|
+```
|
|
|
|
|
+
|
|
|
### Update secret store
|
|
### Update secret store
|
|
|
Be sure the `ibm` provider is listed in the `Kind=SecretStore`
|
|
Be sure the `ibm` provider is listed in the `Kind=SecretStore`
|
|
|
|
|
|
|
@@ -42,6 +98,9 @@ Be sure the `ibm` provider is listed in the `Kind=SecretStore`
|
|
|
```
|
|
```
|
|
|
**NOTE:** In case of a `ClusterSecretStore`, Be sure to provide `namespace` in `secretApiKeySecretRef` with the namespace where the secret resides.
|
|
**NOTE:** In case of a `ClusterSecretStore`, Be sure to provide `namespace` in `secretApiKeySecretRef` with the namespace where the secret resides.
|
|
|
|
|
|
|
|
|
|
+**NOTE:** Only `secretApiKeySecretRef` or `containerAuth` should be specified, depending on authentication me
|
|
|
|
|
+thod being used.
|
|
|
|
|
+
|
|
|
To find your serviceURL, under your Secrets Manager resource, go to "Endpoints" on the left.
|
|
To find your serviceURL, under your Secrets Manager resource, go to "Endpoints" on the left.
|
|
|
Note: Use the url without the `/api` suffix that is presented in the UI.
|
|
Note: Use the url without the `/api` suffix that is presented in the UI.
|
|
|
See here for a list of [publicly available endpoints](https://cloud.ibm.com/apidocs/secrets-manager#getting-started-endpoints).
|
|
See here for a list of [publicly available endpoints](https://cloud.ibm.com/apidocs/secrets-manager#getting-started-endpoints).
|
|
@@ -51,13 +110,13 @@ See here for a list of [publicly available endpoints](https://cloud.ibm.com/apid
|
|
|
### Secret Types
|
|
### Secret Types
|
|
|
We support the following secret types of [IBM Secrets Manager](https://cloud.ibm.com/apidocs/secrets-manager):
|
|
We support the following secret types of [IBM Secrets Manager](https://cloud.ibm.com/apidocs/secrets-manager):
|
|
|
|
|
|
|
|
-* `arbitrary`
|
|
|
|
|
|
|
+* `arbitrary`
|
|
|
* `username_password`
|
|
* `username_password`
|
|
|
* `iam_credentials`
|
|
* `iam_credentials`
|
|
|
* `imported_cert`
|
|
* `imported_cert`
|
|
|
* `public_cert`
|
|
* `public_cert`
|
|
|
* `private_cert`
|
|
* `private_cert`
|
|
|
-* `kv`
|
|
|
|
|
|
|
+* `kv`
|
|
|
|
|
|
|
|
To define the type of secret you would like to sync you need to prefix the secret id with the desired type. If the secret type is not specified it is defaulted to `arbitrary`:
|
|
To define the type of secret you would like to sync you need to prefix the secret id with the desired type. If the secret type is not specified it is defaulted to `arbitrary`:
|
|
|
|
|
|