Awesome
Konfigurator
Problem
Dynamically generating app configuration when kubernetes resources change.
Solution
A kubernetes operator that can dynamically generate app configuration when kubernetes resources change
Features
- Render Configurations to
- ConfigMap
- Secret
- Support for GO Templating Engine
- Custom helper functions
- Support to watch the following Kubernetes Resources
- Pods
- Services
- Ingresses
Deploying to Kubernetes
Deploying Konfigurator requires:
- Deploying CRD to your cluster
- Deploying Konfigurator operator
You can deploy CRDs either together or separately with the operator in the helm chart by setting deployCRD
in values.yaml file.
helm repo add stakater https://stakater.github.io/stakater-charts
helm repo update
helm install stakater/konfigurator
Once Konfigurator is running, you can start creating resources supported by it. For details about its custom resources, look here.
To make Konfigurator work globally, you would have to change the WATCH_NAMESPACE
environment variable to "" in values.yaml. e.g. change WATCH_NAMESPACE
section to:
env:
- name: WATCH_NAMESPACE
value: ""
Help
Got a question? File a GitHub issue, or send us an email.
Talk to us on Slack
Join and talk to us on Slack for discussing Konfigurator
Contributing
Bug Reports & Feature Requests
Please use the issue tracker to report any bugs or file feature requests.
Developing
PRs are welcome. In general, we follow the "fork-and-pull" Git workflow.
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Push your work back up to your fork
- Submit a Pull request so that we can review your changes
NOTE: Be sure to merge the latest from "upstream" before making a pull request!
Changelog
View our closed Pull Requests.
License
Apache2 © Stakater
About
Konfigurator
is maintained by Stakater. Like it? Please let us know at hello@stakater.com
See our other projects or contact us in case of professional services and queries on hello@stakater.com