5ed8d0bbdc
Some checks failed
scrum-manager/pipeline/head There was a failure building this commit
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>
33 lines
822 B
YAML
33 lines
822 B
YAML
# apiVersion: kustomize.config.k8s.io/v1beta1
|
|
# kind: Kustomization
|
|
|
|
# resources:
|
|
# - ../../base
|
|
# - mysql-pv.yaml
|
|
# - ingress.yaml
|
|
|
|
# patches:
|
|
# - path: mysql-pvc-patch.yaml
|
|
# target:
|
|
# kind: PersistentVolumeClaim
|
|
# name: mysql-data-pvc
|
|
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
resources:
|
|
- ../../base
|
|
- ingress.yaml
|
|
|
|
# NOTE: mysql-pv.yaml and mysql-pvc-patch.yaml are only needed on clusters
|
|
# without a default StorageClass. This cluster uses 'local-path' (dynamic
|
|
# provisioner), so the base PVC works as-is and must NOT be patched after
|
|
# it is already bound.
|
|
|
|
images:
|
|
- name: scrum-frontend
|
|
newName: 192.168.108.200:80/library/scrum-frontend
|
|
newTag: latest
|
|
- name: scrum-backend
|
|
newName: 192.168.108.200:80/library/scrum-backend
|
|
newTag: latest |