cheshire
/
hscloud
forked from hswaw/hscloud
1
0
Fork 0
Code Pull Requests Activity

cluster/admitomatic: allow use-regex n-i-c annotation 

This annotation is used to permit routes defined by regexes instead of
simple prefix matching. This is used by our synapse deployment for
routing incomming HTTP requests to diffferent Synapse components.

I've stumbled upon this while deploying a new Matrix/Synapse instance.
This hasn't been yet a problem because the existing ingresses for Matrix
deployments predate admitomatic.

Change-Id: I821e58b214450ccf0de22d2585c3b0d11fbe71c0
master
q3k 2021-06-06 12:28:28 +00:00
parent 56c888b443
commit 89a16f4de4
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
cluster/admitomatic/ingress.go
View File

@ -210,6 +210,7 @@ func (i *ingressFilter) admit(req *admission.AdmissionRequest) (*admission.Admis
"proxy-body-size": true,
"ssl-redirect": true,
"backend-protocol": true,
"use-regex": true,
// Used by cert-manager
"whitelist-source-range": true,
}

2
cluster/kube/lib/admitomatic.libsonnet
View File

@ -32,7 +32,7 @@ local prototext = import "../../../kube/prototext.libsonnet";
cfg:: {
namespace: "admitomatic",
image: "registry.k0.hswaw.net/q3k/admitomatic:315532800-6cc2f867951e123909b23955cd7bcbcc3ec24f8a",
image: "registry.k0.hswaw.net/q3k/admitomatic:1622912229-383fefa14bddd51c1573fb9b5fcc6ecea958f50a",
proto: {},
},