OKD4 Apps - Deployment Configuration
OpenShift deployment configuration, deployed in the Baloise Incubator OKD 4 cluster. The configuration is synced by Argo CD.
| namespace | status |
|---|---|
| okd4-sampleconfig |
| App | Link |
|---|---|
| Keycloak | https://keycloak-okd4-sampleconfig.apps.okd.baloise.dev/ |
| Simple Library-Client | https://bvcc2020-library-client.apps.baloise.dev/library-client/ |
| Scenario Library-Client | https://bvcc2020-library-frontend.apps.baloise.dev/library-client/ |
In order to work, this repository needs to be referenced in the corresponding team's root configuration yaml in the okd34-apps-root-config repository. See the respository property in the configuration.
Every deployment is in its own directory, persistent environments (test, int, acc, prod) are postfixed with the respective environment name.
A configuration for an application named demo that is deployed in test therefore is located in the folder demo-test.
Every root directoy in this repository needs to be listed as application under the applications property.
This is done automatically, whenever you add or remove a directory in the root of this repository.
You can find the corresponding tekton pipeline configuration for that synchronisation here.
Under the hood, the Job uses the GitOps CLI to perform a checkout of the okd4-apps-root-config and adjusts the applications property accordingly to the list of root directories in this repository.
Keep in mind: Only master branch is considered for all of those interactions.
The content of each directory either contains just Resource Definitions as plain yaml, a helm chart or a kustomize yaml configuration.
If you use Helm or Kustomize, the template engine is identified automatically.
ArgoCD is used to manage the deployments and sync any changes, based on a webhook in this repository, into the cluster. You can access the WebUI for baloise incubator here.