
Gitea supports internal TLS termination as well as redirection of http to https. That may be simpler than terminating in a reverse proxy. Let's try it. Also, make the dockerfile match the expectation of the job that there will be a gitea-init stage. Also, fix the repository root setting in app.ini. Change-Id: Ia6b66b53cebdb1afa49fef89a0559615f98052f1
23 lines
366 B
YAML
23 lines
366 B
YAML
kind: Service
|
|
apiVersion: v1
|
|
metadata:
|
|
name: gitea-service
|
|
namespace: gitea
|
|
spec:
|
|
selector:
|
|
app: gitea
|
|
ports:
|
|
- protocol: TCP
|
|
port: 80
|
|
targetPort: 3080
|
|
name: http
|
|
- protocol: TCP
|
|
port: 443
|
|
targetPort: 3000
|
|
name: http
|
|
- protocol: TCP
|
|
port: 22
|
|
targetPort: 22
|
|
name: ssh
|
|
type: LoadBalancer
|