harbor-helm icon indicating copy to clipboard operation
harbor-helm copied to clipboard

How do I configure if I use a apisix ingress controller

Open libo-sober opened this issue 3 years ago • 1 comments

I added kubernetes.io/ingress.class: "apisix", but it didn't take effect.

  ingress:
    hosts:
      core: core.liboer.top
      notary: notary.liboer.top
    # set to the type of ingress controller if it has specific requirements.
    # leave as `default` for most ingress controllers.
    # set to `gce` if using the GCE ingress controller
    # set to `ncp` if using the NCP (NSX-T Container Plugin) ingress controller
    controller: default
    annotations:
      # note different ingress controllers may require a different ssl-redirect annotation
      # for Envoy, use ingress.kubernetes.io/force-ssl-redirect: "true" and remove the nginx lines below
      #ingress.kubernetes.io/ssl-redirect: "true"
      ingress.kubernetes.io/proxy-body-size: "0"
      #nginx.ingress.kubernetes.io/ssl-redirect: "true"
      nginx.ingress.kubernetes.io/proxy-body-size: "0"
      #kubernetes.io/ingress.class: "nginx"
      kubernetes.io/ingress.class: "apisix"
    notary:
      # notary-specific annotations
      annotations: {}
    harbor:
      # harbor ingress-specific annotations
      annotations: {}

libo-sober avatar Aug 24 '21 01:08 libo-sober

hi @libo-sober , we are not tested harbor with apisix, in our test pipeline only test with nginx ingress. you can try it in your environment.

ninjadq avatar Sep 02 '21 07:09 ninjadq

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

github-actions[bot] avatar Feb 08 '24 09:02 github-actions[bot]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.

github-actions[bot] avatar Mar 11 '24 09:03 github-actions[bot]