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

Propeller unable to initialize Redis client #153

Closed
adriangay opened this issue Jan 8, 2020 · 2 comments
Closed

Propeller unable to initialize Redis client #153

adriangay opened this issue Jan 8, 2020 · 2 comments

Comments

@adriangay
Copy link

I have deployed Flyte in Kubernetes v1.14.8 in Docker Desktop v2.1.0.5. The Ui starts up but laucnhing the demo EdgeDetector workflow return status unknown. looking at the deployment, flytepropeller is crashloopbackoff. The logs show the reason is connection refused to the Redis pod... help! Thanks :)

{"json":{"src":"resourcemanager_util.go:23"},"level":"info","msg":"Using Redis based resource manager","ts":"2020-01-08T15:38:34Z"}
{"json":{"src":"redis_client.go:22"},"level":"error","msg":"Error creating Redis client at [redis-resource-manager.flyte:6379]. Error: dial tcp 10.100.0.82:6379: connect: connection refused","ts":"2020-01-08T15:38:35Z"}
{"json":{"src":"resourcemanager_util.go:27"},"level":"error","msg":"Unable to initialize a redis client for the resource manager: [dial tcp 10.100.0.82:6379: connect: connection refused]","ts":"2020-01-08T15:38:35Z"}
{"json":{"src":"controller.go:96"},"level":"panic","msg":"dial tcp 10.100.0.82:6379: connect: connection refused","ts":"2020-01-08T15:38:35Z"}
panic: (*logrus.Entry) (0x1d81ea0,0xc0002c89a0)
@adriangay
Copy link
Author

my apologies... it seems that an existing istio service mesh based deployment in the same K8s interferes with the 'NodePort' Flyte deployment. flytepropeller is now starting up ok :)

@kumare3
Copy link
Contributor

kumare3 commented Mar 30, 2020

Thank you for closing the issue @adriangay

eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 6, 2022
* Add project and domain to cluster resource templating

Signed-off-by: Anand Swaminathan <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
* Inject and Use values from Security Context

Signed-off-by: Anand Swaminathan <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
* Add project and domain to cluster resource templating

Signed-off-by: Anand Swaminathan <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
* Inject and Use values from Security Context

Signed-off-by: Anand Swaminathan <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Apr 30, 2024
austin362667 pushed a commit to austin362667/flyte that referenced this issue May 7, 2024
robert-ulbrich-mercedes-benz pushed a commit to robert-ulbrich-mercedes-benz/flyte that referenced this issue Jul 2, 2024
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

2 participants