Welcome to my Helm Repository! This collection serves as a central storage for my GitOps approach to cluster management. Whenever I spin up a new OpenShift cluster, these charts help me configure it quickly and consistently.
The charts are primarily used by my OpenShift GitOps cluster configuration project.
For detailed information and usage examples, please check out my blog: GitOps Collection
Feel free to test these charts and let me know if you encounter any issues or have suggestions for improvements.
These Helm charts are the building blocks. The GitOps Catalog shows how they come together in actual ArgoCD Applications to configure OpenShift clusters — from security & compliance to observability & storage.
Explore the GitOps Catalog46 charts available
Configure AdminNetworkPolicy and BaselineNetworkPolicy resources for a cluster.
Collection of management Operators which are required as a dependency for other services, such as Logging, Loki, NetObserv etc. It simply calls helper-operator to deploy all required operators without any configuration of a CRD.
Collection of Operators which can be deployed on Demo Systems without any configuration of a CRD.
Collection of optional operators, like CodeReadyWorkspaces without any configuration of a CRD.
Master chart to deploy and configure the Compliance Operator
Red Hat OpenShift Dev Spaces is a collaborative Kubernetes-native development solution that delivers consistent developer environments on Red Hat OpenShift.
Create a CronJob that performs ETCD Backup and stores the backup to a PV.
This Chart is responsible for deploying generic cluster configuration, for example, etcd encryption, OAuth etc.
This Chart shall help to generate policies for Advanced Cluster Management
Takes care of creation of Applications, Appprojects and ApplicationSets (supporting different generators)
Loki requires a secret with specific keys. This Chart creates a Job that will create such a secret based on the OpenShift Data Foundation BucketClaim.
The only purpose of this helper chart is to provide a template for the LokiStack Custom Resource, so it must not be re-defined for multiple services.
A helper Chart to create BackingStore, BackingClass, BucketClaim and StorageClass objects, when ODF is used. Currently type PV is supported only (Creating a local Persistent Volume-backed backingstore)!
Some services like Tempo require a secret with a specifc key for the object sotrage. When a S3 bucket is created via OpenShift Data Foundation, then this chart will help to generate a correct secret. (This is an evolution of helper-loki-bucket-secret)
A helper Chart to reduce code repetition. This Chart should be called as a dependency by other charts in order to install Operators.
This Chart shall deploy namespaces and their depending resources, like NetworkPolicies or Quotas etc.
Using Server Side Apply to create for example node labelling, requires openshift-gitops 1.6+
A helper Chart that creates a job to verify if the deployments of an operator are running. To do so it creates a service account with a role to read the status of the Deployments.
A Chart to automate the bucket creation and configuration for MINIO Object Storage
Installs and configures OpenShift Network Observability Operator.
Deploys and configures the OpenShift Data Foundation Operator.
Installs and patches the Red Hat Openshift Gitops Operator
Deploy and configure OpenShift Logging based on LokiStack
Configure the operator Openshift Virtualization (HyperConverged and HostPath Provisioner)
Create an example Pipeline which does a linting of openshift-clusterconfig-gitops using kubelinter, yamllin, yamlscore ....
Configure Red Hat Build of OpenTelemetry Operator resources (Collector, Instrumentation, TargetAllocator).
Setup and configure Advanced Cluster Managerment. Replaces the Chart rhacm-full-stack.
Chart to create a CronJoc to backup Advanced Cluster Security for Kubernetes to a PerstistentVolume.
Deploy a demo application with known SECURITY RISKS!!! Used for RHACS Demos
Master chart to deploy RHACS operator, initialize it and do some configuration using API Calls
A Helm chart to deploy sealed-secrets - depends on Bitnami's helm chart
Setup the Quay Container Security Operator.
A Helm chart to deploy sonarqube community edition -d epends on Sonarcube's helm chart
A library that shall collect certain templates to reuse them among different charts.
Master chart to deploy RHACM operator
Master chart to deploy RHACS operator, initialize it and do some configuration using API Calls
To use these Helm charts, add this repository to your Helm configuration:
helm repo add tjungbauer https://charts.stderr.at/
helm repo updateThen install any chart:
helm install my-release tjungbauer/<chart-name>
These Charts are used to make my life easier when I need to install a Demo-Environment. Anyone is free to use them and make suggestions.
Mainly used by: https://github.com/tjungbauer/openshift-clusterconfig-gitops