azure-aksazure-monitoringgrafana-mimir

Why this mimir gateway ingress is not getting created?


-- A reverse proxy deployment that is meant to receive traffic for Mimir or GEM. When enterprise.enabled is true the GEM gateway is deployed. Otherwise, it is an nginx. Options except those under gateway.nginx apply to both versions - nginx and GEM gateway.

gateway:
  ingress:
    enabled: true
    nameOverride: mimir-nginx
    hosts:
      - host: mimir-distributor.neu.internal.dev.(companyname).com
        paths:
          - path: /api/v1/push
            pathType: Prefix
    tls:
      - secretName: mimir-distributor-tls
        hosts:
          - mimir-distributor.neu.internal.dev.(companyname).com
  enabledNonEnterprise: true
  replicas: 1

secret exist and doest contain certificates, as far as i understand normal ingress will be depreciated soon so im trying to do one using gateway. But nothing gets created


Solution

  • To setup mimir, follow this document using.

    helm repo add grafana https://grafana.github.io/helm-charts
    helm repo update![mimir](https://i.imgur.com/6Izy6zd.png) 
    

    The Helm chart at https://grafana.github.io/helm-charts is a publication of the source code at grafana/mimir.

    Install Mimir using the Helm chart: helm -n mimir-test install mimir grafana/mimir-distributed

    enter image description here

     kubectl -n mimir-test get pods
    

    here

    kubectl describe pod mimir-nginx -n mimir-test
    

    nginx ingress for mimir. An ingress YAML for Mimir, considering your requirements, would look something like

    apiVersion: networking.k8s.io/v1
    kind: Ingress
    metadata:
      name: mimir-nginx
      annotations:
        kubernetes.io/ingress.class: "nginx"
    spec:
      tls:
      - hosts:
        - mimir-distributor.neu.internal.dev.yourcompanyname.com
        secretName: mimir-distributor-tls
      rules:
      - host: mimir-distributor.neu.internal.dev.yourcompanyname.com
        http:
          paths:
          - path: /api/v1/push
            pathType: Prefix
            backend:
              service:
                name: your-service-name
                port:
                  number: 80