Kvaps' review on #3178 flagged that this package's \`make update\`
target does \`rm -rf charts && helm pull cowboysysop/vertical-pod-
autoscaler --version 11.1.1\` with no re-apply step. Any local edits
to the vendored subchart were therefore one \`make update\` away
from vanishing without warning — exactly what the fluxcd-operator
package pre-empts via a \`patches/*.diff\` re-apply loop after the
helm pull.
Adopt the same convention here:
* New file \`patches/cert-manager-admission-tls.diff\` capturing
all four modifications the cert-manager path makes to the
vendored subchart — the new \`certificate.yaml\` template, the
checksum/tls-secret + new checksum/tls-cert annotation gating on
the admission-controller Deployment, the certManagerEnabled
guard on the legacy \`tls-secret.yaml\`, and the new
\`certManagerEnabled: true\` default in the subchart values.
* Makefile \`update\` target now runs
\`patch --no-backup-if-mismatch -p1 < patches/*.diff\` after the
helm pull, so a future upstream bump (or a routine
\`make update\` today) re-applies the cozystack modifications
over the freshly-fetched vendored files and leaves the chart in
the same state git tracks.
Verified end-to-end: with the on-disk chart intact I ran
cp -r charts/vertical-pod-autoscaler /tmp/reference
rm -rf charts
helm pull cowboysysop/vertical-pod-autoscaler --untar --untardir charts --version 11.1.1
patch --no-backup-if-mismatch -p1 < patches/cert-manager-admission-tls.diff
diff -r charts/vertical-pod-autoscaler /tmp/reference
The diff is empty — \`make update\` now produces a byte-identical
tree to what git has right now, and the 15 helm-unittest cases still
pass unchanged.
Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>