Deployment of mattermost operator using Helm
This package has no upstream release note links on file. Please add some to chart/Chart.yaml under annotations.bigbang.dev/upstreamReleaseNotesMarkdown
.
Example:
annotations:
bigbang.dev/upstreamReleaseNotesMarkdown: |
- [Find our upstream chart's CHANGELOG here](https://link-goes-here/CHANGELOG.md)
- [and our upstream application release notes here](https://another-link-here/RELEASE_NOTES.md)
This package has no upstream release note links on file. Please add some to chart/Chart.yaml under annotations.bigbang.dev/upstreamReleaseNotesMarkdown
.
Example:
annotations:
bigbang.dev/upstreamReleaseNotesMarkdown: |
- [Find our upstream chart's CHANGELOG here](https://link-goes-here/CHANGELOG.md)
- [and our upstream application release notes here](https://another-link-here/RELEASE_NOTES.md)
- Kubernetes Cluster deployed
- Kubernetes config installed in
~/.kube/config
- Helm installed
Kubernetes: >=1.12.0-0
Install Helm
https://helm.sh/docs/intro/install/
- Clone down the repository
- cd into directory
helm install mattermost-operator chart/
Key | Type | Default | Description |
---|---|---|---|
image.imagePullPolicy | string | "IfNotPresent" |
Default image pull policy |
image.repository | string | "registry1.dso.mil/ironbank/opensource/mattermost/mattermost-operator" |
Full image name |
image.tag | string | "v1.22.1" |
Image tag |
replicas.count | int | 1 |
Mattermost operator desired replicas |
imagePullSecrets | list | [{"name":"private-registry"}] |
Image pull secrets |
resources | object | {"limits":{"cpu":"100m","memory":"512Mi"},"requests":{"cpu":"100m","memory":"512Mi"}} |
Resources for operator pod(s) |
securityContext | object | {"runAsGroup":65532,"runAsNonRoot":true,"runAsUser":65532} |
securityContext for Kubernetes pod(s) |
containerSecurityContext | object | {"capabilities":{"drop":["ALL"]},"privileged":false,"readOnlyRootFilesystem":true} |
containerSecurityContext for operator container |
affinity | object | {} |
Affinity for operator pod(s) |
nodeSelector | object | {} |
Node selector for operator pod(s) |
tolerations | object | {} |
Tolerations for operator pod(s) |
podAnnotations | object | {} |
Annotations for operator pod(s) |
podLabels | object | {} |
Labels for operator pod(s) |
networkPolicies.enabled | bool | false |
Toggle on/off Big Bang provided network policies |
networkPolicies.controlPlaneCidr | string | "0.0.0.0/0" |
See kubectl cluster-info and then resolve to IP |
istio.enabled | bool | false |
Toggle on/off istio interaction, used for network policies and mTLS |
istio.hardened.enabled | bool | false |
|
istio.hardened.customAuthorizationPolicies | list | [] |
|
istio.hardened.outboundTrafficPolicyMode | string | "REGISTRY_ONLY" |
|
istio.hardened.customServiceEntries | list | [] |
|
istio.hardened.monitoring.enabled | bool | true |
|
istio.hardened.monitoring.namespaces[0] | string | "monitoring" |
|
istio.hardened.monitoring.principals[0] | string | "cluster.local/ns/monitoring/sa/monitoring-grafana" |
|
istio.hardened.monitoring.principals[1] | string | "cluster.local/ns/monitoring/sa/monitoring-monitoring-kube-alertmanager" |
|
istio.hardened.monitoring.principals[2] | string | "cluster.local/ns/monitoring/sa/monitoring-monitoring-kube-operator" |
|
istio.hardened.monitoring.principals[3] | string | "cluster.local/ns/monitoring/sa/monitoring-monitoring-kube-prometheus" |
|
istio.hardened.monitoring.principals[4] | string | "cluster.local/ns/monitoring/sa/monitoring-monitoring-kube-state-metrics" |
|
istio.hardened.monitoring.principals[5] | string | "cluster.local/ns/monitoring/sa/monitoring-monitoring-prometheus-node-exporter" |
|
istio.mtls | object | {"mode":"STRICT"} |
Default peer authentication |
istio.mtls.mode | string | "STRICT" |
STRICT = Allow only mutual TLS traffic, PERMISSIVE = Allow both plain text and mutual TLS traffic |
monitoring.enabled | bool | false |
Toggle on/off monitoring interaction, used for network policies |
openshift | bool | false |
Openshift feature toggle, used for DNS network policy |
Please see the contributing guide if you are interested in contributing.
This file is programatically generated using helm-docs
and some BigBang-specific templates. The gluon
repository has instructions for regenerating package READMEs.