installation error within namespace with istio-injection enabled and helm flags atomic, cleanup_on_fail about contrib-helm-chart

[daddydrac]

Then next time don’t let me my questions go stale or close them out, and I won’t have to tag ppl or post on other questions. And I support my GitHub repos and help ppl and give advice. When you don’t have good enough docs that’s not my problem. You should make them in the README.md, simply deploying it is not adequate. A simple explain toon of set up, setting ndoePort when you randomly generate one, things like that. Regardless, I got it going but not really impressed with how I was initially treated which was rude. 👌🏼

…

On Fri, Jan 15, 2021 at 2:56 PM Arik Fraimovich ***@***.***> wrote: @joehoeller <https://github.com/joehoeller> its not being rude when there is no documentation for basic things ppl would want to do It is being rude when a person asks you to stop tagging them but you keep doing it. It's also rude to post irrelevant comments on other people's issues. If you don't get a reply, it doesn't mean you should keep pestering but rather wait patiently or try to resolve yourself. This specific repo (the Helm chart) is being maintained by @grugnog <https://github.com/grugnog> and a few others. The chart itself is a big effort they are doing out of their kindness. They don't owe support to anyone as you don't have to use it. I'll really appreciate if you show a bit more respect and understanding towards the people working on free software you use. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHVQHAYADCATF43LL3JEJ3S2CTZPANCNFSM4R4VGCBA> .

[daddydrac]

Stela - I’ll post the config you need in values.yaml shortly.

…

On Wed, Jan 20, 2021 at 7:48 AM Stela L. ***@***.***> wrote: Hey there, I am having the same problem, i deployed the Redash through Helm, kept the basic configuration. I am using the internal redis, looking at the kube-dashboard I get — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHVQHAW3DIWOXPCCZXFWV3S23NKNANCNFSM4R4VGCBA> .

[grugnog]

@aakashRajur thanks for noting this issue - I would be OK adding annotations to the hook jobs, if you would in interested in submitting a PR for that change. For standardization we could add the standard block of pod configurations (resources, security contexts etc) we use for workers etc.

[daddydrac]

@aakashRajur how are you setting up your values.yaml? I am getting a lot of errors, one being it cannot connect to redis.

[aakash-rajur]

@joehoeller, this was my working configuration, for following versions,

• gke version: ~1.17
• chart version: 2.0.0
• istio version: 1.7.4

## Service account and security context configuration
serviceAccount:
  # serviceAccount.create -- Specifies whether a service account should be created
  create: true
  # serviceAccount.annotations -- Annotations to add to the service account
  annotations: {}
  # serviceAccount.name -- The name of the service account to use. If not set and create is true, a name is generated using the fullname template
  name:

## Redash application configuration
redash:
  ## Start primary Redash configuration
  # redash.secretKey -- REQUIRED `REDASH_SECRET_KEY` value. Defaults to ``. Secret key used for data encryption. Stored as a Secret value.
  secretKey: FAKE_SECRET_KEY
  # redash.proxiesCount -- `REDASH_PROXIES_COUNT` value. Defaults to `1`.
  googleClientId: FAKE_GOOGLE_CLIENT_ID
  # redash.googleClientSecret -- `REDASH_GOOGLE_CLIENT_SECRET` value. Defaults to ``. Stored as a Secret value.
  googleClientSecret: FAKE_CLIENT_SECRET

## Configuration for Redash web server
server:
  # server.httpPort -- Server container port (only useful if you are using a customized image)
  httpPort: 5000

  # server.env -- Redash server specific envrionment variables
  # Don't use this for variables that are in the configuration above, however.
  env: {}

  # server.replicaCount -- Number of server pods to run
  replicaCount: 1

  # server.resources -- Server resource requests and limits [ref](http://kubernetes.io/docs/user-guide/compute-resources/)
  resources:
    limits:
      cpu: 1000m
      memory: 2Gi
    requests:
      cpu: 500m
      memory: 500Mi

  # server.affinity -- Affinity for server pod assignment [ref](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity)
  affinity:
    nodeAffinity:
      preferredDuringSchedulingIgnoredDuringExecution:
        - preference:
            matchExpressions:
              - key: preemptive
                operator: NotIn
                values:
                  - "true"
          weight: 100

  # server.podAnnotations -- Annotations for server pod assignment [ref](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/)
  podAnnotations:
    sidecar.istio.io/inject: "true"

