zuul-operator/zuul_operator/templates
Michael Kelly ac2488d242
Allow the specification of storageClassName in PVCs
Not every cluster has a default storage class and even if they do, we
don't always want to use that default storage class for our persistent
volumes.  Instead, allow the user to specific this via the cluster
configuration itself for the three cases we require (zookeeper,
scheduler, and registry).

Change-Id: I948d57ce59d9b16c1c70fc52af2e22bd6131e6e2
2022-11-02 22:33:08 -07:00
..
__init__.py Use kopf operator framework 2021-07-20 13:16:07 -07:00
cert-authority.yaml Update CRD apiVersion to v1 (from v1beta) 2022-06-30 18:45:23 +00:00
cert-manager.yaml Update CRD apiVersion to v1 (from v1beta) 2022-06-30 18:45:23 +00:00
nodepool-launcher.yaml Add support for imagePullSecrets 2021-10-01 16:38:36 -07:00
pxc-bundle.yaml Update CRD apiVersion to v1 (from v1beta) 2022-06-30 18:45:23 +00:00
pxc-cluster.yaml Update CRD apiVersion to v1 (from v1beta) 2022-06-30 18:45:23 +00:00
pxc-create-db.yaml Use kopf operator framework 2021-07-20 13:16:07 -07:00
zookeeper.yaml Allow the specification of storageClassName in PVCs 2022-11-02 22:33:08 -07:00
zuul-registry.yaml Allow the specification of storageClassName in PVCs 2022-11-02 22:33:08 -07:00
zuul.conf Remove gearman configuration 2022-06-28 14:02:38 +00:00
zuul.yaml Allow the specification of storageClassName in PVCs 2022-11-02 22:33:08 -07:00