Skip to content

Example App Deployment Configuration for Baloise Incubator OKDv4 Cluster

Notifications You must be signed in to change notification settings

baloise-incubator/okd4-example-apps

Repository files navigation

OKD4 Example Apps - Deployment Configuration

App Status

Setup

In order to work, this repository needs to be referenced in the corresponding team's root configuration yaml in the okd4-apps-root-config repository. See the respository property in the configuration.

Structure

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.

Continuous Delivery

Argo CD 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.

About

Example App Deployment Configuration for Baloise Incubator OKDv4 Cluster

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published