service:
  # service.type -- Kubernetes Service type
  type: ClusterIP
  # service.port -- Service external port
  port: 80

ingress:
  # ingress.enabled -- Enable ingress controller resource
  enabled: false

## Configuration for Redash ad-hoc workers
adhocWorker:
  # adhocWorker.env -- Redash ad-hoc worker specific envrionment variables.
  env:
    QUEUES: "queries,celery"
    WORKERS_COUNT: 2

  # adhocWorker.replicaCount -- Number of ad-hoc worker pods to run
  replicaCount: 1

  # adhocWorker.resources -- Ad-hoc worker resource requests and limits [ref](http://kubernetes.io/docs/user-guide/compute-resources/)
  resources:
    limits:
      cpu: 500m
      memory: 2Gi
    requests:
      cpu: 100m
      memory: 500Mi

  # adhocWorker.affinity -- Affinity for ad-hoc worker pod assignment [ref](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity)
  affinity:
    nodeAffinity:
      preferredDuringSchedulingIgnoredDuringExecution:
        - preference:
            matchExpressions:
              - key: preemptive
                operator: In
                values:
                  - "true"
          weight: 100

  # adhocWorker.podAnnotations -- Annotations for adhoc worker pod assignment [ref](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/)
  podAnnotations:
    sidecar.istio.io/inject: "true"

## Configuration for Redash scheduled workers
scheduledWorker:
  # scheduledWorker.env -- Redash scheduled worker specific envrionment variables.
  env:
    QUEUES: "scheduled_queries"
    WORKERS_COUNT: 2

  # scheduledWorker.replicaCount -- Number of scheduled worker pods to run
  replicaCount: 1

  # scheduledWorker.resources -- Scheduled worker resource requests and limits [ref](http://kubernetes.io/docs/user-guide/compute-resources/)
  resources:
    limits:
      cpu: 500m
      memory: 2Gi
    requests:
      cpu: 100m
      memory: 500Mi

  # scheduledWorker.affinity -- Affinity for scheduled worker pod assignment [ref](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity)
  affinity:
    nodeAffinity:
      preferredDuringSchedulingIgnoredDuringExecution:
        - preference:
            matchExpressions:
              - key: preemptive
                operator: In
                values:
                  - "true"
          weight: 100

  # scheduledWorker.podAnnotations -- Annotations for scheduled worker pod assignment [ref](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/)
  podAnnotations:
    sidecar.istio.io/inject: "true"

# externalPostgreSQL -- External PostgreSQL configuration. To use an external PostgreSQL instead of the automatically deployed postgresql chart: set postgresql.enabled to false then uncomment and configure the externalPostgreSQL connection URL.
# externalPostgreSQL: "postgres://localhost:5432/redash"

