Neil Hanlon a95a5b43bf fix(backend/kubernetes): Ensure valid naming of name field (#1661) ... - Kubernetes v1.26 on VKE causes error when creating persistent volume claim because of uppercase characters in name field This patch is trivial just in order to get it working - happy to implement differently. The error in question: ``` The PersistentVolumeClaim "wp-01G1131R63FWBSPMA4ZAZTKLE-0-clone-0" is invalid: metadata.name: Invalid value: "wp-01G1131R63FWBSPMA4ZAZTKLE-0-clone-0": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*') ```		2023-03-21 20:00:45 +01:00
..
kubernetes.go	fix(backend/kubernetes): Ensure valid naming of name field (#1661)	2023-03-21 20:00:45 +01:00
pod.go	fix(backend/kubernetes): Ensure valid naming of name field (#1661)	2023-03-21 20:00:45 +01:00
service.go	fix(backend/kubernetes): Ensure valid naming of name field (#1661)	2023-03-21 20:00:45 +01:00
service_test.go	Adding initial version of Kubernetes backend (#552)	2022-09-05 06:01:14 +02:00
utils.go	fix(backend/kubernetes): Ensure valid naming of name field (#1661)	2023-03-21 20:00:45 +01:00
volume.go	fix(backend/kubernetes): Ensure valid naming of name field (#1661)	2023-03-21 20:00:45 +01:00
volume_test.go	fix(backend/kubernetes): Ensure valid naming of name field (#1661)	2023-03-21 20:00:45 +01:00