You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, Im currently testing k8s harbor setup in our new datacenter. The datacenter is behind a opnsense. I have managed to migrate services and resolve them using the HAProxy in the opnsense.
I have managed to install harbor, login and resolve the dns correctly. Harbor is exposed using metallb in l2 mode and the storage is longhorn.
Im currently facing the issue where It keeps retrying to push the image to the repository and eventually gives a 500 erorr.
➜ harbor docker login harbordc.ubiwhere.com -u admin
Password:
Login Succeeded
➜ harbor time docker push harbordc.ubiwhere.com/test-speed/1gb-random-file:latest
The push refers to repository [harbordc.ubiwhere.com/test-speed/1gb-random-file]
613d42ba11ea: Pushing [==================================================>] 1.074GB
e154057080f4: Pushing [==================================================>] 4.23MB
received unexpected HTTP status: 500 writing request for harbordc.ubiwhere.com:80: write tcp 10.255.2.3:43868->91.209.16.33:80: write: broken pipe
docker push harbordc.ubiwhere.com/test-speed/1gb-random-file:latest 0.15s user 0.09s system 0% cpu 3:19.58 total
I think the issue might be my configurations HaProxy and Harbor's internal proxy conflict. All our dns and CA is resolved in the haproxy.
I think the problem here is that the harbor as TLS Disabled and tryes to connect to port 80 instead of port 443 and docker doenst allow that while trying to push (?).
If I enable TLS and change haproxy to forward to port 443 I get this info:
Any help provided is welcome. Thanks.
The text was updated successfully, but these errors were encountered:
gsaudade99
changed the title
Harnor K8s running behind a OPNSense
Harbor K8s running behind a OPNSense
Apr 15, 2024
Hello, Im currently testing k8s harbor setup in our new datacenter. The datacenter is behind a opnsense. I have managed to migrate services and resolve them using the HAProxy in the opnsense.
I have managed to install harbor, login and resolve the dns correctly. Harbor is exposed using metallb in l2 mode and the storage is longhorn.
Im currently facing the issue where It keeps retrying to push the image to the repository and eventually gives a 500 erorr.
I think the issue might be my configurations HaProxy and Harbor's internal proxy conflict. All our dns and CA is resolved in the haproxy.
Bellow Is my values.yml configuration:
Some of the logs while trying to push to the registry:
I think the problem here is that the harbor as TLS Disabled and tryes to connect to port 80 instead of port 443 and docker doenst allow that while trying to push (?).
If I enable TLS and change haproxy to forward to port 443 I get this info:
Any help provided is welcome. Thanks.
The text was updated successfully, but these errors were encountered: