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
I am using the values.yaml file to deploy akqh, but the error 404 occurs when trying to access it from dns or lb endpoint, and some attempts the screen is blank, that is, the login screen for access does not appear and also There are no log messages that help in this tshoot, could you please help me to answer what I am doing wrong?
to know: Pods running, ingress , svc, sa, role, sg's, all created
# imagePullSecrets:
# - name: my-repository-secret
image:
repository: tchiotludo/akhq
tag: "" # uses Chart.AppVersion by default
# custom annotations (example: for prometheus)
annotations: {}
# prometheus.io/scrape: 'true'
# prometheus.io/port: '8080'
# prometheus.io/path: '/prometheus'
podAnnotations: {}
# custom labels
labels:
env: hom
podLabels:
env: hom
## You can put directly your configuration here... or add java opts or any other env vars
extraEnv: []
# - name: AKHQ_CONFIGURATION
# value: |
# akhq:
# secrets:
# docker-kafka-server:
# properties:
# bootstrap.servers: "kafka:9092"
# - name: JAVA_OPTS
# value: "-Djavax.net.ssl.trustStore=/opt/java/openjdk/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=password"
# - name: CLASSPATH
# value: "/any/additional/jars/desired.jar:/go/here.jar"
## Or you can also use configmap for the configuration...
configuration:
akhq:
server:
access-log:
enabled: false
name: org.akhq.log.access
logger:
levels:
root: DEBUG
org.akhq.configs: TRACE
io.micronaut.security: TRACE
existingSecrets: ""
# name of the existingSecret
#secrets: {}
kafkaSecrets: []
secrets:
akhq:
connections:
akhq-poc:
properties:
bootstrap.servers: kafka1:9098,kafka2:9098,kafka3:9098
security.protocol: SASL_SSL
sasl.mechanism: AWS_MSK_IAM
sasl.client.callback.handler.class: software.amazon.msk.auth.iam.IAMClientCallbackHandler
sasl.jaas.config: software.amazon.msk.auth.iam.IAMLoginModule required awsDebugCreds=true;
micronaut:
security:
enabled: true
token:
jwt:
signatures:
secret:
generator:
secret: *************
server:
host-resolution:
host-header: Host
protocol-header: X-Forwarded-Proto
# Any extra volumes to define for the pod (like keystore/truststore)
extraVolumes: []
# Any extra volume mounts to define for the akhq container
extraVolumeMounts: []
# Specify ServiceAccount for pod
serviceAccountName: akhq-role-sa
serviceAccount:
create: false
annotations:
eks.amazonaws.com/role-arn: arn:aws:iam::0000000000000:role/akhq-role
# Add your own init container or uncomment and modify the example.
initContainers: {}
# create-keystore:
# image: "eclipse-temurin:11-jre"
# command: ['sh', '-c', 'keytool']
# volumeMounts:
# - mountPath: /tmp
# name: certs
# Configure the Pod Security Context
# ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
securityContext: {}
# runAsNonRoot: true
# runAsUser: 1000
# Configure the Container Security Context
# ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
containerSecurityContext: {}
# allowPrivilegeEscalation: false
# privileged: false
# capabilities:
# drop:
# - ALL
# runAsNonRoot: true
# runAsUser: 1001
#readOnlyRootFilesystem: false
service:
enabled: true
type: ClusterIP
port: HTTP
managementPort: 28081
#httpNodePort: 32551
labels: {}
annotations:
# cloud.google.com/load-balancer-type: "Internal"
ingress:
enabled: true
#ingressClassName: alb
annotations:
alb.ingress.kubernetes.io/backend-protocol: HTTP
alb.ingress.kubernetes.io/certificate-arn: arn:aws:iam::**********:server-certificate/********
alb.ingress.kubernetes.io/healthcheck-interval-seconds: "5"
alb.ingress.kubernetes.io/healthcheck-path: /health
# alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS": 443}]'
alb.ingress.kubernetes.io/healthcheck-port: "28081"
alb.ingress.kubernetes.io/healthcheck-protocol: HTTP
# service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "443"
alb.ingress.kubernetes.io/healthcheck-timeout-seconds: "3"
alb.ingress.kubernetes.io/healthy-threshold-count: "2"
alb.ingress.kubernetes.io/load-balancer-attributes: idle_timeout.timeout_seconds=60
alb.ingress.kubernetes.io/scheme: internal
alb.ingress.kubernetes.io/security-groups: my-sg-1, my-sg-2, my-sg3
alb.ingress.kubernetes.io/subnets: my-subnet-a,my-subnet-b,my-subnet-c
alb.ingress.kubernetes.io/tags: env=hom
alb.ingress.kubernetes.io/target-group-attributes: deregistration_delay.timeout_seconds=60
alb.ingress.kubernetes.io/target-type: ip
alb.ingress.kubernetes.io/unhealthy-threshold-count: "2"
kubernetes.io/ingress.class: alb
nginx.ingress.kubernetes.io/rewrite-target: /
paths:
- /
hosts:
- akhq.poc.hom.internal
tls: []
# - secretName: akhq-tls
# hosts:
# - akhq.demo.com
### Readiness / Liveness probe config.
### ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/
readinessProbe:
enabled: true
prefix: "" # set same as `micronaut.server.context-path`
path: /health
port: 28081
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 3
httpGetExtra: {}
livenessProbe:
enabled: true
prefix: "" # set same as `micronaut.server.context-path`
path: /health
port: 28081
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 3
httpGetExtra: {}
resources: {}
# limits:
# cpu: 500m
# memory: 2512Mi
# requests:
# cpu: 100m
# memory: 2128Mi
nodeSelector: {}
tolerations: []
affinity: {}
networkPolicy:
enabled: true
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
hello,
I am using the values.yaml file to deploy akqh, but the error 404 occurs when trying to access it from dns or lb endpoint, and some attempts the screen is blank, that is, the login screen for access does not appear and also There are no log messages that help in this tshoot, could you please help me to answer what I am doing wrong?
to know: Pods running, ingress , svc, sa, role, sg's, all created
Beta Was this translation helpful? Give feedback.
All reactions