- If you made changes to mysql and keycloak credentials.
- If you want to change logging level (TRACE / DEBUG / INFO / WARN / ERROR).
> ***If you are using a non-local domain, replace everywhere the http://keycloak:8080 with the respective {{protocol://domain.name}}, as well as "spring.portal.main.domain" property.***
In folder `org.etsi.osl.main/compose/` edit the file `docker-compose.yaml`
If you want to create and manage Kubernetes Custom Resources (CRs), you will have to provide:
If you want to create and manage Kubernetes Custom Resources (CRs), you will have to provide:
...
@@ -226,7 +179,7 @@ volumes:
...
@@ -226,7 +179,7 @@ volumes:
> **The above configuration works for the default kubeconf file names. It explicitly expects a file named `config` within the `/root/.kube` directory of the created container.**
> **The above configuration works for the default kubeconf file names. It explicitly expects a file named `config` within the `/root/.kube` directory of the created container.**
Optionally, if you want to use custom kubeconf file names you will have to sync volumes by files and not entire directories, e.g.
Optionally, if you want to use custom kubeconf file names, you will have to sync volumes by files and not entire directories, e.g.
```yaml
```yaml
volumes:
volumes:
...
@@ -234,6 +187,7 @@ volumes:
...
@@ -234,6 +187,7 @@ volumes:
```
```
OpenSlice also offers management support of *multiple Kubernetes Clusters* simultaneously. For this, you will have to:
OpenSlice also offers management support of *multiple Kubernetes Clusters* simultaneously. For this, you will have to:
- add all the respective kubeconf files into the `org.etsi.osl.main/compose/kubedir` directory.
- add all the respective kubeconf files into the `org.etsi.osl.main/compose/kubedir` directory.
- create a copy of CRIDGE service in the deployment file and map the appropriate volumes. *Mind the need for a different service and container name*.
- create a copy of CRIDGE service in the deployment file and map the appropriate volumes. *Mind the need for a different service and container name*.
...
@@ -255,6 +209,53 @@ cridge-cluster2:
...
@@ -255,6 +209,53 @@ cridge-cluster2:
> Note the same `/root/.kube/config` container's path for the proper functionality. See the above note for explanation.
> Note the same `/root/.kube/config` container's path for the proper functionality. See the above note for explanation.
- If you made changes to mysql and keycloak credentials.
- If you want to change logging level (TRACE / DEBUG / INFO / WARN / ERROR).
> ***If you are using a non-local domain, replace everywhere the http://keycloak:8080 with the respective {{protocol://domain.name}}, as well as "spring.portal.main.domain" property.***
In folder `org.etsi.osl.main/compose/` edit the file `docker-compose.yaml`
@@ -119,6 +119,7 @@ By default, the deployment process copies the `org.etsi.osl.main/kubernetes/helm
...
@@ -119,6 +119,7 @@ By default, the deployment process copies the `org.etsi.osl.main/kubernetes/helm
> **The above configuration works for the default kubeconf file names. It explicitly expects a file named `config` within the `org.etsi.osl.main/kubernetes/helm/openslice/files/org.etsi.osl.cridge` directory. If you are working with custom kubeconf file names, you will have to rename them.**
> **The above configuration works for the default kubeconf file names. It explicitly expects a file named `config` within the `org.etsi.osl.main/kubernetes/helm/openslice/files/org.etsi.osl.cridge` directory. If you are working with custom kubeconf file names, you will have to rename them.**
OpenSlice also offers management support of *multiple Kubernetes Clusters* simultaneously. For this, you will have to:
OpenSlice also offers management support of *multiple Kubernetes Clusters* simultaneously. For this, you will have to:
- add all the respective kubeconf files into the `org.etsi.osl.main/compose/kubedir` directory.
- add all the respective kubeconf files into the `org.etsi.osl.main/compose/kubedir` directory.
- create a copy of the `cridge.yaml` and `cridge-config.yaml` in `\org.etsi.osl.main\kubernetes\helm\openslice\templates` directory for every Cluster. *Mind the need for different naming*.
- create a copy of the `cridge.yaml` and `cridge-config.yaml` in `\org.etsi.osl.main\kubernetes\helm\openslice\templates` directory for every Cluster. *Mind the need for different naming*.
- update every `cridge-config.yaml` file to get the appropriate kubeconf file for every Cluster.
- update every `cridge-config.yaml` file to get the appropriate kubeconf file for every Cluster.