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

Big Bang Core Example - Use HTTPS and the Ingress consistently #43

Closed
RothAndrew opened this issue Sep 15, 2021 · 2 comments
Closed

Big Bang Core Example - Use HTTPS and the Ingress consistently #43

RothAndrew opened this issue Sep 15, 2021 · 2 comments

Comments

@RothAndrew
Copy link
Member

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

@RothAndrew
Copy link
Member Author

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

@RothAndrew
Copy link
Member Author

Old, stale. Closing. Can be reopened if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

2 participants