Having the status field in the CRDs prevents continuous deployment tools (like
Argo CD) from converging.
Signed-off-by: Yann Soubeyrand <yann.soubeyrand@camptocamp.com>
* Fix CRD annotations, bump operator version
Alter port on node-exporter because CI is down
Signed-off-by: vas <vasily.sliouniaev@jet.com>
* Update dependent charts to latest
Signed-off-by: vas <vasily.sliouniaev@jet.com>
* Update readme and cleanup-attempt template
Signed-off-by: vas <vasily.sliouniaev@jet.com>
* Add option configSecret for prometheus-operator
Signed-off-by: Igor Churmeev <ingvarch@gmail.com>
* Bump version
Signed-off-by: Igor Churmeev <ingvarch@gmail.com>
* Added variabled in README.md
Signed-off-by: Igor Churmeev <ingvarch@gmail.com>
* Commented configSecret options and bump versin
Signed-off-by: Igor Churmeev <ingvarch@gmail.com>
* Introduce crds directory for compatibility with Helm v3
- This adds `crds` directory which has all 5 CRDs
- As files from crds directory needs to be plain YAMLs, keeps
app: prometheus-operator label and removes all the templating
- With this change `.Values.prometheusOperator.createCustomResource`
will be ignored by Helm v3 as it handles the CRDs differently. Which
means, if the CRDs already present in the cluster then it won't
touch them at all
- Helm v3 ignores the objects from `templates` directory which have a
`crd-install` hook
- Update the README.md
- Update the chart version
Signed-off-by: Bhavin Gandhi <bhavin7392@gmail.com>
* Use files from crds directory to generate CRDs for Helm v2
- Deletes the templates/prometheus-operator/crd-*.yaml
- Adds templates/prometheus-operator/crds.yaml which generates YAMLs
for CRDs. The hooks from these CRDs are detected by Helm v2 as well
as v3. Helm v2 executes the hook and Helm v3 ignores the hook (YAML
files are not applied)
Signed-off-by: Bhavin Gandhi <bhavin7392@gmail.com>
Markos Chandras
Jean Baptiste Favre
Yann Soubeyrand
Vasily Sliouniaev
slimm609
Igor Churmeev
Bhavin Gandhi