UNCLASSIFIED - NO CUI

OCI Chart naming consistency

For OCI naming consistency we want OCI artifacts to be named the same as our values keys (which should align to our naming standards).

From a quick review of our draft 2.0 values there are several packages that need renaming:

  • jaeger: rename chart from jaeger-operator to jaeger
  • kyvernoReporter: rename chart from policy-reporter to kyverno-reporter
  • monitoring: rename chart from kube-prometheus-stack to monitoring

NOTE: We want to leverage name overrides where possible so that nothing changes names for pods, labels, etc. Most packages have a nameOverride value or similar that you can set to the previous chart name and then templates will use that. If this is not an option, this change will need to be re-evaluated.

Edited by Micah Nagel