rbren
commented
2 years ago FWIW I deleted the chart, waited ~15 minutes~ 12 hours, and tried again (IIRC the rate limit resets after 10m). Sadly it didn't seem to work - still rate limited. So I'm guessing there's something else going on.
Happy to provide additional logs.
Here are the values I supplied to the budibase chart - that may help to reproduce.
services:
couchdb:
storage: 1Gi
objectStore:
storage: 1Gi
redis:
storage: 1Gi
ingress:
enabled: true
hosts:
- host: $BUDIBASE_HOST
tls: true
tlsSecret: tls-prod-cert-ghost
paths:
- path: /
pathType: Prefix
backend:
service:
name: proxy-service
port:
number: 10000
annotations:
kubernetes.io/ingress.class: nginx
certmanager.k8s.io/cluster-issuer: letsencrypt-prod
kubernetes.io/tls-acme: "true"
nginx.ingress.kubernetes.io/proxy-body-size: 5m
timoreimann
I seem to get rate limited rather quickly when using the DO CSI. Given the nature of the kubernetes control loop, it's not surprising that it makes a number of (probably unnecessary) requests.
I wonder if rate limiting could be relaxed a bit for traffic coming from the CSI?
What did you do? (required. The issue will be closed when not provided.)
I tried to install Budibase via the helm chart
What did you expect to happen?
Everything installs nicely. But instead, I get
Configuration (MUST fill this out):
Please provide the following logs:
I can provide these if need be, but not super comfortable giving all that info out.
This will output everthing from your cluster. Please use a private gist via https://gist.github.com/ to share this dump with us
Please provide the total set of manifests that are needed to reproduce the issue. Just providing the
pvcis not helpful. If you cannot provide it due privacy concerns, please try creating a reproducible case.CSI Version:
docker.io/digitalocean/do-csi-plugin:v2.1.2Kubernetes Version:
Cloud provider/framework version, if applicable (such as Rancher): DO