3dbe870455
Update kube-prometheus-stack helm release values to configure
kube-state-metrics and use kube-state-metrics to collect gotk resource
state metrics.
- Configure kube-state-metrics to run in custom resource state only
mode. In this mode, it'll only watch custom resources. Also, pass
empty collectors as extra args to prevent passing all the core
resources to watch as an argument.
- Running kube-state-metrics in custom resource state only mode makes
the default grafana dashboards of no use. Disable the default
dashboards.
- Add kube-state-metrics configuration to provide RBAC permissions to it
to allow listing and watching flux CRDs.
- Also, configure custom resource state for each of the flux custom
resources using Info type metrics called `gotk_resource_info`. KSM
issues a warning if an Info type object doesn't have `_info` suffix.
These metrics have the value 1 always. This works well for the CRD
state metrics as a zero value would mean that the resource doesn't
exist, in which case, the resource is deleted.
- Update the cluster dashboard panels to use `gotk_resource_info` in the
queries.
- Only the following panels have been updated
- Cluster Reconcilers
- Failing Reconcilers
- Cluster reconciliation readiness
- Kubernetes Manifests Sources
- Failing Sources
- Source acquisition readiness
- The panels have been updated such that it's work with static
resources which don't have any status as well. By default, it assumes
such static resources to be in a Ready state. Resources are seen as
failed only when the ready value is false.
- The queries have been updated to Instant type in order to show the
current data, instead of the result of past 15 minutes. This shows
more accurate resource data as the resource metrics change.
- The Stat visualizers have been updated to have zero as the default
value when there's no data. This is to prevent showing no data when
there's no object. This was motivated by the behavior of the previous
configuration which depended on stale metrics from controllers and
deleted conditions to show zero value when objects get deleted. With
the fixes in the controller metrics that removes stale metrics, this
will no longer work. In order to show a zero value for these stats, a
default is set.
- The `$namespace` variable has been updated to refer to
`exported_namespace` from `gotk_resource_info`.
Signed-off-by: Sunny <darkowlzz@protonmail.com>
|
||
|---|---|---|
| .github | ||
| action | ||
| cmd/flux | ||
| docs/release | ||
| install | ||
| internal | ||
| manifests | ||
| pkg | ||
| rfcs | ||
| tests | ||
| .gitignore | ||
| .goreleaser.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| DCO | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| netlify.toml | ||
| README.md | ||
Flux version 2
Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories and OCI artifacts), and automating updates to configuration when there is new code to deploy.
Flux version 2 ("v2") is built from the ground up to use Kubernetes' API extension system, and to integrate with Prometheus and other core components of the Kubernetes ecosystem. In version 2, Flux supports multi-tenancy and support for syncing an arbitrary number of Git repositories, among other long-requested features.
Flux v2 is constructed with the GitOps Toolkit, a set of composable APIs and specialized tools for building Continuous Delivery on top of Kubernetes.
Flux is a Cloud Native Computing Foundation (CNCF) project, used in production by various organisations and cloud providers.
Quickstart and documentation
To get started check out this guide on how to bootstrap Flux on Kubernetes and deploy a sample application in a GitOps manner.
For more comprehensive documentation, see the following guides:
- Ways of structuring your repositories
- Manage Helm Releases
- Automate image updates to Git
- Manage Kubernetes secrets with Mozilla SOPS
If you need help, please refer to our Support page.
GitOps Toolkit
The GitOps Toolkit is the set of APIs and controllers that make up the runtime for Flux v2. The APIs comprise Kubernetes custom resources, which can be created and updated by a cluster user, or by other automation tooling.
You can use the toolkit to extend Flux, or to build your own systems for continuous delivery -- see the developer guides.
Components
- Source Controller
- Kustomize Controller
- Helm Controller
- Notification Controller
- Image Automation Controllers
Community
Need help or want to contribute? Please see the links below. The Flux project is always looking for new contributors and there are a multitude of ways to get involved.
- Getting Started?
- Look at our Get Started guide and give us feedback
- Need help?
- First: Ask questions on our GH Discussions page.
- Second: Talk to us in the #flux channel on CNCF Slack.
- Please follow our Support Guidelines (in short: be nice, be respectful of volunteers' time, understand that maintainers and contributors cannot respond to all DMs, and keep discussions in the public #flux channel as much as possible).
- Have feature proposals or want to contribute?
- Propose features on our GitHub Discussions page.
- Join our upcoming dev meetings (meeting access and agenda).
- Join the flux-dev mailing list.
- Check out how to contribute to the project.
- Check out the project roadmap.
Events
Check out our events calendar, both with upcoming talks, events and meetings you can attend. Or view the resources section with past events videos you can watch.
We look forward to seeing you with us!