Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
javajon opened this issue May 10, 2021 · 4 comments
Assignees

Comments

@javajon
Copy link

javajon commented May 10, 2021

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"

@amiramm
Copy link
Collaborator

amiramm commented May 11, 2021

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

@yuvallevy2
Copy link
Contributor

@javajon please let me know if you need further assistance

@javajon
Copy link
Author

javajon commented May 12, 2021

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?

@worldofgeese
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants