You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+150-7Lines changed: 150 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,17 +7,22 @@
7
7
The openmcp bootstrapper is a command line tool that is able to set up an openmcp landscape initially and to update existing openmcp landscapes with new versions of the openmcp project.
8
8
9
9
Supported commands:
10
-
*`ocmTransfer`: Transfers the specified OCM component version from the source location to the target location.
10
+
*`ocm-transfer`: Transfers the specified OCM component version from the source location to the target location.
11
+
*`deploy-flux`: Deploys the FluxCD components to the specified Kubernetes cluster.
12
+
*`manage-deployment-repo`: Templates the openMCP git ops templates and applies them to the specified git repository and all kustomized resources to the specified Kubernetes cluster.
11
13
12
-
### `ocmTransfer`
14
+
Supported global flags:
15
+
*`--verbosity`: Sets the verbosity level of the logging output. Supported levels are `trace`, `debug`, `info`, `warn`, `error`. Default is `info`.
13
16
14
-
The `ocmTransfer` command is used to transfer an OCM component version from a source location to a target location.
15
-
The `ocmTransfer` requires the following parameters:
17
+
### `ocm-transfer`
18
+
19
+
The `ocm-transfer` command is used to transfer an OCM component version from a source location to a target location.
20
+
The `ocm-transfer` requires the following parameters:
16
21
*`source`: The source location of the OCM component version to be transferred.
17
22
*`target`: The target location where the OCM component version should be transferred to.
18
23
19
24
Optional parameters:
20
-
*`--config`: Path to the OCM configuration file.
25
+
*`--ocm-config`: Path to the OCM configuration file.
The `deploy-flux` command is used to deploy the FluxCD components to a Kubernetes cluster.
46
+
The `deploy-flux` command requires the following parameters:
47
+
*`bootstrapper-config`: Path to the bootstrapper configuration file.
48
+
49
+
Optional parameters:
50
+
*`--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.
51
+
*`--ocm-config`: Path to the OCM configuration file.
52
+
*`--git-config`: Path to the git configuration file containing the credentials for accessing the git repository. If not set, no authentication will be configured.
53
+
54
+
### bootstrapper configuration file
55
+
56
+
The `deploy-flux` command requires a bootstrapper configuration file in YAML format. The configuration file contains the following sections:
57
+
*`component` (required): The OCM component version to be deployed. The location must be in the format `<OCM Registry Location>//<Component Name>:<version>`. For example: `ghcr.io/openmcp-project/components//github.com/openmcp-project/openmcp:v0.0.18`.
58
+
*`repository` (required): The git repository where the FluxCD components should be deployed to. The `url` field specifies the URL of the git repository and the `branch` field specifies the branch to be used.
59
+
*`environment` (required): The name of the openMCP environment that shall be managed by FluxCD. For example: `dev`, `prod`, `dev-eu10`, etc.
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.
81
+
The `manageDeploymentRepo` command requires the following parameters:
82
+
*`bootstrapper-config`: Path to the bootstrapper configuration file.
83
+
*`--git-config`: Path to the git configuration file containing the credentials for accessing the git repository.
38
84
85
+
Optional parameters:
86
+
*`--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.
87
+
*`--ocm-config`: Path to the OCM configuration file.
88
+
*`--extra-manifest-dir` (repeatable): Path to an extra manifest directory that should be added to the kustomization. This can be used to add custom resources to the deployment.
89
+
*
90
+
91
+
92
+
The `manage-deployment-repo` requires a bootstrapper configuration file in YAML format. The configuration file contains the following sections:
93
+
*`component` (required): The OCM component version to be deployed. The location must be in the format `<OCM Registry Location>//<Component Name>:<version>`. For example: `gh
94
+
*`repository` (required): The git repository where the FluxCD components should be deployed to. The `url` field specifies the URL of the git repository and the `branch` field specifies the branch to be used.
95
+
*`environment` (required): The name of the openMCP environment that shall be managed by FluxCD. For example: `dev`, `prod`, `dev-eu10`, etc.
96
+
*`imagePullSecrets` (optional): A list of image pull secrets that shall be used for all Kubernetes deployments created by the bootstrapper. The secrets must already exist in the target cluster in the namespace `openmcp-system`.
97
+
*`providers` (optional): A list of `cluster-providers`, `service-providers`, and `platform-services` that shall be enabled in the deployment. Each provider can have its own configuration.
98
+
*`openmcpOperator` (required): Configuration for the openmcp operator.
0 commit comments