Files
wlan-cloud-helm/tip-wlan/resources/environments/dev-integrated.yaml
Rahul Sharma dfa6bfc728 Remove CloudDeployment flag from Helm charts.
Not needed if pods(running in local env) can reach Jfrog to retrieve schema.
2020-11-04 18:54:41 -05:00

127 lines
3.8 KiB
YAML

# This is a development override file.
# It overrides the default Tip-Wlan parent chart behaviour
#
# It can be tweaked, based on the need to support different
# dev environments.
# This file expects to have a GlusterFS storage solution running
# before "helm install" is performed.
#################################################################
# Global configuration overrides.
#
# These overrides will affect all helm charts (ie. applications)
# that are listed below and are 'enabled'.
#################################################################
global:
# Change to an unused port prefix range to prevent port conflicts
# with other instances running within the same k8s cluster
nodePortPrefix: 302
nsPrefix: tip
# image pull policy
pullPolicy: Always
repository: tip-tip-wlan-cloud-docker-repo.jfrog.io
# override default mount path root directory
# referenced by persistent volumes and log files
persistence:
# flag to enable debugging - application support required
debugEnabled: true
# Integrated Deployment which deploys Prov Service, Portal Service and
# SSC Service in a single docker image
integratedDeployment: true
# Annotations for namespace
annotations: {
"helm.sh/resource-policy": keep
}
createReleaseNamespace: false
# Docker registry secret
dockerRegistrySecret: ewoJImF1dGhzIjogewoJCSJ0aXAtdGlwLXdsYW4tY2xvdWQtZG9ja2VyLXJlcG8uamZyb2cuaW8iOiB7CgkJCSJhdXRoIjogImRHbHdMWEpsWVdRNmRHbHdMWEpsWVdRPSIKCQl9Cgl9LAoJIkh0dHBIZWFkZXJzIjogewoJCSJVc2VyLUFnZW50IjogIkRvY2tlci1DbGllbnQvMTkuMDMuOCAobGludXgpIgoJfQp9
#################################################################
# Enable/disable and configure helm charts (ie. applications)
# to customize the TIP-WLAN deployment.
#################################################################
opensync-gw-static:
enabled: false
opensync-gw-cloud:
enabled: true
env:
protocol: https
ssc:
service: wlan-integrated-cloud-component-service
port: 9092
prov:
service: wlan-integrated-cloud-component-service
port: 9092
opensync-mqtt-broker:
enabled: true
replicaCount: 1
persistence:
enabled: true
storageClass: "glusterfs-storage"
wlan-cloud-graphql-gw:
enabled: true
wlan-cloud-static-portal:
enabled: true
wlan-integrated-cloud-component-service:
enabled: true
image:
name: wlan-integrated-cloud-component-service-persistence
tag: 0.0.1-SNAPSHOT
creds:
enabled: true
postgres:
password: cG9zdGdyZXMxMjM=
schema_repo:
username: tip-read
password: tip-read
integratedWithPersistence:
enabled: true
nginx-ingress-controller:
enabled: true
controller:
nodeSelector: {
type: master
}
config:
externalStatusAddress: "192.168.56.101"
zookeeper:
enabled: true
replicaCount: 1
persistence:
enabled: true
storageClass: "glusterfs-storage"
kafka:
enabled: true
replicaCount: 1
persistence:
enabled: true
storageClass: "glusterfs-storage"
cassandra:
enabled: true
config:
## NOTE: If we are using glusterfs as Storage class, we don't really need
## replication turned on, since the data is anyway replicated on glusterfs nodes
## Replication is useful when we use HostPath as storage mechanism
## For Hostpath storage, recommendation is cluster_size: 3 and seed_size: 2
cluster_size: 1
seed_size: 1
persistence:
enabled: true
storageClass: "glusterfs-storage"
postgresql:
enabled: true
postgresqlPassword: cG9zdGdyZXMxMjM=
## NOTE: If we are using glusterfs as Storage class, we don't really need
## replication turned on, since the data is anyway replicated on glusterfs nodes
## Replication is useful:
## a. When we use HostPath as storage mechanism
## b. If master goes down and one of the slave is promoted as master
replication:
enabled: false
slaveReplicas: 1
persistence:
enabled: true
storageClass: "glusterfs-storage"