redis-enterprise-k8s-docs icon indicating copy to clipboard operation
redis-enterprise-k8s-docs copied to clipboard

Operator fails with "Failed to get watch namespace: WATCH_NAMESPACE must not be empty"

Open javajon opened this issue 4 years ago • 4 comments

Start Kubernetes 1.18 instance on Katacoda, for example a sandbox here

Following the install procedure at https://operatorhub.io/operator/redis-enterprise, steps to reproduce:

curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.18.1/install.sh | bash -s v0.18.1

kubectl create -f https://operatorhub.io/install/redis-enterprise.yaml

kubectl logs -n operators redis-enterprise-operator-xxxxx... time="2021-05-10T21:57:28Z" level=info msg="Go Version: go1.10.3" time="2021-05-10T21:57:28Z" level=info msg="Go OS/Arch: linux/amd64" time="2021-05-10T21:57:28Z" level=info msg="operator-sdk Version: 0.0.5+git" time="2021-05-10T21:57:28Z" level=fatal msg="Failed to get watch namespace: WATCH_NAMESPACE must not be empty"

javajon avatar May 10 '21 22:05 javajon

Hi @javajon the deployment at https://operatorhub.io/operator/redis-enterprise is olds and no longer supported. For deployment steps please follow the latest version here: https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/README.md

amiramm avatar May 11 '21 01:05 amiramm

@javajon please let me know if you need further assistance

yuvallevy2 avatar May 12 '21 01:05 yuvallevy2

I tripped on the rug at the entrance. Shouldn't the published and public instructions at both operatorhub and artifacthub be the latest? Perhaps, until it's ready, the redis-enterprise might be removed from those sites if the instructions are not valid? Perhaps the top of the pages should point us to the valid instructions?

javajon avatar May 12 '21 14:05 javajon

I agree with @javajon. If the operator is deprecated on OperatorHub, it should be removed. I'd prefer the operator be updated to work on OperatorHub.

worldofgeese avatar Aug 02 '21 07:08 worldofgeese