3 dépôts
Helmfile applies strategic merge patches, JSON patches, or transformers to a Helm chart prior to installation without forking upstream charts.
Distinct from Strategic Merge Patching: Distinct from Strategic Merge Patching: focuses on patching charts before deployment, not general YAML merging.
Explore 3 awesome GitHub repositories matching devops & infrastructure · Pre-Deployment Chart Patching. Refine with filters or upvote what's useful.
Helmfile is a declarative tool for managing Kubernetes Helm releases across multiple environments. It defines the desired state of releases in version-controlled YAML files and synchronizes the cluster to match that state, acting as both a release manager and a state sync orchestrator. The tool layers environment-specific values, secrets, and lifecycle hooks onto shared release definitions, enabling consistent multi-environment deployments. Helmfile distinguishes itself through several integrated capabilities: it generates separate dependency lockfiles per environment for staged rollout of ch
Helmfile applies JSON or strategic-merge patches to resources before installation without forking upstream charts.
This is a Java client library for interacting with the Kubernetes API server. It provides a programmatic interface and a set of typed models to manage cluster resources, orchestrate state reconciliation, and administer pods and namespaces within a Kubernetes environment. The library enables the development of custom controllers by providing frameworks for implementing automated control loops that reconcile the actual state of resources with a desired target state. It supports the generation of strongly-typed Java classes from OpenAPI specifications and custom resource definitions to ensure ty
Allows updating specific fields of a resource using partial patch formats without replacing the entire object.
The project is a declarative GitOps controller and package manager designed to automate the deployment and lifecycle management of Helm charts within a cluster. It continuously watches custom resources and external artifact sources, comparing the actual cluster state against desired declarations to drive reconciliation. Artifacts and manifests are retrieved from standard package repositories, Git sources, OCI registries, and object storage buckets. The system handles complex application delivery through dependency sequencing, automated failure remediation, and drift detection. It supports cro
Applies modifications directly to external deployment definitions during synchronization to adjust configurations without forking sources.