Kue

Kue helps you manage your Kubernetes cluster configuration using CueLang.

📜 Prerequisites

• timoni installed in your system.

  Hopefully, this'll not be a requirement anymore in Kue v2.

• A Git repository.

• A Kubernetes cluster.

🚦 Getting started

• Run kue init in the manifests directory of your Git repository, to initialize a Kue project.

• The project's folder structure will look like so :

  ├── manifests/
  │   ├── environments/
  │   │   ├── production/
  │   │   │   └── main.cue
  │   ├── lib/
  │   │   ├── argocd/
  │   │   │   └── *.cue
  │   │   ├── kue.cue
  │   ├── renderred/
  │   │   ├── production/
  │   │   │   └── applications/*.yaml
  

• Run kue render to render the Kubernetes manifests.

• Push the changes to remote origin.

• kubectl apply the root ArgoCD Application.

• Open ArgoCD UI and sync the root and argocd ArgoCD Applications.

You can writeup a CI workflow, to automate renderring of the Kubernetes manifests, everytime you push changes in your Kue project.

👀 Examples

• Helm interoperatability

• Kustomize interoperatability

  Currently, you can only refer to resources in remote Git repositories. Support for specifying relative path to refer YAML document containing Kubernetes resources will be added soon.

• Sealed Secrets interoperatability

🌐 REFERENCEs

• The 2-Clause BSD License

• gitmoji : An emoji guide for your commit messages

• Go Your Own Way: Customizing Go with Environment Variables

• Nixpkgs language frameworks : Go

• Version and Automate ⚡️ Releases like a Pro - Walkthrough and Demo

• Add Commitlint, Commitizen, Standard Version, and Husky to SvelteKit Project

• The Rendered Manifests Pattern (Enhancing GitOps Visibility and Control)