1

it is about to expose service via ingress rules and ingress controller , i do installation of harbor registry via helm chart https://github.com/bitnami/charts/tree/master/bitnami/harbor and default service expose method is to bind service to external load balancer, since i have single ubuntu machine with microk8s i want to expose via host machine ingress controller, i do it but by overriding values.yaml files from helm, chart repo

global:  

storageClass: "ssd-hostpath"


externalURL: https://core.ip.nip.io

exposureType: ingress


# service:
#   type: LoadBalancer

ingress:
  core:
    #ingressClassName: "contour"
    hostname: core.ip.nip.io
    annotations:
      kubernetes.io/ingress.class: contour
      cert-manager.io/cluster-issuer: letsencrypt-staging-cluster-issuer
      ingress.kubernetes.io/force-ssl-redirect: "true"
      kubernetes.io/tls-acme: "true"
    tls: true  
    # secrets: 
    # - name: nip-io-lets-encr-stage-tls-cert
  notary:
    #ingressClassName: ""
    hostname: notary.ip .nip.io
    annotations:
      kubernetes.io/ingress.class: contour
      cert-manager.io/cluster-issuer: letsencrypt-staging-cluster-issuer
      ingress.kubernetes.io/force-ssl-redirect: "true"
      kubernetes.io/tls-acme: "true"
    tls: true  
    # secrets: 
    # - name: nip-io-lets-encr-stage-tls-cert  

But in this case strangely pods are failing ang give network error , just want to know if anyone could share sample installation of bitnami/harbor with exposing via ingress controller on same machine

0 Answers0