Closed nlf closed 5 years ago
this shuffles some values around so that they're in the locations the k8s api expects them (they currently fail validation when applied via kubectl)
kubectl
Coverage increased (+0.01%) to 84.143% when pulling 2a25c0082bba76090680f58567a84274f1e8f01d on fix-spec into cfa387b791e6f66ce67aaf0f064cb68df2a57469 on master.
this shuffles some values around so that they're in the locations the k8s api expects them (they currently fail validation when applied via
kubectl
)