Thiết kế website giá rẻ

Question

I’m a little noob to kubernetes to be honest.

I’m trying to deploy multiple apps to an Azure Kubernetes Services cluster.

I deployed a Budibase app using helm.

Then I deployed an Nginx Ingress Controller and an Ingress to publish the app. It work well. Here is the configuration files

# values.yaml

# Ingress configuration
ingress:
  enabled: true
  className: "nginx"
  annotations:
    cert-manager.io/cluster-issuer: "letsencrypt-prod" # Remplacez par le nom de votre ClusterIssuer
  hosts:
    - host: "budibase-kube.***.******-******.***" # Remplacez par votre nom de domaine
      paths:
        - path: /
          pathType: Prefix
          backend:
            service:
              name: proxy-service # Assurez-vous que ce nom de service correspond à votre service Budibase
              port:
                number: 10000
  tls:
    - hosts:
        - "budibase-kube.***.******-******.***" # Remplacez par votre nom de domaine
      secretName: budibase-tls # Nom du secret Kubernetes pour stocker le certificat

This work well. I can connect to the application and it generate an SSL certificate well.

Then, I tried to deploy an Infisical instance in the same cluster. I want to use the same ingress controller.

Here is the configuration file:

replicaCount: 1

image:
  repository: infisical/infisical
  tag: latest
  pullPolicy: IfNotPresent



ingress:
  enabled: true
  className: nginx
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-staging
  hosts:
    - host: "infisical.***.******-******.***"
      paths:
        - path: /
          pathType: Prefix
          backend:
            service:
              name: infisical-backend
              port:
                number: 8080
  tls:
    - hosts:
        - "infisical.***.******-******.***"
      secretName: infisical-tls

envFromSecret: infisical-secrets

But with this use case. The host part of the ingress isn’t the host I’ve setup in the file. It keep being ” * “.

Here is the budibase ingress describe:

Name:             budibase-budibase
Labels:           app.kubernetes.io/instance=budibase
                  app.kubernetes.io/managed-by=Helm
                  app.kubernetes.io/name=budibase
                  app.kubernetes.io/version=2.26.2
                  helm.sh/chart=budibase-3.0.129
Namespace:        budibase
Address:          ***.***.***.***
Ingress Class:    nginx
Default backend:  <default>
TLS:
  budibase-tls terminates budibase-kube.***.******-******.***
Rules:
  Host                                 Path  Backends
  ----                                 ----  --------
  budibase-kube.***.******-******.***
                                       /   proxy-service:10000 (10.224.0.173:10000)
Annotations:                           cert-manager.io/cluster-issuer: letsencrypt-prod
                                       meta.helm.sh/release-name: budibase
                                       meta.helm.sh/release-namespace: budibase
Events:                                <none>                              <none>

And here is the infisical ingress describe:

Name:             infisical-ingress
Labels:           app.kubernetes.io/managed-by=Helm
Namespace:        infisical
Address:          ***.***.***.***
Ingress Class:    nginx
Default backend:  <default>
TLS:
  infisical-tls terminates infisical.***.******-******.***
Rules:
  Host        Path  Backends
  ----        ----  --------
  *
              /             infisical-backend:8080 (10.224.0.174:8080,10.224.0.26:8080)
              /ss-webhook   infisical-backend:8080 (10.224.0.174:8080,10.224.0.26:8080)
Annotations:  cert-manager.io/cluster-issuer: letsencrypt-staging
              meta.helm.sh/release-name: infisical
              meta.helm.sh/release-namespace: infisical
Events:       <none>

I don’t understand why the host keep being ” * ” instead of infisical..–. like I mentionned in the values.yaml file…

Thiết kế website giá rẻ

Danh mục

Kubernetes multiple ingress issue