You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| edge.envAsAppConfigFile | bool |`true`| If `true`, entries from `environmentVars` and `envFromSecret` fields will be mapped to configuration files. `environmentVars` to /etc/app-config/application.properties `envFromSecret` to /etc/app-config/secrets.properties Used for retrocompatiblity with FeatureHub controller versions lower than 1.5.0 https://docs.featurehub.io/featurehub/latest/installation.html#_run_configuration|
54
54
| edge.envFromSecret | string |`""`| Name of the secret containing secret properties, to be exposed as environment variables to edge deployment. Create the secret in advance, then reference it here. As of 1.5.0 all FeatureHub controller properties are available as environment variables using the same case Entries of the secret specified here are the same as would be specified in /etc/app-config/secrets.properties |
55
-
| edge.environmentVars | object |`{"dacha.url.default":"http://featurehub-dacha","listen.pool-size":"30","maxSlots":"30","server.gracePeriodInSeconds":"10","update.pool-size":"30"}`| Environment variables to be exposed to edge deployment. As of 1.5.0 all FeatureHub controller properties are available as environment variables using the same case. Entries accepted here are the same as would be specified in /etc/app-config/applications.properties. Note that `server.port` and `monitor.port` use their default values of `8085` and `8701` respectively, to make it easier to implement the deployment, service and the prometheus serviceMonitor manifests. |
55
+
| edge.environmentVars | object |`{"dacha.url.default":"http://featurehub-dacha:8600","listen.pool-size":"30","maxSlots":"30","server.gracePeriodInSeconds":"10","update.pool-size":"30"}`| Environment variables to be exposed to edge deployment. As of 1.5.0 all FeatureHub controller properties are available as environment variables using the same case. Entries accepted here are the same as would be specified in /etc/app-config/applications.properties. Note that `server.port` and `monitor.port` use their default values of `8085` and `8701` respectively, to make it easier to implement the deployment, service and the prometheus serviceMonitor manifests. |
56
56
| edge.extraContainers | list |`[]`| List of extra containers to add to Edge Pod |
57
57
| edge.extraEnvironmentVars | object |`{}`| Extra environment variables to be exposed to edge deployment. In terms of environment variable setting, this is the same as `environmentVars` field. The only difference is that if `envAsAppConfigFile: true`, only entries from `environmentVars` will be mapped to the application.properties configuration file, and not the ones from `extraEnvironmentVars`. |
58
58
| edge.extraVolumeMounts | list |`[]`| List of extra mounts to add to Edge Deployment |
59
59
| edge.extraVolumes | list |`[]`| List of extra volumes to add to Edge Deployment |
| global.envAsApplicationProperties | bool |`true`| If `true`, entries from `environmentVars` will be mapped to /etc/app-config/common.properties file To mount secret settings as /etc/app-config/common.properties see volume fields Used for retrocompatiblity with FeatureHub controller versions lower than 1.5.0 https://docs.featurehub.io/featurehub/latest/installation.html#_run_configuration|
86
-
| global.environmentVars |string|`nil`| Environment variables to be exposed to Management Repository, Edge and Dacha deployments. As of 1.5.0 all FeatureHub controller properties are available as environment variables using the same case. Entries accepted here are the same as would be specified in /etc/app-config/common.properties. |
86
+
| global.environmentVars |object|`{"nats.urls":"nats://featurehub-nats"}`| Environment variables to be exposed to Management Repository, Edge and Dacha deployments. As of 1.5.0 all FeatureHub controller properties are available as environment variables using the same case. Entries accepted here are the same as would be specified in /etc/app-config/common.properties. |
| global.extraEnvironmentVars | object |`{}`| Extra environment variables to be exposed to Management Repository, Edge and Dacha deployments. In terms of environment variable setting, this is the same as `environmentVars` field. The only difference is that if `envAsAppConfigFile: true`, only entries from `environmentVars` will be mapped to the common.properties configuration file, and not the ones from `extraEnvironmentVars`. |
91
91
| global.extraVolumeMounts | list |`[]`| List of extra mounts to add to Management Repository Deployment |
92
92
| global.extraVolumes | list |`[]`| List of extra volumes to add to Management Repository Deployment |
93
+
| global.ingress.annotations | list |`[]`||
94
+
| global.ingress.enabled | bool |`true`||
93
95
| managementRepository.affinity | object |`{}`||
94
96
| managementRepository.enabled | bool |`true`||
95
97
| managementRepository.envAsApplicationProperties | bool |`false`| If `true`, entries from `environmentVars` will be mapped to /etc/app-config/application.properties file To mount secret settings as /etc/app-config/application.properties see volume fields Used for retrocompatiblity with FeatureHub controller versions lower than 1.5.0 https://docs.featurehub.io/featurehub/latest/installation.html#_run_configuration|
96
98
| managementRepository.envFromSecret | string |`""`| Name of the secret containing secret properties, to be exposed as environment variables to edge deployment. Create the secret in advance, then reference it here. As of 1.5.0 all FeatureHub controller properties are available as environment variables using the same case Entries of the secret specified here are the same as would be specified in /etc/app-config/secrets.properties |
97
-
| managementRepository.environmentVars | object |`{"db.connections":"3","db.url":"jdbc:postgresql://setmeup-postgresql-endpoint:5432/featurehub","db.username":"featurehub","portfolio.admin.group.suffix":"Administrators","register.url":"http://localhost/register-url?token=%s","run.nginx":"true","server.gracePeriodInSeconds":"10"}`| Environment variables to be exposed to management-repository deployment. As of 1.5.0 all FeatureHub controller properties are available as environment variables using the same case. Entries accepted here are the same as would be specified in /etc/app-config/applications.properties. Note that `server.port` and `monitor.port` use their default values of `8085` and `8701` respectively, to make it easier to implement the deployment, service and the prometheus serviceMonitor manifests. |
99
+
| managementRepository.environmentVars | object |`{"db.connections":"20","db.password":"featurehub","db.url":"jdbc:postgresql://featurehub-postgresql:5432/featurehub","db.username":"featurehub","portfolio.admin.group.suffix":"Administrators"}`| Environment variables to be exposed to management-repository deployment. As of 1.5.0 all FeatureHub controller properties are available as environment variables using the same case. Entries accepted here are the same as would be specified in /etc/app-config/applications.properties. Note that `server.port` and `monitor.port` use their default values of `8085` and `8701` respectively, to make it easier to implement the deployment, service and the prometheus serviceMonitor manifests. |
98
100
| managementRepository.extraContainers | list |`[]`| List of extra containers to add to Management Repository Pod |
99
101
| managementRepository.extraEnvironmentVars | object |`{}`| Extra environment variables to be exposed to management-repository deployment. In terms of environment variable setting, this is the same as `environmentVars` field. The only difference is that if `envAsAppConfigFile: true`, only entries from `environmentVars` will be mapped to the application.properties configuration file, and not the ones from `extraEnvironmentVars`. |
100
102
| managementRepository.extraVolumeMounts | list |`[]`| List of extra mounts to add to Management Repository Deployment |
101
103
| managementRepository.extraVolumes | list |`[]`| List of extra volumes to add to Management Repository Deployment |
| postgresql | object |`{"enabled":false,"global":{"postgresql":{"auth":{"postgresPassword":"postgresql"}}},"primary":{"initdb":{"scripts":{"featurehub.sql":"CREATE USER featurehub PASSWORD 'featurehub'; CREATE DATABASE featurehub; GRANT ALL PRIVILEGES ON DATABASE featurehub TO featurehub;"}},"persistence":{"accessModes":["ReadWriteOnce"],"enabled":true,"size":"128Mi","storageClassName":"standard"}}}`| ----------------------------------------------------------------------------- # |
130
+
| postgresql | object |`{"enabled":true,"global":{"postgresql":{"auth":{"postgresPassword":"postgresql"}}},"primary":{"initdb":{"scripts":{"featurehub.sql":"CREATE USER featurehub PASSWORD 'featurehub'; CREATE DATABASE featurehub; GRANT ALL PRIVILEGES ON DATABASE featurehub TO featurehub;"}},"persistence":{"accessModes":["ReadWriteOnce"],"enabled":true,"size":"128Mi","storageClassName":"standard"}}}`| ----------------------------------------------------------------------------- # |
129
131
130
132
----------------------------------------------
131
-
Autogenerated from chart metadata using [helm-docs v1.6.0](https://github.com/norwoodj/helm-docs/releases/v1.6.0)
133
+
Autogenerated from chart metadata using [helm-docs v1.10.0](https://github.com/norwoodj/helm-docs/releases/v1.10.0)
0 commit comments