We just installed dremio following the documentation.
helm install dremio dremio_v2/ -f values-override.yaml
Then we created an ingress expose dremio.
But when we try to access the dremio on the browser, we go directly to login page and skipped the user setup.
We have reinstalled several times and cleared all pvc and pv but still the same.
Anything wrong with what we are doing?
ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod-route53
external-dns.alpha.kubernetes.io/hostname: dremio.dev.domain.com
name: dremio-ingress
spec:
ingressClassName: nginx
rules:
- host: dremio.dev.domain.com
http:
paths:
- backend:
service:
name: dremio-client
port:
number: 9047
path: /
pathType: Prefix
tls:
- hosts:
- dremio.dev.domain.com
secretName: dremio-tls
values-override.yaml
# The Dremio image used in the cluster.
#
# It is *highly* recommended to update the version tag to
# the version that you are using. This will ensure that all
# the pods are using the same version of the software. If
# you are directly consuming Dremio's images from Docker Hub,
# when specifying which version to use, it is best to use the
# full version tag in the form X.Y.Z (i.e. 21.1.0), as image
# tags in the form X.Y (i.e. 21.1) are updated with the latest
# patch version released.
#
# Using the image tag latest or in the form X.Y
# will potentially cause Dremio to upgrade versions
# automatically during redeployments and may negatively impact
# the cluster.
image: dremio/dremio-oss
imageTag: latest
# Annotations, labels, node selectors, and tolerations
#
# annotations: Annotations are applied to the StatefulSets that are deployed.
# podAnnotations: Pod annotations are applied to the pods that are deployed.
# labels: Labels operate much like annotations.
# podLabels: Labels that are applied to the pods that are deployed.
# nodeSelector: Target pods to nodes based on labels set on the nodes. For more
# information, see https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
# tolerations: Tolerations allow the negation of taints that have been applied to some set of nodes
# in the Kubernetes cluster so that pods can be scheduled on those tainted nodes.
annotations: {}
podAnnotations: {}
labels: {}
podLabels: {}
nodeSelector:
karpenter.sh/nodepool: rda-dev-pool
tolerations:
- effect: NoSchedule
key: repository.com/rda-dev
operator: Exists
# Dremio Coordinator
coordinator:
# CPU & Memory
# Memory allocated to each coordinator, expressed in MB.
# CPU allocated to each coordinator, expressed in CPU cores.
cpu: 1
memory: 4096
# This count is used for slave coordinators only.
# The total number of coordinators will always be count + 1.
# If this is greater than zero then the client and flight ports on the master
# will be deactivated to steer these requests away from the master node.
count: 1
# Coordinator data volume size (applies to the master coordinator only).
# In most managed Kubernetes environments (AKS, GKE, etc.), the size of the disk has a direct impact on
# the provisioned and maximum performance of the disk.
volumeSize: 100Gi
# Kubernetes Service Account
# Uncomment below to use a custom Kubernetes service account for the coordinator.
#serviceAccount: ""
# Uncomment the lines below to use a custom set of extra startup parameters for the coordinator.
#extraStartParams: >-
# -DsomeKey=someValue
# Extra Init Containers
# Uncomment the below lines to use a custom set of extra init containers for the coordinator.
#extraInitContainers: |
# - name: extra-init-container
# image: {{ $.Values.image }}:{{ $.Values.imageTag }}
# command: ["echo", "Hello World"]
# Extra Volumes
# Uncomment below to use a custom set of extra volumes for the coordinator.
#extraVolumes: []
# Extra Volume Mounts
# Uncomment below to use a custom set of extra volume mounts for the coordinator.
#extraVolumeMounts: []
# Extra Environment Variables
# Uncomment below to add extra environment variables for the coordinator.
#extraEnvs: []
# Uncomment this value to use a different storage class for the coordinator.
storageClass: gp2
# Uncomment this value to use a different storage class for the coordinator logs.
#logStorageClass:
# Whether to write coordinator logs to a file on disk. Disabled by default.
# When enabled, log messages are logged to the console and written to a persistent volume mounted at /opt/dremio/log.
# When disabled, log messages are logged to the console only.
#writeLogsToFile: true
# These values, when defined, override the provided shared annotations, labels, node selectors, or tolerations.
# Uncomment only if you are trying to override the chart's shared values.
#annotations: {}
#podAnnotations: {}
#labels: {}
#podLabels: {}
#nodeSelector: {}
#tolerations: []
# Web UI
web:
port: 9047
tls:
# To enable TLS for the web UI, set the enabled flag to true and provide
# the appropriate Kubernetes TLS secret.
enabled: false
# To create a TLS secret, use the following command:
# kubectl create secret tls ${TLS_SECRET_NAME} --key ${KEY_FILE} --cert ${CERT_FILE}
secret: dremio-tls-secret-ui
# ODBC/JDBC Client
client:
port: 31010
tls:
# To enable TLS for the client endpoints, set the enabled flag to
# true and provide the appropriate Kubernetes TLS secret. Client
# endpoint encryption is available only on Dremio Enterprise
# Edition and should not be enabled otherwise.
enabled: false
# To create a TLS secret, use the following command:
# kubectl create secret tls ${TLS_SECRET_NAME} --key ${KEY_FILE} --cert ${CERT_FILE}
secret: dremio-tls-secret-client
# Flight Client
flight:
port: 32010
tls:
# To enable TLS for the Flight endpoints, set the enabled flag to
# true and provide the appropriate Kubernetes TLS secret.
enabled: false
# To create a TLS secret, use the following command:
# kubectl create secret tls ${TLS_SECRET_NAME} --key ${KEY_FILE} --cert ${CERT_FILE}
secret: dremio-tls-secret-flight
# Startup Probe
startupProbe:
# Max timeout for the probe is calculated as failureThreshold * periodSeconds
# failureThreshold: Maximum number of allowed failures
failureThreshold: 300
# periodSeconds: Polling frequency expressed in seconds
periodSeconds: 1
# Readiness Probe
readinessProbe:
# Max timeout for the probe is calculated as failureThreshold * periodSeconds
# failureThreshold: Maximum number of allowed failures
failureThreshold: 120
# periodSeconds: Polling frequency expressed in seconds
periodSeconds: 1
# Dremio Executor
executor:
# CPU & Memory
# Memory allocated to each executor, expressed in MB.
# CPU allocated to each executor, expressed in CPU cores.
cpu: 0.5
memory: 4096
# Engines
# Engine names be 47 characters or less and be lowercase alphanumber characters or '-'.
# Note: The number of executor pods will be the length of the array below * count.
engines: ["default"]
count: 3
# Executor volume size.
volumeSize: 128Gi
# Kubernetes Service Account
# Uncomment below to use a custom Kubernetes service account for executors.
#serviceAccount: ""
# Uncomment the lines below to use a custom set of extra startup parameters for executors.
#extraStartParams: >-
# -DsomeKey=someValue
# Extra Init Containers
# Uncomment the below lines to use a custom set of extra init containers for executors.
#extraInitContainers: |
# - name: extra-init-container
# image: {{ $.Values.image }}:{{ $.Values.imageTag }}
# command: ["echo", "Hello World"]
# Extra Volumes
# Uncomment below to use a custom set of extra volumes for executors.
#extraVolumes: []
# Extra Volume Mounts
# Uncomment below to use a custom set of extra volume mounts for executors.
#extraVolumeMounts: []
# Extra Environment Variables
# Uncomment below to add extra environment variables for the executors.
#extraEnvs: []
# Uncomment this value to use a different storage class for executors.
storageClass: gp2
# Uncomment this value to use a different storage class for the executor logs.
#logStorageClass:
# Whether to write executor logs to a file on disk. Disabled by default.
# When enabled, log messages are logged to the console and written to a persistent volume mounted at /opt/dremio/log.
# When disabled, log messages are logged to the console only.
#writeLogsToFile: true
# Dremio C3
# Designed for use with NVMe storage devices, performance may be impacted when using
# persistent volume storage that resides far from the physical node.
cloudCache:
enabled: true
# Uncomment this value to use a different storage class for C3.
storageClass: gp2
# Volumes to use for C3, specify multiple volumes if there are more than one local
# NVMe disk that you would like to use for C3.
#
# The below example shows all valid options that can be provided for a volume.
# volumes:
# - name: "dremio-default-c3"
# size: 100Gi
# storageClass: "local-nvme"
volumes:
- size: 100Gi
# These values, when defined and not empty, override the provided shared annotations, labels, node selectors, or tolerations.
# Uncomment only if you are trying to override the chart's shared values.
#annotations: {}
#podAnnotations: {}
#labels: {}
#podLabels: {}
#nodeSelector: {}
#tolerations: []
# DEPRECATION NOTICE: The nodeLifecycleService feature has been deprecated and is no longer supported.
# By default, the number of Engines is static. Enable the Node Lifecycle Service
# to enable dynamic scaling.
# nodeLifecycleService:
# enabled: true
# scalingMetrics:
# default:
# enabled: true
# scalingBehavior:
# scaleDown:
# defaultPolicy:
# enabled: true
# scaleUp:
# defaultPolicy:
# enabled: true
# Engine Overrides
#
# The settings above are overridable on a per-engine basis. These
# values here will take precedence and *override* the configured values
# on a per-engine basis. Engine overrides are matched with the name in the above
# list of engines.
#
# Special per-engine parameters:
# volumeClaimName: For each engine, you can optionally specify a value for the volume claim name,
# this value must be unique to each engine or may cause unintended consequences. This value is
# primarily intended for transitioning an existing single engine to a multi-engine configuration
# where there may already have been existing persistent volumes.
#
# The below example shows all valid options that can be overridden on a per-engine basis.
# engineOverride:
# engineNameHere:
# cpu: 1
# memory: 122800
#
# count: 1
#
# annotations: {}
# podAnnotations: {}
# labels: {}
# podLabels: {}
# nodeSelector: {}
# tolerations: []
#
# nodeLifecycleService:
# enabled: true
# scalingMetrics:
# default:
# enabled: true
# scalingBehavior:
# scaleDown:
# defaultPolicy:
# enabled: true
# scaleUp:
# defaultPolicy:
# enabled: true
#
# serviceAccount: ""
#
# extraStartParams: >-
# -DsomeCustomKey=someCustomValue
#
# extraInitContainers: |
# - name: extra-init-container
# image: {{ $.Values.image }}:{{ $.Values.imageTag }}
# command: ["echo", "Hello World"]
#
#
# extraVolumes: []
# extraVolumeMounts: []
# extraEnvs: []
#
# volumeSize: 50Gi
# storageClass: managed-premium
# logStorageClass: ""
# volumeClaimName: dremio-default-executor-volume
#
# cloudCache:
# enabled: true
#
# storageClass: ""
#
# volumes:
# - name: "default-c3"
# size: 100Gi
# storageClass: ""
# Zookeeper
zookeeper:
# The Zookeeper image used in the cluster.
image: zookeeper
imageTag: 3.8.4-jre-17
# CPU & Memory
# Memory allocated to each zookeeper, expressed in MB.
# CPU allocated to each zookeeper, expressed in CPU cores.
cpu: 0.2
memory: 1024
count: 3
volumeSize: 10Gi
# Kubernetes Service Account
# Uncomment below to use a custom Kubernetes service account for Zookeeper.
#serviceAccount: ""
# Uncomment this value to use a different storage class for Zookeeper.
storageClass: gp2
# These values, when defined, override the provided shared annotations, labels, node selectors, or tolerations.
# Uncomment only if you are trying to override the chart's shared values.
#annotations: {}
#podAnnotations: {}
#labels: {}
#podLabels: {}
#nodeSelector: {}
#tolerations: []
# Control where uploaded files are stored for Dremio.
# For more information, see https://docs.dremio.com/deployment/distributed-storage.html
distStorage:
# The supported distributed storage types are: local (<21.0.0 only), aws, azure, gcp, or azureStorage.
#
# local: (<21.0.0 only) Not recommended for production use. When using local, dist-caching is disabled.
# aws: AWS S3, additional parameters required, see "aws" section.
# azure: ADLS Gen 1, additional parameters required, see "azure" section.
# azureStorage: Azure Storage Gen2, additional parameters required, see "azureStorage" section.
# gcp: Google Cloud Storage, additional parameters required, see "gcp" section.
type: "aws"
# AWS S3
# For more details of S3 configuration, see https://docs.dremio.com/deployment/dist-store-config.html#amazon-s3
#
# bucketName: The name of the S3 bucket for distributed storage.
# path: The path, relative to the bucket, to create Dremio's directories.
# authentication: Valid types are: accessKeySecret, instanceMetadata, or awsProfile.
# - Note: Instance metadata is only supported in AWS EKS and requires that the
# EKS worker node IAM role is configured with sufficient access rights. At this time,
# Dremio does not support using an K8s service account based IAM role.
# credentials: If using accessKeySecret authentication, uncomment the credentials section below.
aws:
bucketName: "dremio-bucket-dev"
path: "/"
authentication: "accessKeySecret"
# If using accessKeySecret for authentication against S3, uncomment the lines below and use the values
# to configure the appropriate credentials.
#
credentials:
accessKey: "SOME_KEY"
secret: "SOME_BUCKET"
#
# If using awsProfile for authentication against S3, uncomment the lines below and use the values
# to choose the appropriate profile.
#
#credentials:
# awsProfileName: "default"
#
# Extra Properties
# Use the extra properties block to provide additional parameters to configure the distributed
# storage in the generated core-site.xml file.
#
#extraProperties: |
# <property>
# <name></name>
# <value></value>
# </property>
service:
type: ClusterIP