Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unnecessary backend in ingress when portal is disabled #823

Closed
heww opened this issue Dec 7, 2021 · 0 comments · Fixed by #834
Closed

Unnecessary backend in ingress when portal is disabled #823

heww opened this issue Dec 7, 2021 · 0 comments · Fixed by #834
Assignees
Labels
kind/bug Something isn't working release/1.2

Comments

@heww
Copy link
Collaborator

heww commented Dec 7, 2021

Install the harbor cluster without portal, but the ingress still has backend for the portal.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    cluster-sample-ns.core.checksum.goharbor.io/harborcluster-sample-harbor-harbor: "6362"
    cluster-sample-ns.harbor.checksum.goharbor.io/harborcluster-sample-harbor: "3"
    cluster-sample-ns.portal.checksum.goharbor.io/harborcluster-sample-harbor-harbor: "5286"
    goharbor.io/warning: ⚠️ This Resource is managed by *harbor* ⚠️
    nginx.ingress.kubernetes.io/backend-protocol: HTTPS
    nginx.ingress.kubernetes.io/proxy-body-size: "0"
  labels:
    goharbor.io/operator-controller: harbor
    goharbor.io/operator-version: 0.0.0-dev
  name: harborcluster-sample-harbor-harbor
  namespace: cluster-sample-ns
spec:
  rules:
  - host: core.xxx.xxx.xxx.xxx.nip.io
    http:
      paths:
      - backend:
          service:
            name: harborcluster-sample-harbor-harbor-portal
            port:
              number: 443
        path: /
        pathType: Prefix
      - backend:
          service:
            name: harborcluster-sample-harbor-harbor-core
            port:
              number: 443
        path: /api/
        pathType: Prefix
      - backend:
          service:
            name: harborcluster-sample-harbor-harbor-core
            port:
              number: 443
        path: /service/
        pathType: Prefix
      - backend:
          service:
            name: harborcluster-sample-harbor-harbor-core
            port:
              number: 443
        path: /v2
        pathType: Prefix
      - backend:
          service:
            name: harborcluster-sample-harbor-harbor-core
            port:
              number: 443
        path: /chartrepo/
        pathType: Prefix
      - backend:
          service:
            name: harborcluster-sample-harbor-harbor-core
            port:
              number: 443
        path: /c/
        pathType: Prefix
  tls:
  - hosts:
    - core.xxx.xxx.xxx.xxx.nip.io
    secretName: sample-public-certificate
@cndoit18 cndoit18 added the kind/bug Something isn't working label Dec 8, 2021
cndoit18 added a commit to cndoit18/harbor-operator that referenced this issue Jan 10, 2022
Signed-off-by: cndoit18 <cndoit18@outlook.com>
cndoit18 added a commit to cndoit18/harbor-operator that referenced this issue Jan 10, 2022
Signed-off-by: cndoit18 <cndoit18@outlook.com>
cndoit18 added a commit to cndoit18/harbor-operator that referenced this issue Jan 11, 2022
Signed-off-by: cndoit18 <cndoit18@outlook.com>
cndoit18 added a commit that referenced this issue Jan 12, 2022
Signed-off-by: cndoit18 <cndoit18@outlook.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working release/1.2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants