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
Functionality for setting ephemeral metadata for Canary rollouts was proposed in #455 and implemented in #770. I would like to extend this functionality to the BlueGreen strategy as well. This would be done by adding previewMetadata and activeMetadata to the BlueGreen spec and using similar reconciliation logic to apply them to the replicasets and pods.
Use Cases
Same use cases as ephemeral metadata for canary rollouts (i.e. tagging metrics with consistent labels). My specific use case is to tag Prometheus metrics with a label if the pod is active and use that for selecting custom HPA metrics.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
@cooperbenson-qz this sounds great to have parity for blue-green. No objections to the proposal or you working on this. I'll assign the issue to you. Thanks!
Summary
Functionality for setting ephemeral metadata for Canary rollouts was proposed in #455 and implemented in #770. I would like to extend this functionality to the BlueGreen strategy as well. This would be done by adding
previewMetadata
andactiveMetadata
to the BlueGreen spec and using similar reconciliation logic to apply them to the replicasets and pods.Use Cases
Same use cases as ephemeral metadata for canary rollouts (i.e. tagging metrics with consistent labels). My specific use case is to tag Prometheus metrics with a label if the pod is active and use that for selecting custom HPA metrics.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: