feat: [PIDM-504] update deploy config

[dylantangredi-jakala]

List of Changes

• migrated helm chart to v8.0.2
• added rolling update strategy (maxUnavailable, maxSurge)

NOTE: upgraded in

• DEV -> OK
• UAT -> TODO
• PROD -> TODO

Motivation and Context

This upgrade was required to address an issue with the rollout strategy and the autoscaler behaviour, where the pods would scale down to 1 during deploy instead of keeping the same number of pods and doing +1 -1 to avoid traffic congestion.
This also ensures zero-downtime deployments by keeping all existing pods running until new versions are healthy and ready, then replacing them one at a time.

How Has This Been Tested?

❯ kubectl get scaledobject pagopa-stand-in-technical-support-microservice-chart -n nodo -o jsonpath='{.metadata.labels.helm\.sh/blueprint-version}' && echo
7.5.0

❯   kubectl get scaledobject pagopa-stand-in-technical-support-microservice-chart -n nodo -o jsonpath='{.metadata.annotations.helm\.sh/hook}' && echo " (has hooks)" || echo " (no hooks or doesn't exist)"
post-install ,post-upgrade (has hooks)

❯   kubectl delete scaledobject pagopa-stand-in-technical-support-microservice-chart -n nodo
scaledobject.keda.sh "pagopa-stand-in-technical-support-microservice-chart" deleted from nodo namespace

❯ helm dependency update
Getting updates for unmanaged Helm repositories...
...Successfully got an update from the "https://pagopa.github.io/aks-microservice-chart-blueprint" chart repository
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading microservice-chart from repo https://pagopa.github.io/aks-microservice-chart-blueprint
Deleting outdated charts

❯ helm upgrade --namespace nodo \
      --install --values ./values-dev.yaml \
      --set microservice-chart.azure.workloadIdentityClientId=919f4844-xxxxx \
      --set microservice-chart.podAnnotations.force-rollout="rollout-$(date +%s)" \
      --wait --timeout 15m0s \
      pagopa-stand-in-technical-support .
Release "pagopa-stand-in-technical-support" has been upgraded. Happy Helming!
NAME: pagopa-stand-in-technical-support
LAST DEPLOYED: Fri Oct 17 15:31:30 2025
NAMESPACE: nodo
STATUS: deployed
REVISION: 10
TEST SUITE: None

❯ kubectl get scaledobject pagopa-stand-in-technical-support-microservice-chart -n nodo -o jsonpath='{.metadata}' | jq '{labels: .labels, annotations: .annotations}'
{
  "labels": {
    "app.kubernetes.io/instance": "pagopa-stand-in-technical-support",
    "app.kubernetes.io/managed-by": "Helm",
    "app.kubernetes.io/name": "microservice-chart",
    "app.kubernetes.io/version": "0.0.10",
    "azure.workload.identity/use": "true",
    "canaryDelivery": "false",
    "helm.sh/blueprint-version": "8.0.2",
    "helm.sh/chart": "microservice-chart-0.0.10",
    "scaledobject.keda.sh/name": "pagopa-stand-in-technical-support-microservice-chart"
  },
  "annotations": {
    "meta.helm.sh/release-name": "pagopa-stand-in-technical-support",
    "meta.helm.sh/release-namespace": "nodo"
  }
}

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Comment this PR with update_code to format the code. Consider to use pre-commit to format the code.