cloud
/
manifests
3
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

use NodePort instead of Ingress for Harbor

This commit is contained in:
Max Erenberg 2022-01-03 10:29:12 -05:00 committed by root
parent 78ae41cc61
commit d5e485f9bf
1 changed files with 18 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
harbor/values.yaml
View File

@ -3,14 +3,24 @@ expose:
# We are performing TLS termination OUTSIDE of the k8s cluster
tls:
enabled: false
type: ingress
ingress:
hosts:
core: registry.cloud.csclub.uwaterloo.ca
notary: notary.cloud.csclub.uwaterloo.ca
annotations:
ingress.kubernetes.io/ssl-redirect: "false"
nginx.ingress.kubernetes.io/ssl-redirect: "false"
#type: ingress
#ingress:
# hosts:
# core: registry.cloud.csclub.uwaterloo.ca
# notary: notary.cloud.csclub.uwaterloo.ca
# annotations:
# ingress.kubernetes.io/ssl-redirect: "false"
# nginx.ingress.kubernetes.io/ssl-redirect: "false"
type: nodePort
nodePort:
name: harbor
ports:
http:
port: 80
nodePort: 30002
notary:
port: 4443
nodePort: 30004
externalURL: https://registry.cloud.csclub.uwaterloo.ca
harborAdminPassword: REPLACE_ME
# must be a string of 16 chars