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
It's probably also worth discussing the use if interal K8s routes for git and zarf.localhost for the registry mirror. Ideally they'd both use HTTPS and the ingress consistently.
We need to change the paths for git repositories from an East-West URL (*.<namespace>.svc.cluster.local) to one that comes in on the Ingress for Gitea (https://zarf.localhost)
Watch out for possible certificate/CA trust issues
The text was updated successfully, but these errors were encountered:
I think this is OBE since we don't hardcode to localhost anymore. Hardcoding http://stuart-gitea-http.git.svc.cluster.local:3000 is the only surefire way to git Gitea. Maybe we can change to https instead of http?
Note that this is only an issue for these examples, where the workload and the gitops-service are in the same cluster. In a production scenario when I'm building out my zarf package I'm gonna use https://the-hub-cluster or something as the URL
It's probably also worth discussing the use if interal K8s routes for git and
zarf.localhost
for the registry mirror. Ideally they'd both use HTTPS and the ingress consistently.Originally posted by @jeff-mccoy in #29 (comment)
We need to change the paths for git repositories from an East-West URL (
*.<namespace>.svc.cluster.local
) to one that comes in on the Ingress for Gitea (https://zarf.localhost)Watch out for possible certificate/CA trust issues
The text was updated successfully, but these errors were encountered: