You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "manneym (via GitHub)" <gi...@apache.org> on 2023/09/22 17:45:30 UTC
[GitHub] [superset] manneym opened a new issue, #25375: Installing latest superset via helm, cant connect to azure redis service via ssl
manneym opened a new issue, #25375:
URL: https://github.com/apache/superset/issues/25375
I have been trying to install superset:latest using helm into an azure aks kubernetes service.
I wanted to use a managed postgresql db server for the database
I also wanted to.use an azure managed redis cache
Managed to get it installed ok and connecting to the database with no issues
However it was running like a dog.
Examining the log file I noticed it was reporting errors connecting to the redis cache.
REDIS_HOST, REDIS_PORT, REDIS_PASSWORD were set correctly, but it was still failing to connect. I noticed that default settings for azure redus cache is to disable non-SSL connections... if I turn the option off, and changed the REDIS_PORT to the non ssl port, superset connected fine.
However there is no helm value setting to allow you to set REDIS_SSL = True, and it affect the way superset connects to the rredis cache, which I think would only need ", ssl=true" apending to the redis connection string.
#### How to reproduce the bug
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
### Expected results
what you expected to happen.
### Actual results
what actually happens.
#### Screenshots
If applicable, add screenshots to help explain your problem.
### Environment
(please complete the following information):
- browser type and version:
- superset version: `superset version`
- python version: `python --version`
- node.js version: `node -v`
- any feature flags active:
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- [ ] I have reproduced the issue with at least the latest released version of superset.
- [ ] I have checked the issue tracker for the same issue and I haven't found one similar.
### Additional context
Add any other context about the problem here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Installing latest superset via helm, cant connect to azure redis service via ssl [superset]
Posted by "sfirke (via GitHub)" <gi...@apache.org>.
sfirke commented on issue #25375:
URL: https://github.com/apache/superset/issues/25375#issuecomment-1898501780
Thanks @shakeelansari63 ! @manneym would you be able to test a fix once Shakeel shares it?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] manneym commented on issue #25375: Installing latest superset via helm, cant connect to azure redis service via ssl
Posted by "manneym (via GitHub)" <gi...@apache.org>.
manneym commented on issue #25375:
URL: https://github.com/apache/superset/issues/25375#issuecomment-1731821607
I posted this whilst waiting to give blood, so unfortunately don't have all the other info the template asks to include... Will try and do that when I am back at work, however I don't think it matters... if you are connecting to a redis server that only accepts ssl connections, I think the result will be the same
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Installing latest superset via helm, cant connect to azure redis service via ssl [superset]
Posted by "shakeelansari63 (via GitHub)" <gi...@apache.org>.
shakeelansari63 commented on issue #25375:
URL: https://github.com/apache/superset/issues/25375#issuecomment-2049072381
> I'm having an issue similar to @manneym. I'm upgrading to 3.1.1, from 2.1.0. Deploy through Helm chart version 0.12.7.
>
> Connection to Azure Cache for Redis now fails with error: **Invalid SSL Certificate Requirements Flag: CERT_NONE**
>
> Optional CERT flag also fails.
>
> My `values.yaml` looks something like this:
>
> ```yaml
> connections:
> # Change in case of bringing your own redis and then also set redis.enabled:false
> redis_host: "XXX"
> redis_port: "6380"
> redis_ssl:
> enabled: true
> ssl_cert_reqs: CERT_NONE
> ```
That's strange. It was working for me. Can you try this -
```yaml
redia_ssl:
enabled: true
ssl_cert_reqs: none
```
Or `ssl_cert_reqs: None`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Installing latest superset via helm, cant connect to azure redis service via ssl [superset]
Posted by "shakeelansari63 (via GitHub)" <gi...@apache.org>.
shakeelansari63 commented on issue #25375:
URL: https://github.com/apache/superset/issues/25375#issuecomment-1898494452
I can help update the help chart to include options for Redis SSL. Will submit the PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] sfirke commented on issue #25375: Installing latest superset via helm, cant connect to azure redis service via ssl
Posted by "sfirke (via GitHub)" <gi...@apache.org>.
sfirke commented on issue #25375:
URL: https://github.com/apache/superset/issues/25375#issuecomment-1731949400
Thanks for this GitHub issue - and for donating blood 🩸
On the one hand, the Helm / Kubernetes workflow is not officially part of the Superset project as I understand it, more of a community-supported thing. So I'm not sure this is a Superset bug per se. That said, that deployment route is important and widely used, and it would be good if this was supported.
Are you able to contribute a fix? If not, you could try the #helm-k8-deployment channel on the Superset Slack and see if anyone has advice or can modify the chart.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Installing latest superset via helm, cant connect to azure redis service via ssl [superset]
Posted by "shakeelansari63 (via GitHub)" <gi...@apache.org>.
shakeelansari63 commented on issue #25375:
URL: https://github.com/apache/superset/issues/25375#issuecomment-1898615954
Hey Guys, I have updated the Helm on MR # 26663. Need someone to test the updated chart.
@manneym , would you be able to test the updated chart?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Installing latest superset via helm, cant connect to azure redis service via ssl [superset]
Posted by "simaolucio (via GitHub)" <gi...@apache.org>.
simaolucio commented on issue #25375:
URL: https://github.com/apache/superset/issues/25375#issuecomment-2048236099
I'm having an issue similar to @manneym. I'm upgrading to 3.1.1, from 2.1.0. Deploy through Helm chart version 0.12.7.
Connection to Azure Cache for Redis now fails with error: **Invalid SSL Certificate Requirements Flag: CERT_NONE**
Optional CERT flag also fails
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org