https://github.com/kharf/navecd
A Type Safe Declarative Continuous Delivery Toolkit For Kubernetes
https://github.com/kharf/navecd
cloud-native cue gitops kubernetes
Last synced: 12 days ago
JSON representation
A Type Safe Declarative Continuous Delivery Toolkit For Kubernetes
- Host: GitHub
- URL: https://github.com/kharf/navecd
- Owner: kharf
- License: apache-2.0
- Created: 2023-04-21T19:29:25.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2026-03-09T17:25:53.000Z (15 days ago)
- Last Synced: 2026-03-09T22:45:25.937Z (15 days ago)
- Topics: cloud-native, cue, gitops, kubernetes
- Language: Go
- Homepage: https://navecd.dev/
- Size: 3.35 MB
- Stars: 25
- Watchers: 1
- Forks: 0
- Open Issues: 46
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
- Dco: DCO
Awesome Lists containing this project
README
A Type Safe Declarative Continuous Delivery Toolkit For Kubernetes
## What is GitOps?
GitOps is a way of implementing Continuous Deployment for cloud native applications by having a repository that contains declarative descriptions of the desired infrastructure and applications and an automated process to reconcile the production environment with the desired state in the repository.
## Why Navecd?
Traditional GitOps tools often rely on YAML for configuration, which can lead to verbosity and complexity.
Navecd leverages [CUE](https://cuelang.org/), a type safe configuration language with a more concise and expressive syntax and the benefits of general-purpose programming languages,
making it easier to define and maintain your desired cluster state.
## Documentation
To learn more about Navecd, visit [navecd.dev](https://navecd.dev/documentation/overview/)
## Contributions
We welcome contributions! To contribute to Navecd, follow these steps:
1. Fork the repository.
2. Create a new branch for your feature or bug fix.
3. Make your changes.
4. Install Dagger (https://dagger.io/)
5. Create tests and run them in a containerized environment via Dagger with:
```bash
# Run all tests
dagger call test --source=.
# Or run a specific test
dagger call test --source=. --pkg=pkg/mypkg --test=MyTest
```
6. Create a PR.
7. Ensure that your code passes the CI/CD checks.
For more information, see [CONTRIBUTING.md]().