Browse Source

Use edge TLS termination

Quarkus < 3.x doesn't support some of the route options, we need to
apply this YAML instead and disable auto route enable

still todo, combine yaml's into one for easier oc apply -f <COMBINED> or
have quarkus apply the snippets for us
kerberos_auth
Jonathan Christison 3 years ago
parent
commit
e755fe945c
  1. 20
      k8s/stage/edgeroute.yml
  2. 0
      k8s/stage/kerberos-config.yaml
  3. 9
      src/main/resources/application.properties

20
k8s/stage/edgeroute.yml

@ -0,0 +1,20 @@
apiVersion: route.openshift.io/v1
kind: Route
metadata:
creationTimestamp: null
labels:
app.kubernetes.io/name: osh
app.kubernetes.io/version: 1.0.0-SNAPSHOT
app.openshift.io/runtime: quarkus
env: stage
name: osh
spec:
port:
targetPort: http
tls:
termination: edge
to:
kind: ""
name: osh
weight: null
status: {}

0
k8s/kerberos-config.yaml → k8s/stage/kerberos-config.yaml

9
src/main/resources/application.properties

@ -12,8 +12,14 @@
%stage.quarkus.openshift.name=osh
%stage.quarkus.openshift.labels.env=stage
%stage.quarkus.log.level=DEBUG
#Only in Quarkus > 3.x
%stage.quarkus.openshift.route.tls.termination=edge
%stage.quarkus.openshift.route.expose=true
#As we cant create a edge terminated route (quarkus <3.x) lets disable route creation for now
%stage.quarkus.openshift.route.expose=false
%stage.quarkus.openshift.route.target-port=https
%stage.quarkus.openshift.route.tls.insecure-edge-termination-policy=redirect
##########################################
# Kerberos Specifics #
@ -31,5 +37,4 @@
%stage.quarkus.openshift.mounts.osh-wrapper-config-vol.read-only=true
%stage.quarkus.log.level=DEBUG

Loading…
Cancel
Save