## Configuration values for the postgresql dependency. This PostgreSQL instance is used by default for all Redash state storage [ref](https://github.com/kubernetes/charts/blob/master/stable/postgresql/README.md)
postgresql:
  # postgresql.enabled -- Whether to deploy a PostgreSQL server to satisfy the applications database requirements. To use an external PostgreSQL set this to false and configure the externalPostgreSQL parameter.
  enabled: true
  image:
    # postgresql.image.tag -- Bitnami supported version close to the one specified in Redash [setup docker-compose.yml](https://github.com/getredash/setup/blob/master/data/docker-compose.yml)
    tag: "9.6.17-debian-10-r3"
  # postgresql.postgresqlUsername -- PostgreSQL username for redash user (when postgresql chart enabled)
  postgresqlUsername: redash
  # postgresql.postgresqlPassword -- REQUIRED: PostgreSQL password for redash user (when postgresql chart enabled)
  postgresqlPassword: FAKE_PASSWORD
  # postgresql.postgresqlDatabase -- PostgreSQL database name (when postgresql chart enabled)
  postgresqlDatabase: redash
  service:
    type: ClusterIP
    port: 5432
  persistence:
    # postgresql.persistence.enabled -- Use a PVC to persist PostgreSQL data (when postgresql chart enabled)
    enabled: true
    # postgresql.persistence.storageClass - Storage Class for PostgreSQL backing PVC. If undefined (the default) or set to null, no storageClassName spec is set, choosing the default provisioner.  (gp2 on AWS, standard on GKE, AWS & OpenStack).
    storageClass: ""
    # postgresql.persistence.accessMode -- Use PostgreSQL volume as ReadOnly or ReadWrite
    accessMode: ReadWriteOnce
    # postgresql.persistence.size -- PVC Storage Request size for PostgreSQL volume
    size: 10Gi
    # postgresql.persistence.existingClaim -- Provide an existing PostgreSQL PersistentVolumeClaim
    # existingClaim: ""

# externalRedis -- External Redis configuration. To use an external Redis instead of the automatically deployed redis chart: set redis.enabled to false then uncomment and configure the externalRedis connection URL.
# externalRedis: redis://user:pass@host:6379/database

## Configuration values for the redis dependency. This Redis instance is used by default for caching and temporary storage [ref](https://github.com/kubernetes/charts/blob/master/stable/redis/README.md)
redis:
  # redis.enabled -- Whether to deploy a Redis server to satisfy the applications database requirements. To use an external Redis set this to false and configure the externalRedis parameter.
  enabled: true
  # redis.password -- If the password is not specified, a random password will be generated (when redis chart enabled)
  # password:
  # redis.databaseNumber -- Redis database number to use (when redis chart enabled)
  databaseNumber: 0
  master:
    # redis.master.port -- Redis master port to use (when redis chart enabled)
    port: 6379
    resources:
      limits:
        cpu: 200m
        memory: 512Mi
      requests:
        cpu: 100m
        memory: 256Mi
    affinity:
      nodeAffinity:
        preferredDuringSchedulingIgnoredDuringExecution:
          - preference:
              matchExpressions:
                - key: preemptive
                  operator: In
                  values:
                    - "true"
            weight: 100
  cluster:
    # redis.databaseNumber -- Enable Redis clustering (when redis chart enabled)
    enabled: false

[daddydrac]

why cant anyone answer any question here?

id also like to know where am i supposed to set the nodePort just so i can access the UI, honestly the delays in ans. ques. on this project are irritating. i support all my github repos - why cant you??? @arikfr @jezdez @grugnog

Anytime I try and do an upgrade or change settings I get:

Failed to install app redash. Error: failed post-install: timed out waiting for the condition

[jezdez]

why cant anyone answer any question here?

id also like to know where am i supposed to set the nodePort just so i can access the UI, honestly the delays in ans. ques. on this project are irritating. i support all my github repos - why cant you??? @arikfr @jezdez

@joehoeller First, please be so kind and stop being rude to people here. I'm a volunteer working at a different company than Redash and am not a support contact.

Secondly, you've tagged me before in a different issue and I said this there already: I can't help you since I've never worked on this repo and have never used it. Why are you continuing to do that?

@arikfr Please clarify what it means that this is a "community project" (like it is mentioned in the README, @joehoeller). Or move this elsewhere outside the redash org.

[daddydrac]

@jezdez its not being rude when there is no documentation for basic things ppl would want to do, especially when no one ever asks the most simple questions. All they have to do is just say ok, here is the values in values.yaml you need for X.

