Closed mneedham closed 1 year ago
Hi @mneedham, thanks for the feedback. The problem was caused by an initializing cert-manager. Though the Pods were running, it might take a while before it gets ready. The problem can be simply solved by waiting for another minute and retrying the apply
. Would you mind trying it again?
$ kubectl apply --server-side -f https://github.com/risingwavelabs/risingwave-operator/releases/latest/download/risingwave-operator.yaml
We need to add a note to the K8s page about this behavior (there might be a delay)
Steps were updated to mention that users need to wait for one minute to allow for initialization. Details in #895.
Where's the bug?
https://www.risingwave.dev/docs/current/risingwave-kubernetes
Describe the bug
I'm not sure if this is a bug, but I'm up to the 'Deploy the Operator' step and so far I did this:
So it seems like the cert manager was installed based on the output.
But then when I try to install the operator I get this output:
I think the certmanger webhook container wasn't ready at the time that we tried to call it because when I tried to apply the operator 10 minutes late I don't see any errors and all my containers are running:
I'm not knowledgeable enough about K8s operators to know if this is an actual issue, but I wonder if there could be some sort of retry logic if it fails or if not could we wait until the webhook is ready before trying to call it?