I have a minikube cluster running with Docker with a deployment of Harbor done with helm.
It is local setup I used openssl to generate cert and key to use TLS to access harbor.
The problem I encounter is that I can’t access harbor.

Here is my value yaml file:

Global settings

global:
persistence:
enabled: true

harborAdminPassword: Harbor12345
hostname: k8s.local
http:
port: 85
https:
port: 443

Ingress settings

ingress:
enabled: true
annotations: {}
hosts:
– host: k8s.local
paths: [“/”]
tls:
– secretName: registry-tls
hosts:
– k8s.local

TLS settings

tls:
secretName: registry-tls
existingSecret: true

Certificate and private key settings

certificates:
secretName: registry-tls
existingSecret: true
secretKey: registry.k8s.local.key
secretCrt: registry.k8s.local.crt

External URL for accessing Harbor

externalURL: https://k8s.local

Harbor authentication mode

authMode: db_auth

Harbor database settings

database:
type: internal
password: Harbor12345

Harbor storage settings

storage:
type: filesystem
filesystem:
rootdirectory: /data

Harbor registry settings

registry:
secretName: registry-secret

Harbor Redis settings

redis:
enabled: true
persistence:
enabled: true

Harbor Trivy settings

trivy:
enabled: true

Harbor portal settings

portal:
secretName: portal-secret

Harbor jobservice settings

jobservice:
secretName: jobservice-secret

exporter:
secretName: exporter-secret

curl https://k8s.local
curl: (7) Failed to connect to k8s.local port 443 after 1 ms: Connection refused

output kubectl get po -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-5dd5756b68-xg76g 1/1 Running 9 (6d4h ago) 10d
etcd-minikube 1/1 Running 9 (6d4h ago) 10d
kube-apiserver-minikube 1/1 Running 9 (6d4h ago) 10d
kube-controller-manager-minikube 1/1 Running 9 (6d4h ago) 10d
kube-proxy-qtcc6 1/1 Running 9 (6d4h ago) 10d
kube-scheduler-minikube 1/1 Running 9 (6d4h ago) 10d
registry-c2fjr 1/1 Running 7 (6d4h ago) 8d
registry-proxy-bdv59 1/1 Running 7 (6d4h ago) 8d
storage-provisioner 1/1 Running 18 (14h ago) 10d

check dns resolution and firewall config as well.
I am looking to find a way to check the log of the proxy.

kubectl get services -n harbor

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
harbor-core ClusterIP 10.102.243.216 80/TCP 24h
harbor-database ClusterIP 10.97.101.141 5432/TCP 24h
harbor-jobservice ClusterIP 10.100.245.195 80/TCP 24h
harbor-portal ClusterIP 10.97.185.234 80/TCP 24h
harbor-redis ClusterIP 10.103.50.52 6379/TCP 24h
harbor-registry ClusterIP 10.98.42.132 5000/TCP,8080/TCP 24h
harbor-trivy ClusterIP 10.106.210.64 8080/TCP 24h

I wonder if the problem is with Kube-proxy:
Do I need to add a rule?
kubectl get configmap kube-proxy -n kube-system -o yaml

apiVersion: v1
data:
config.conf: |-
apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: 0.0.0.0
bindAddressHardFail: false
clientConnection:
acceptContentTypes: “”
burst: 0
contentType: “”
kubeconfig: /var/lib/kube-proxy/kubeconfig.conf
qps: 0
clusterCIDR: 10.244.0.0/16
configSyncPeriod: 0s
conntrack:
maxPerCore: 0
min: null
tcpCloseWaitTimeout: 0s
tcpEstablishedTimeout: 0s
detectLocal:
bridgeInterface: “”
interfaceNamePrefix: “”
detectLocalMode: “”
enableProfiling: false
healthzBindAddress: “”
hostnameOverride: “”
iptables:
localhostNodePorts: null
masqueradeAll: false
masqueradeBit: null
minSyncPeriod: 0s
syncPeriod: 0s
ipvs:
excludeCIDRs: null
minSyncPeriod: 0s
scheduler: “”
strictARP: false
syncPeriod: 0s
tcpFinTimeout: 0s
tcpTimeout: 0s
udpTimeout: 0s
kind: KubeProxyConfiguration
logging:
flushFrequency: 0
options:
json:
infoBufferSize: “0”
verbosity: 0
metricsBindAddress: 0.0.0.0:10249
mode: “”
nodePortAddresses: null
oomScoreAdj: null
portRange: “”
showHiddenMetricsForVersion: “”
winkernel:
enableDSR: false
forwardHealthCheckVip: false
networkName: “”
rootHnsEndpointName: “”
sourceVip: “”
kubeconfig.conf: |-
apiVersion: v1
kind: Config
clusters:
– cluster:
certificate-authority: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
server: https://control-plane.minikube.internal:8443
name: default
contexts:
– context:
cluster: default
namespace: default
user: default
name: default
current-context: default
users:
– name: default
user:
tokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
kind: ConfigMap
metadata:
creationTimestamp: “2024-04-19T22:05:52Z”
labels:
app: kube-proxy
name: kube-proxy
namespace: kube-system
resourceVersion: “272”
uid: a44631f7-8dfb-47bf-bf00-45f11098ff53