Renaming k8s deployment/service prevent auto-scaling

[corneil]

Description: HPA (Horizontal Pod Autoscaling) uses a Deployment name to configure scaling. If the Deployment name is modified when the user updates the deployment the HPA becomes invalid and needs to be updated.

Discussion Do we need to rename the Deployment and other artefacts when Kubernetes will rollout an update when the non-immutable part of the resource is updated?

Rollback

• k8s does provide for query of previous versions of deployment for rollback.
• SCDF can apply previously saved deployment in a roll forward fashion.

[markpollack]

The current design of skipper was based off ArgoCD and to a lesser extent Flux

[markpollack]

In a related note, can investigate supporting the TAS blue/green deployment feature now in TAS, which wasn't available when skipper was created.