Add gating for helm release management

This adds gating for helm release management by including a minimal
example workload phase which consists of a HelmRelease for the nginx
ingress controller and a corresponding deployment script including
supporting validation logic.

Change-Id: Ia21a799030289c7e40a0e61292578987ea0f6c63
Relates-To: #351
This commit is contained in:
Sean Eagan
2020-09-16 15:39:02 -05:00
committed by Kostyantyn Kalynovskyi
parent 2f5402ae80
commit eb40a5700f
10 changed files with 95 additions and 0 deletions

View File

@@ -0,0 +1,32 @@
---
apiVersion: "helm.fluxcd.io/v1"
kind: HelmRelease
metadata:
name: ingress
spec:
wait: true
timeout: 600
# This chart doesn't have any helm tests, but this still runs a noop
# helm test flow, to ensure we can do this.
test:
enable: true
values:
defaultBackend:
enabled: true
controller:
service:
type: NodePort
nodePorts:
http: 30000
https: 30001
kind: DaemonSet
hostNetwork: "false"
nodeSelector:
node-role.kubernetes.io/master: ""
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule
chart:
repository: https://kubernetes-charts.storage.googleapis.com
name: nginx-ingress
version: 1.40.1

View File

@@ -0,0 +1,4 @@
resources:
- namespace.yaml
- helmrelease.yaml
namespace: ingress

View File

@@ -0,0 +1,4 @@
apiVersion: v1
kind: Namespace
metadata:
name: ingress

View File

@@ -0,0 +1,2 @@
resources:
- ingress