This chart is with the security team and @pjbgf proposed an automation that would fetch the rancher-cis-operator and automatically update and generate a new charts version at rancher-cis-benchmark upon changes or by a manual trigger for starting.
Task
Architect how to implement.
Implement automation GHA job.
Document the standards necessary for other charts to adopt this automation
Why are we only implementing this for this chart?
Some charts, defined at Charts Repository architecture state review, do not follow our versioning or folder structure standards.
The idea is to use this as a Proof of Concept and present to the other teams, if they choose they can collect the benefits of the automation by adopting the standards that will be defined once again after this implementation.
We have some upstream and local charts on charts repository
rancher-cis-operator is one of the upstream charts that Rancher owns (annoyingly called different on
charts-repository
rancher-cis-benchmark.This chart is with the security team and @pjbgf proposed an automation that would fetch the rancher-cis-operator and automatically update and generate a new charts version at rancher-cis-benchmark upon changes or by a manual trigger for starting.
Task
Why are we only implementing this for this chart? Some charts, defined at Charts Repository architecture state review, do not follow our versioning or folder structure standards.
The idea is to use this as a Proof of Concept and present to the other teams, if they choose they can collect the benefits of the automation by adopting the standards that will be defined once again after this implementation.