When improving our charts, it is necessary to contribute upstream on Cloudpirates.io.

1. Set upstream URL with git remote add upstream https://github.com/CloudPirates-io/helm-charts.git
2. Execute ./contrib.sh <new-branch> script to start new contribution
3. Cherry-pick your changes
4. Create a new PR on upstream main branch

To keep our fork aligned with the upstream repository, a dedicated pipeline runs daily to synchronize changes. This pipeline automatically creates a pull request containing all upstream updates. The PR is created from a dedicated branch (automated-upstream-sync) and is updated daily if new changes are detected upstream.

The pipeline can also be triggered manually from the Actions tab by running the Sync Fork with Upstream workflow.

When ready, merge the PR to sync the fork with the upstream repository.

First ensure you enable merge policy by adding in your .git/config file:

[merge "theirs"] driver = true 

This will apply the CHANGELOG.md merge policy defined in .gitattributes

1. Update upstream git fetch upstream
2. Create sync branch git checkout -b my-sync-branch
3. Check last X most recent commits that are on upstream/main but not yet on your branch git log --pretty=format:'%h %ad %s' --date=short HEAD..upstream/main | tail -50
4. Merge target commit git merge <sha>
5. Push to remote branch git push origin my-sync-branch

A curated collection of production-ready Helm charts for open-source cloud-native applications. This repository provides secure, well-documented, and configurable Helm charts following cloud-native best practices (project name "nonami").

Chart	Description	Version
ClusterPirate	Client agent for the CloudPirates Managed Observability Platform to connect your Kubernetes cluster to our infrastructure
Common	A library chart for common templates and helper functions
Etcd	A distributed reliable key-value store
Ghost	A simple, powerful publishing platform that allows you to share your stories with the world.
Keycloak	Open Source Identity and Access Management solution
MariaDB	High-performance, open-source relational database server that is a drop-in replacement for MySQL
Memcached	High-performance, distributed memory object caching system
MinIO	High-Performance Object Storage compatible with Amazon S3 APIs
MongoDB	MongoDB a flexible NoSQL database for scalable, real-time data management
Nginx	High-performance HTTP server and reverse proxy
PostgreSQL	The World's Most Advanced Open Source Relational Database
RabbitMQ	A messaging broker that implements the Advanced Message Queuing Protocol (AMQP)
RabbitMQ Cluster Operator	Kubernetes operator to deploy and manage RabbitMQ clusters [ALPHA]
Redis	In-memory data structure store, used as a database, cache, and message broker
RustFS	High-performance distributed object storage with S3-compatible API (MinIO alternative) [ALPHA]
TimescaleDB	TimescaleDB is a PostgreSQL extension for high-performance real-time analytics on time-series and event data
Valkey	High-performance in-memory data structure store, fork of Redis
Zookeeper	Centralized service for maintaining configuration information, naming, providing distributed synchronization, and group services

• Kubernetes 1.24+
• Helm 3.2.0+
• PV provisioner support in the underlying infrastructure (if persistence is enabled)

# From Docker Hub registry helm install my-release oci://registry-1.docker.io/cloudpirates/<chartname># From GitHub Container Registry (GHCR) helm install my-release oci://ghcr.io/cloudpirates-io/helm-charts/<chartname># From local clone helm install my-release ./charts/<chart-name>

All charts in this repository provide:

• Cryptographically Signed: All charts are signed with Cosign for supply chain security
• Non-root containers by default
• Read-only root filesystems where possible
• Dropped Linux capabilities
• Security contexts configured
• No hardcoded credentials

• Comprehensive health checks (liveness, readiness, startup probes)
• Resource requests and limits support
• Persistent storage configurations
• Rolling update strategies
• Health check endpoints

• Extensive values.yaml with detailed documentation
• Support for existing secrets and ConfigMaps
• Flexible ingress configurations
• Service account customization
• Common labels and annotations support

Each chart provides extensive configuration options through values.yaml. Key configuration areas include:

• Authentication & Security: User credentials, existing secrets, security contexts
• Storage: Persistent volumes, storage classes, backup configurations
• Networking: Services, ingress, network policies
• Scaling: Replica counts, autoscaling, resource limits
• Monitoring: Metrics, service monitors, health checks

Refer to individual chart READMEs for detailed configuration options.

Want to contribute? Awesome! The most basic way to show your support is to star the project, or to raise issues.

If you want to open a PR, read our contributing guidelines for information about setting up your environment and instructions on the signature verification that we require.

Chat with us and the community on our Discord server!
Everyone is welcome, wether you have a question, need help with a chart, want to contribute, know what's coming next or just have a talk with us.

This project is built and maintained by our growing community of contributors!

Made with contrib.rocks.

For issues specific to these Helm charts:

• Check individual chart README files for troubleshooting
• Review chart documentation and examples
• Verify configuration values
• Open an issue on GitHub