cc33d34ca8
Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com> Co-authored-by: Michael Kriese <michael.kriese@visualon.de> |
||
---|---|---|
.. | ||
__fixtures__ | ||
artifacts.spec.ts | ||
artifacts.ts | ||
common.ts | ||
extract.spec.ts | ||
extract.ts | ||
index.ts | ||
readme.md | ||
types.ts |
This manager parses Flux YAML manifests and supports:
HelmRelease
resources- 'GitRepository' resources
- 'OCIRepository' resources
- Flux system manifests
HelmRelease support
Extracts helm
dependencies from HelmRelease
resources.
The flux
manager only extracts helm
dependencies for HelmRelease
resources linked to HelmRepository
or GitRepository
sources.
Renovate does not support OCI HelmRepository
sources, those with type: oci
.
In addition, for the flux
manager to properly link HelmRelease
and HelmRepository
resources, both of the following conditions must be met:
- The
HelmRelease
resource must either have itsmetadata.namespace
property set or itsspec.chart.spec.sourceRef.namespace
property set - The referenced
HelmRepository
resource must have itsmetadata.namespace
property set
Namespaces will not be inferred from the context (e.g. from the parent Kustomization
).
Renovate updates HelmRelease
resources coming from GitRepository
by updating the GitRepository
resource.
GitRepository support
Renovate can update git
references from GitRepository
resources.
The flux
manager only updates GitRepository
fields that have a tag
or commit
key.
OCIRepository support
Renovate can update oci
references from OCIRepository
resources.
The flux
manager only updates OCIRepository
fields that have a digest
or tag
key.
If tag
and digest
exist then digest
takes precedence.
Flux system manifests support
Support updating Flux system manifests generated during Flux installation.
Updating system manifests requires that either:
- The
flux
tool is pre-installed, or - You run a Docker image based on containerbase, such as the official Renovate images, and have
binarySource=install
configured
Non-configured fileMatch
By default, the flux
manager will only match flux-system/{.,**}/gotk-components.yaml
(i.e. system manifest) files.
This is because there is no commonly accepted file/directory naming convention for Flux manifests and we don't want to check every single *.yaml
file in repositories just in case some of them have Flux definitions.
If most .yaml
files in your repository are Flux manifests, then you could add this to your config:
{
"flux": {
"fileMatch": ["\\.yaml$"]
}
}
If instead you have all your Flux manifests inside a flux/
directory, you would add this:
{
"flux": {
"fileMatch": ["flux/.+\\.yaml$"]
}
}
Versioning
If you need to change the versioning format, read the versioning documentation to learn more.