kube: clean up PersistentVolumeClaims
There's no difference as far as jsonnet is concerned, but it may confuse newbies, as Service and SimpleIngress use double colon for its top-level kube helpers. This also removes any ambiguity as to whether this is manifested in final JSON. So we can make that a convention.
Change-Id: I01ad4ea63f4d5d8ee6e5d41c79637ba186548c6f
Reviewed-on: https://gerrit.hackerspace.pl/c/hscloud/+/1803
Reviewed-by: q3k <q3k@hackerspace.pl>
diff --git a/personal/radex/demo-next/prod.jsonnet b/personal/radex/demo-next/prod.jsonnet
index b0308d0..5710030 100644
--- a/personal/radex/demo-next/prod.jsonnet
+++ b/personal/radex/demo-next/prod.jsonnet
@@ -44,10 +44,8 @@
},
data: top.ns.Contain(kube.PersistentVolumeClaim("data")) {
- storage: "1Gi",
- spec+: {
- storageClassName: "waw-hdd-redundant-3",
- },
+ storage:: "1Gi",
+ storageClass:: "waw-hdd-redundant-3",
},
service: top.ns.Contain(kube.Service(cfg.name)) {
target:: top.deployment,