feat: [PIDM-504] update deploy config

[dylantangredi-jakala]

List of Changes

• upgraded helm chart to v8.0.2 (note: no autoscaling enabled on this service so no ScaledObject presence/migration)
• 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?

❯ 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 fdr \
    --install --values ./values-dev.yaml \
    --set microservice-chart.azure.workloadIdentityClientId=edaa7974-85d3-47ec-9a72-0c050f15fe1f \
    --set microservice-chart.podAnnotations.force-rollout="rollout-$(date +%s)" \
    --wait --timeout 15m0s \
    fdr-technicalsupport .
Release "fdr-technicalsupport" has been upgraded. Happy Helming!
NAME: fdr-technicalsupport
LAST DEPLOYED: Thu Oct 16 14:41:30 2025
NAMESPACE: fdr
STATUS: deployed
REVISION: 7
TEST SUITE: None

❯ kubectl get pods,hpa,scaledobject -n fdr -l app.kubernetes.io/instance=fdr-technicalsupport
NAME                                                           READY   STATUS    RESTARTS   AGE
pod/fdr-technicalsupport-microservice-chart-85c9bb8dd6-lh2f9   1/1     Running   0          3m42s

❯ kubectl get pods -n fdr -l app.kubernetes.io/instance=fdr-technicalsupport
NAME                                                       READY   STATUS    RESTARTS   AGE
fdr-technicalsupport-microservice-chart-85c9bb8dd6-lh2f9   1/1     Running   0          4m25s

❯ kubectl get deployment -n fdr -l app.kubernetes.io/instance=fdr-technicalsupport
NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
fdr-technicalsupport-microservice-chart   1/1     1            1           170d

❯ kubectl get deployment -n fdr -l app.kubernetes.io/instance=fdr-technicalsupport -o jsonpath='{.items[0].metadata.labels.helm\.sh/blueprint-version}'
8.0.2%

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.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.