You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automatically bump version stored in chart during release process
The mechanism could be similar to the one used in serverless - version is set to main on main branch, and replaced by Github Action with correct version on release.
Currently version would need to be updated in these places:
docker-registry - mix of config/operator/base/kustomization.yaml and chart
After labels update it became necessary to store version in the k8s resources labels.
Currently this version needs to be manually bumped, which can lead to desynchronization and errors
I have installed 0.2.0 version of docker registry module on k3d. It ws released last week.
When I lookup for the app.kubernetes.io/version label I get nothing back k get pods -n kyma-system -oyaml | grep app.kubernetes.io/version
Description
Automatically bump version stored in chart during release process
The mechanism could be similar to the one used in serverless - version is set to
main
on main branch, and replaced by Github Action with correct version on release.Currently version would need to be updated in these places:
app.kubernetes.io/*
labels for keda resources to indicate they are managed by keda manager #457)Reasons
After labels update it became necessary to store version in the k8s resources labels.
Currently this version needs to be manually bumped, which can lead to desynchronization and errors
Attachments
The text was updated successfully, but these errors were encountered: