Khalkeon is a tool designed to streamline and automate the process of merging multiple coreos ignitions. It ensures that the resulting configurations are consistent, valid, and ready for deployment.
- go version v1.23.0+
- docker version 17.03+.
- kubectl version v1.11.3+.
- Access to a Kubernetes v1.11.3+ cluster.
Build and push your image to the location specified by IMG
:
make docker-build docker-push IMG=<some-registry>/khalkeon:tag
NOTE: This image ought to be published in the personal registry you specified. And it is required to have access to pull the image from the working environment. Make sure you have the proper permission to the registry if the above commands don’t work.
Install the CRDs into the cluster:
make install
Deploy the Manager to the cluster with the image specified by IMG
:
make deploy IMG=<some-registry>/khalkeon:tag
Create instances of your solution You can apply the samples (examples) from the config/sample:
kubectl apply -k config/samples/
Validate ignition was created successfully You can check the result of ignitions merging in the secret data:
kubectl get secret target --template={{.data.config}} | base64 --decode | jq .
Delete the instances (CRs) from the cluster:
kubectl delete -k config/samples/
UnDeploy the controller from the cluster:
make undeploy
Delete the APIs(CRDs) from the cluster:
make uninstall
This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.
If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.
Copyright 2025 SAP SE or an SAP affiliate company and IronCore contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.