gitea.kosmos.org

kosmos/gitea.kosmos.org

Archived

Fork 0

Commit Graph

Author	SHA1	Message	Date
Greg Karékinian	91dab0f121	Explicitly set the ingress name to gitea-ingress The old config was generating a separate nginx ingress instead of attaching the HTTP challenge URL to our existing ingress (gitea-ingress)	2019-07-04 14:44:49 +02:00
Greg Karékinian	ae8d6a6cf3	WIP: Set up ingress with Let's Encrypt certificates using cert-manager This is using haproxy-ingress to support forwarding SSH on port 22 Since we're using cert-manager with ingress to get Let's Encrypt certs, we're not using the Let's Encrypt functionality that's part of Gitea. To run this we need to change the config file, have Gitea run on port 3000 as HTTP and disable all the Let's Encrypt config keys. Currently the gitea-ingress.yaml uses the letsencrypt-staging ClusterIssuer This has been tested on a local Kubernetes cluster using Docker for Mac	2019-06-05 17:57:16 +02:00

Author

SHA1

Message

Date

Greg Karékinian

91dab0f121

Explicitly set the ingress name to gitea-ingress

The old config was generating a separate nginx ingress instead of
attaching the HTTP challenge URL to our existing ingress (gitea-ingress)

2019-07-04 14:44:49 +02:00

Greg Karékinian

ae8d6a6cf3

WIP: Set up ingress with Let's Encrypt certificates using cert-manager

This is using haproxy-ingress to support forwarding SSH on port 22

Since we're using cert-manager with ingress to get Let's Encrypt certs,
we're not using the Let's Encrypt functionality that's part of Gitea. To
run this we need to change the config file, have Gitea run on port 3000
as HTTP and disable all the Let's Encrypt config keys. Currently the
gitea-ingress.yaml uses the letsencrypt-staging ClusterIssuer

This has been tested on a local Kubernetes cluster using Docker for Mac

2019-06-05 17:57:16 +02:00

2 Commits