Skip to content

Commit dd5fbed

Browse files
committed
feat: add deploy-eso part to readme
On-behalf-of: Radek Schekalla (SAP) <[email protected]> Signed-off-by: Radek Schekalla (SAP) <[email protected]>
1 parent 05aacdd commit dd5fbed

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

README.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,30 @@ Example:
7575
openmcp-bootstrapper deploy-flux ./examples/bootstrapper-config.yaml --kubeconfig ~/.kube/config --ocm-config ./examples/ocm-config.yaml --git-config ./examples/git-config.yaml ./examples/bootstrapper-config.yaml
7676
```
7777

78+
## `deploy-eso`
79+
The `deploy-eso` command is used to deploy the `external-secrets-operator` to a Kubernetes cluster using the previously deployed `FluxCD` components.
80+
81+
The `deploy-eso` command requires the following parameters:
82+
* `bootstrapper-config`: Path to the bootstrapper configuration file, optionally containing the `ExternalSecrets` section.
83+
* `ExternalSecrets` (optional): Configuration for the external-secrets-operator deployment containing `RepositorySecretRef` and `ImagePullSecrets`
84+
85+
```yaml
86+
externalSecrets:
87+
repositorySecretRef:
88+
name: repo-secret
89+
imagePullSecrets:
90+
- name: image-pull-secret
91+
```
92+
93+
Optional parameters:
94+
* `--kubeconfig`: Path to the kubeconfig file of the target Kubernetes cluster. If not set, the value of the `KUBECONFIG` environment variable will be used. If the `KUBECONFIG` environment variable is not set, the default kubeconfig file located at `$HOME/.kube/config` will be used.
95+
* `--ocm-config`: Path to the OCM configuration file.
96+
97+
Example:
98+
```shell
99+
openmcp-bootstrapper deploy-eso ./examples/bootstrapper-config.yaml --kubeconfig ~/.kube/config --ocm-config ./examples/ocm-config.yaml ./examples/bootstrapper-config.yaml
100+
```
101+
78102
## `manage-deployment-repo`
79103

80104
The `manageDeploymentRepo` command is used to template the openMCP git ops templates and apply them to the specified git repository and all kustomized resources to the specified Kubernetes cluster.

0 commit comments

Comments
 (0)