[daddydrac]

Also getting this from redis:

File "/usr/local/lib/python2.7/site-packages/redis/connection.py", line 642, in read_response
    raise response
ResponseError: WRONGPASS invalid username-password pair

[aakash-rajur]

@joehoeller, let's break down your problem, right?

1. this issue is very specific with the said title, I'm not sure if your comments belong specifically here and it is of my opinion that you should file a new issue in this repo or any other relevant place.
2. everything worked fine deploying it with provided values.yaml in my earlier comment.
3. please provide your deployment context, assuming you're using this chart for your redash deployment
   a. are you using an existing/managed redis instance.
   b. does that redis deployment if preexistent have credentials
   c. have you provided those credentials in your deployment values.yaml
   d. link, the exact place to override for an existing redis instance
4. if possible we should move comments related to your issue to other relevant place as this problem is not related to the title of this issue and could confuse future contributors and users

Hope I've been helpful

[daddydrac]

I eventually got it to work and I placed it here bc my other ques never got answered. Now, what would be nice is if you could tell me how to provide a static nodePort for the UI, and not have some random one. I did try adding nodePort: 30000 in services, but I got an install error.

…

On Wed, Jan 13, 2021 at 1:17 AM Aakash Rajur ***@***.***> wrote: @joehoeller <https://github.com/joehoeller>, let's break down your problem, right? 1. this issue is very specific with the said title, I'm not sure if your comments belong specifically here and it is of my opinion that you should file a new issue in this repo or any other relevant place. 2. everything worked fine deploying it with provided values.yaml in my earlier comment. 3. please provide your deployment context, assuming you're using this chart for your redash deployment a. are you using an existing/managed redis instance. b. does that redis deployment if preexistent have credentials c. have you provided those credentials in your deployment values.yaml <https://github.com/getredash/contrib-helm-chart/blob/43c58db822567d5fa956d5826510b0be672adfdc/values.yaml#L458> d. link <https://github.com/getredash/contrib-helm-chart/blob/43c58db822567d5fa956d5826510b0be672adfdc/values.yaml#L458>, the exact place to override for an existing redis instance 4. if possible we should move comments related to your issue to other relevant place as this problem is not related to the title of this issue and could confuse future contributors and users Hope I've been helpful — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHVQHESE3XRECCCBOXJE23SZVCJZANCNFSM4R4VGCBA> .

[arikfr]

@joehoeller

its not being rude when there is no documentation for basic things ppl would want to do

It is being rude when a person asks you to stop tagging them but you keep doing it. It's also rude to post irrelevant comments on other people's issues. If you don't get a reply, it doesn't mean you should keep pestering but rather wait patiently or try to resolve yourself.

This specific repo (the Helm chart) is being maintained by @grugnog and a few others. The chart itself is a big effort they are doing out of their kindness. They don't owe support to anyone as you don't have to use it.

I'll really appreciate if you show a bit more respect and understanding towards the people working on free software you use.

[stela-leon]

Hey there,
I am having the same problem, i deployed the Redash through Helm, kept the basic configuration. I am using the internal redis, looking at the kube-dashboard I get
Failed to install app redash. Error: failed post-install: timed out waiting for the condition and from the redash-tool logs (the rest of the pods seem to complete fine): ConnectionError: Error 111 connecting to redash-tool-redis-master:6379. Connection refused. [2021-01-20 13:48:51,071] ERROR in app: Exception on /ping [GET]
the configuration seems fine in the config-map:
REDASH_REDIS_HOSTNAME
public
redash-tool-redis-master << which I assume it's where it tries to connects. Although I am confused by this env variable, why am i having it inside the pod : REDASH_TOOL_REDIS_MASTER_SERVICE_HOST= some IP (just a curiosity)?

Any help is highly appreciated,
Cheers!

[stela-leon]

@joehoeller Sure :) Thank you.