Repository files navigation

Dynamically generating app configuration when kubernetes resources change.

A kubernetes operator that can dynamically generate app configuration when kubernetes resources change

• Render Configurations to
  • ConfigMap
  • Secret
• Support for GO Templating Engine
• Custom helper functions
• Support to watch the following Kubernetes Resources
  • Pods
  • Services
  • Ingresses

Deploying Konfigurator requires:

1. Deploying CRD to your cluster
2. Deploying Konfigurator operator

You can deploy CRDs either together or separately with the operator in the helm chart by settingdeployCRD in values.yaml file.

helm repo add stakater https://stakater.github.io/stakater-chartshelm repo updatehelm install stakater/konfigurator

Once Konfigurator is running, you can start creating resources supported by it. For details about its custom resources, lookhere.

To make Konfigurator work globally, you would have to change theWATCH_NAMESPACE environment variable to "" in values.yaml. e.g. changeWATCH_NAMESPACE section to:

env:  -name:WATCH_NAMESPACEvalue:""

Got a question?File a GitHubissue, or send us anemail.

Join and talk to us on Slack for discussing Konfigurator

Please use theissue tracker to report any bugs or file feature requests.

PRs are welcome. In general, we follow the "fork-and-pull" Git workflow.

1. Fork the repo on GitHub
2. Clone the project to your own machine
3. Commit changes to your own branch
4. Push your work back up to your fork
5. Submit aPull request so that we can review your changes

NOTE: Be sure to merge the latest from "upstream" before making a pull request!

View our closedPull Requests.

Apache2 ©Stakater

Konfigurator is maintained byStakater. Like it? Please let us know athello@stakater.com

Seeour other projectsor contact us in case of professional services and queries onhello@stakater.com