Dex deployment for subclusters using existing dex HelmRelease in treasuremap

Note:
1. As per the latest conclusion, Dex and SIPCluster would be deployed on same namespace, hence dex function added to same Kustomization file

2. As a part of Issue# 136 for catalogue, there would be another patchset to make nodeport flexible

Change-Id: I53b2bb33278dd229450c305ad2e15476d8796073
This commit is contained in:
sa069q 2021-05-10 16:57:17 +05:30
parent ee9403fb1c
commit 88d18fa126
10 changed files with 28 additions and 6 deletions

View File

@ -36,7 +36,7 @@ spec:
endpoints:
hostname: dex.function.local
port:
https: 32556
https: 30556
http: 32554
k8s: 6443
tls:

View File

@ -8,7 +8,7 @@
"oidc-ca-file": "/etc/kubernetes/certs/dex-cert",
"oidc-client-id": "function-kubernetes",
"oidc-groups-claim": "group",
"oidc-issuer-url": "https://dex.function.local:32556/dex",
"oidc-issuer-url": "https://dex.function.local:30556/dex",
"oidc-username-claim": "email"
},
"extraVolumes":

View File

@ -1,2 +1,4 @@
resources:
- ../../../../../function/dex-aio
- sipcluster.yaml
namespace: lma-infra

View File

@ -1,3 +1,3 @@
resources:
- networking.yaml
- versions.yaml
- versions.yaml

View File

@ -45,3 +45,13 @@ replacements:
# NOTE: The SIPCluster CR accepts multiple infra service definitions,
# but we only deploy one instance of each.
fieldrefs: ["{.spec.services.loadBalancer[0].nodePort}"]
- source:
objref:
kind: VariableCatalogue
name: subcluster-networking
fieldref: "{.spec.lma.exposed_services[?(.name == 'auth')].nodePort}"
target:
objref:
kind: HelmRelease
name: dex-aio
fieldrefs: ["{.values.params.endpoints.port.https}"]

View File

@ -2,7 +2,6 @@ apiVersion: airship.airshipit.org/v1
kind: SIPCluster
metadata:
name: lma
namespace: sipcluster-system
finalizers:
- sip.airship.airshipit.org/finalizer
spec:

View File

@ -1,2 +1,4 @@
resources:
- ../../../../../function/dex-aio
- sipcluster.yaml
namespace: wordpress-infra

View File

@ -1,3 +1,3 @@
resources:
- networking.yaml
- versions.yaml
- versions.yaml

View File

@ -45,3 +45,13 @@ replacements:
# NOTE: The SIPCluster CR accepts multiple infra service definitions,
# but we only deploy one instance of each.
fieldrefs: ["{.spec.services.loadBalancer[0].nodePort}"]
- source:
objref:
kind: VariableCatalogue
name: subcluster-networking
fieldref: "{.spec.wordpress.exposed_services[?(.name == 'auth')].nodePort}"
target:
objref:
kind: HelmRelease
name: dex-aio
fieldrefs: ["{.values.params.endpoints.port.https}"]

View File

@ -2,7 +2,6 @@ apiVersion: airship.airshipit.org/v1
kind: SIPCluster
metadata:
name: wordpress
namespace: sipcluster-system
finalizers:
- sip.airship.airshipit.org/finalizer
spec: