kosmos/gitea.kosmos.org
Archived
8
1
Fork 0
Code Issues Pull Requests Releases Activity

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

Closed
greg wants to merge 5 commits from feature/ingress into master
pull from: feature/ingress
merge into: :master
Conversation 17 Commits 5 Files Changed 6
+2300 -4
5 Commits
Author SHA1 Message Date
greg 67d87d7d5b Use the correct name for the ingress 2019-07-05 11:13:22 +02:00
greg 3cdc07cdf3 Add initial Ingress documentation 2019-07-04 17:34:19 +02:00
greg 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 ed48c92e4f Update cert-manager to 0.8.1 2019-07-04 14:44:20 +02:00
greg 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