tusuii 5ed8d0bbdc fix: remove PVC patch that broke kubectl apply on bound claims ...

The mysql-data-pvc was already dynamically provisioned by the cluster's
'local-path' StorageClass. The overlay patch tried to change storageClassName
to 'manual' and volumeName on an already-bound PVC, which Kubernetes forbids:
  "spec is immutable after creation except resources.requests"

Fixes:
- Remove mysql-pvc-patch from kustomization.yaml (PVC left as-is)
- Remove mysql-pv.yaml resource (not needed with dynamic provisioner)
- Add comment explaining when manual PV/PVC is needed vs not

Jenkinsfile: add --timeout and FQDN to smoke test curl; add comments
explaining MySQL Recreate strategy startup timing expectations.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-02-27 23:02:54 +05:30

..

deploy.sh

fix: k8s on-premise deployment and session persistence

2026-02-27 22:51:57 +05:30

ingress.yaml

fix: k8s on-premise deployment and session persistence

2026-02-27 22:51:57 +05:30

kustomization.yaml

fix: remove PVC patch that broke kubectl apply on bound claims

2026-02-27 23:02:54 +05:30

mysql-pvc-patch.yaml

fix: k8s on-premise deployment and session persistence

2026-02-27 22:51:57 +05:30