You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I am trying to install redash with the helm chart via Terraform on our corporate cluster.
I've read that the inital deployment takes a bit and also let it run for over a few hours but still no luck.
Locally my setup runs fine. Only on the corporate cluster it fails somehow.
1.) I am suspecting that there is somekind of proxy-hick-up that is why I disabled most of the query_runner & destination this at least reduced that amound of WORKER TIMEOUT inside redash itself. But finally didn't solve my problem.
2.) What also is kind of weird is that I get an redash-redis-master connection refused. altough it is reachable within the k8s network.
I'm happy for any help.
What I've already tried:
Deactivate Liveness/Readyness Probe: Pods are green but nothing is reachable ending up, that the setup is dead.
Giving the setup a http_proxy/https_proxy/no_proxy via the env
[2022-06-30 08:41:48,921][PID:6][ERROR][MainProcess] consumer: Cannot connect to redis://:**@redash-redis-master:6379/0: Error 110 connecting to redash-redis-master:6379. Connection timed out..
Trying again in 6.00 seconds...
[2022-06-30 08:41:48,918][PID:6][ERROR][MainProcess] consumer: Cannot connect to redis://:**@redash-redis-master:6379/0: Error 110 connecting to redash-redis-master:6379. Connection timed out..
Trying again in 6.00 seconds...
[2022-06-30 08:42:13,493][PID:11][ERROR][Beat] beat: Connection error: Error 110 connecting to redash-redis-master:6379. Connection timed out.. Trying again in 2.0 seconds...
Here are my settings.
main.tf
resource "helm_release" "redash" {
name = "redash"
repository = "https://getredash.github.io/contrib-helm-chart/"
chart = "redash"
version = "3.0.0"
namespace = "dev"
set {
name = "postgresql.postgresqlPassword"
value = "password123verystrong"
}
set {
name = "redash.cookieSecret"
value = "secret"
}
set {
name = "redash.secretKey"
value = "key"
}
set {
name = "image.tag"
value = "latest"
}
set {
name = "postgresql.image.repository"
value = "bitnami/postgresql"
}
set {
name = "postgresql.image.tag"
value = "9.6.17-debian-10-r3"
}
set {
name = "redis.image.repository"
value = "bitnami/redis"
}
set {
name = "redis.image.tag"
value = "6.0.8-debian-10-r0"
}
set {
name = "server.podSecurityContext.runAsNonRoot"
value = true
}
set {
name = "server.podSecurityContext.runAsUser"
value = 1000
}
set {
name = "adhocWorker.podSecurityContext.runAsNonRoot"
value = true
}
set {
name = "adhocWorker.podSecurityContext.runAsUser"
value = 1000
}
set {
name = "scheduledWorker.podSecurityContext.runAsNonRoot"
value = true
}
set {
name = "scheduledWorker.podSecurityContext.runAsUser"
value = 1000
}
set {
name = "scheduler.podSecurityContext.runAsNonRoot"
value = true
}
set {
name = "scheduler.podSecurityContext.runAsUser"
value = 1000
}
set {
name = "genericWorker.podSecurityContext.runAsNonRoot"
value = true
}
set {
name = "genericWorker.podSecurityContext.runAsUser"
value = 1000
}
set {
name = "hookInstallJob.podSecurityContext.runAsNonRoot"
value = true
}
set {
name = "hookInstallJob.podSecurityContext.runAsUser"
value = 1000
}
set {
name = "hookUpgradeJob.podSecurityContext.runAsNonRoot"
value = true
}
set {
name = "hookUpgradeJob.podSecurityContext.runAsUser"
value = 1000
}
set {
name = "ingress.enabled"
value = "true"
}
set {
name = "ingress.hosts[0].host"
value = "someurl"
}
set {
name = "ingress.hosts[0].paths[0]"
value = "/"
}
set {
name = "ingress.annotations.traefik\\.ingress\\.kubernetes\\.io\\/router\\.tls"
value = "true"
type = "string"
}
set {
name = "redash.enabledQueryRunners"
value = "redash.query_runner.pg"
}
set {
name = "redash.enabledDestinations"
value = "redash.destinations.mattermost"
}
}
The text was updated successfully, but these errors were encountered:
@Rusiecki nothing really from the above - it seems like a cluster network issue of some kind, but I can't come up with any ideas from the information above, particularly if the same config works locally. My guess is that there is some additional network layer or policy enforcement on the corporate cluster that is denying the connection?
Hello,
I am trying to install
redash
with thehelm chart
viaTerraform
on ourcorporate cluster
.I've read that the inital deployment takes a bit and also let it run for over a few hours but still no luck.
Locally my setup runs fine. Only on the
corporate cluster
it fails somehow.1.) I am suspecting that there is somekind of proxy-hick-up that is why I disabled most of the
query_runner
&destination
this at least reduced that amound ofWORKER TIMEOUT
inside redash itself. But finally didn't solve my problem.2.) What also is kind of weird is that I get an redash-redis-master connection refused. altough it is reachable within the k8s network.
I'm happy for any help.
What I've already tried:
Liveness/Readyness Probe
: Pods are green but nothing is reachable ending up, that the setup is dead.http_proxy/https_proxy/no_proxy
via theenv
Here are the logs of the pods if it helps:
Logs(dev/redash-adhocworker-7b59b97db6-ldggj:redash-adhocworker)[1m]
Logs(dev/redash-c5bbb5cc4-d9gj9:redash-server)[1m]
Logs(dev/redash-genericworker-65bb9df79d-tt8kw:redash-genericworker)[1m]
Logs(dev/redash-scheduledworker-5dc5c9c89f-mm8qf:redash-scheduledworker)[1m]
Logs(dev/redash-scheduler-7b5865c4-sbsfj:redash-scheduler)[1m]
Here are my settings.
main.tf
The text was updated successfully, but these errors were encountered: