Open jameshbarton opened 2 years ago
Workaround is to disable prom and grafana for my testing:
prometheus:
server:
persistentVolume:
enabled: false
grafana:
persistence:
enabled: false
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Gloo Edge Version
1.12.x (beta)
Kubernetes Version
1.21.x
Describe the bug
I'm trying to test the latest 1.12 enterprise beta (beta11) in a local k3d cluster. The cluster was just created on MacOS.
The
glooe-grafana
andglooe-prometheus-server
pods fall into aCrashLoopBackOff
state. Both are failing with file access errors.glooe-prometheus-server logs:
glooe-grafana logs:
Steps to reproduce the bug
gloo.yaml file contents:
apiVersion: k3d.io/v1alpha4 kind: Simple metadata: name: gloo image: rancher/k3s:v1.21.3-k3s1 ports:
--port '8080:80@loadbalancer'
nodeFilters:--port '8443:443@loadbalancer'
nodeFilters:--wait
(default: true) timeout: "60s" # wait timeout before aborting; same as--timeout 60s
disableLoadbalancer: false # same as--no-lb
k3s: # options passed on to K3s itself extraArgs: # additional arguments passed to thek3s server
command; same as--k3s-server-arg
--k3s-node-label 'foo=bar@agent:1'
-> this results in a Kubernetes node label nodeFilters:--k3s-node-label 'foo=bar@agent:1'
-> this results in a Kubernetes node label nodeFilters:--kubeconfig-update-default
(default: true) switchCurrentContext: false # also set current-context to the new cluster's context; same as--kubeconfig-switch-context
(default: true)Install Edge Enterprise
Observe CLBF condition in
glooe-grafana
andglooe-prometheus-server
podsExpected Behavior
Enterprise installation completes with no errors.
Additional Context