Katenary / katenary

> **⚠️ Project has moved !⚠️** > > **Project moved to https://repo.katenary.io/katenary/katenary** > > Please, update your bookmaks. Discussion about the move is here : https://github.com/orgs/Katenary/discussions/162 🚀 Unleash Productivity with Katenary! 🚀 Tired of manual conversions? Katenary harnesses the labels from your " " file to craft complete Helm Charts effortlessly, saving you time and energy. 🛠️ Simple automated CLI: Katenary handles the grunt work, generating everything needed for seamless service binding and Helm Chart creation. 💡 Effortless Efficiency: You only need to add labels when it's necessary to precise things. Then call and let the magic happen. What ? Katenary is a tool to help to transform ( , , , ...) files to a working Helm Chart for Kubernetes. Today, it's partially developed in collaboration with Klee Group. Note that Katenary is and **will stay an open source and free (as freedom) project**. We are convinced that the best way to make it better is to share it with the community. The main developer is Patrice FERLET. Install Package from repository and Windows installer You can find Linux packages repository and Windows installer in the packages page. > Note for Fedora >= 42, the repository instructions are not up-to-date. You should use: > > • Windows users, go to the "generic" packages page, and download the file. • macOS users, please use the " " binary. An experimental package is in preparation. • FreedBSD users, please use the " " package in "generic" packages page. Binary installation You can download the binaries from the Release section. Copy the binary and rename it to . Place the binary inside your . You should now be able to call the command. On Linux, you can use the from the repository to install it in your directory: All OS, if you've installed Go on your computer, you can install using: Or, build yourself If you've got or , you can build by using: You can then install it with: It will use the default PREFIX ( ) to install the binary in the subdirectory. You can force the PREFIX value at install time, but maybe you need to use " ": If that goes wrong, you can use your local Go compiler: Then place the binary file inside your PATH. Tips We strongly recommend adding the completion call to you SHELL using the common , or whatever the profile file you use. E.g., Usage Katenary will try to find a or file inside the current directory. It will check \*the existence of the directory to create a new Helm Chart inside a named subdirectory. Katenary will ask you if you want to delete it before recreating. It creates a subdirectory inside that is named with the option (default is ) > To respect the ability to install the same application in the same namespace, Katenary will create variable names > like . So, you will need to use some labels inside your docker-compose file to help > Katenary to build a correct helm chart. Example of a possible file: Labels These labels could be found by , and can be placed as labels inside your docker-compose file: Katenary.yaml file and schema validation Instead of using labels inside the docker-compose file, you can use a file to define the labels. This file is simpler to read and maintain, but you need to keep it up-to-date with the docker-compose file. For example, instead of using this: You can remove the labels, and use a file: To validate the file, you can use the JSON schema using the "master" raw content: It's easy to configure in LazyVim, using , create a Lua file in your directory, or apply the settings as the example below: Use this address to validate the file in VSCode: > You can, of course, replace the with a specific tag or branch. What a name… Katenary is the stylized name of the project that comes from the "catenary" word. A catenary is a curve formed by a wire, rope, or chain hanging freely from two points that are not in the same vertical line. For example, the anchor chain between a boat and the anchor. This curved link represents what we try to do, the project is a stretched link from docker-compose to helm chart.