Our Kubernetes cluster enforces the presence of resource limits on container specs. These can be specified via the helm chart for every container, except for the yugabyted-ui containers. See, here:
This leads to the deployment of Yugabyte with the UI enabled failing
$ kubectl get events
LAST SEEN TYPE REASON OBJECT MESSAGE
22s Warning FailedCreate statefulset/yb-master create Pod yb-master-0 in StatefulSet yb-master failed error: admission webhook "validation.gatekeeper.sh" denied the request: [container-ephemeral-storage-limit] container <yugabyted-ui> has no resource limits...
22s Warning FailedCreate statefulset/yb-tserver create Pod yb-tserver-0 in StatefulSet yb-tserver failed error: admission webhook "validation.gatekeeper.sh" denied the request: [container-ephemeral-storage-limit] container <yugabyted-ui> has no resource limits...
Our Kubernetes cluster enforces the presence of resource limits on container specs. These can be specified via the helm chart for every container, except for the yugabyted-ui containers. See, here:
charts/stable/yugabyte/templates/service.yaml
Line 667 in cfaafff
This leads to the deployment of Yugabyte with the UI enabled failing