- airline-prediction-generator
- airline-prediction-stream
- book-info-app
- iotdemo-app
- kafka-loadtest-app
- amq-broker-operator
- argocd-operator
- codeready-workspaces-operator
- container-security-operator
- elasticsearch-operator
- integreatly-grafana-operator
- jaeger-operator
- kiali-operator
- metering-operator
- namespace-config-operator
- node-feature-discovery-operator
- opendatahub-operator
- openshift-pipelines-operator
- podium-operator
- prometheus-operator
- quay-operator
- servicemesh-operator
- strimzi-kafka-operator
- web-terminal-operator
Following a GitOps folder structure suggested by the Red Hat Canada Cloud SA team which has excellent guidance for GitOps principles (https://github.com/gnunn-gitops/standards/blob/master/folders.md)
kustomize. Kustomize is built into Kubernetes as of 1.14 which means there is full support for it in your kubernetes or OpenShift environment out of the box. Kustomize is not a templating framework, it is a patching framework that works through the concept of inheritance. Bases define the base level yaml for an application and overlays inherit from those bases or other overlays with patches to differentiate as needed.
Since kustomize doesn't use templating it's very easy to follow and understand what it is doing keeping initial complexity low. However because it relies on inheritance getting a structure that works for your team can be an involved process. (Source: https://github.com/gnunn-gitops/standards/blob/master/tools.md)
I personally have found the official documentation on kustomize to be very helpful to understand (https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/)
- Dev - Elevated security/permissions
- Test - Restricted security/permissions
- Prod - Fully controlled by pipeline process