Mateusz Gozdek
Mateusz Gozdek
I also hit this, when trying to deploy using https://github.com/nextcloud/helm with the following values.yaml file: ``` nextcloud: password: "test test test" ```
I think it shouldn't be too hard to implement a retry on 429 for this provider, though 10 requests per _minute_ seems like a serious limitation, which will increase Terraform...
It seems with combination with https://github.com/stakater/IngressMonitorController, iteracting with UptimeRobot API is now barely usable :disappointed:
Not very production quality but I wrote a patch, which makes provider very slow when you're close to API limit, but usable: https://github.com/louy/terraform-provider-uptimerobot/compare/master...invidian:invidian/retry-on-rate-limit?expand=1
/area tech-debt :smile:
#48 did not address all points here.
You can run the following as a workaround for now :smile: ``` linkerd inject https://projectcontour.io/quickstart/contour.yaml | sed 's/automountServiceAccountToken: false/automountServiceAccountToken: true/g' | kubectl apply -f - ```
@edgan you could also try to manually approve the certificate when bootstrapping first node. `hostNetwork: true` should also do the trick.
Also adding a member as a learner and then promoting it in PostStart hook once it catched up would be good.
Few ideas: - with admin config passed to kubelet, we could generate and create bootstrap tokens automatically - helm chart can take list of tokens to create (e.g. with expiration...