Docs
Helm-Charts
autopush

autopush

autopush

Version: 0.0.6 Type: application AppVersion: 1.72.2

A Helm chart for Kubernetes

Maintainers

NameEmailUrl
WrenIXhttps://wrenix.eu

= Beta

WARNING

We let it run in production, but it is not stable / complete.

TODOs:

====

Usage

Helm must be installed and setup to your kubernetes cluster to use the charts. Refer to Helm’s documentation to get started. Once Helm has been set up correctly, fetch the charts as follows:

helm pull oci://codeberg.org/wrenix/helm-charts/autopush

You can install a chart release using the following command:

helm install autopush-release oci://codeberg.org/wrenix/helm-charts/autopush --values values.yaml

To uninstall a chart release use helm’s delete command:

helm uninstall autopush-release

Requirements

RepositoryNameVersion
oci://docker.io/bitnamichartsredis20.6.3

Values

KeyTypeDefaultDescription
autoconnect.affinityobject{}
autoconnect.image.pullPolicystring"IfNotPresent"
autoconnect.image.registrystring"codeberg.org"
autoconnect.image.repositorystring"wrenix/autopush/autoconnect"
autoconnect.image.tagstring"latest"
autoconnect.livenessProbeobject{"httpGet":{"path":"/health","port":"http"}}This is to setup the liveness and readiness probes more information can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
autoconnect.nodeSelectorobject{}
autoconnect.podAnnotationsobject{}This is for setting Kubernetes Annotations to a Pod. For more information checkout: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
autoconnect.podLabelsobject{}This is for setting Kubernetes Labels to a Pod. For more information checkout: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
autoconnect.podSecurityContextobject{}
autoconnect.readinessProbe.httpGet.pathstring"/health"
autoconnect.readinessProbe.httpGet.portstring"http"
autoconnect.replicaCountint1This will set the replicaset count more information can be found here: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
autoconnect.resourcesobject{}We usually recommend not to specify default resources and to leave this as a conscious choice for the user. This also increases chances charts run on environments with little resources, such as Minikube. If you do want to specify resources, uncomment the following lines, adjust them as necessary, and remove the curly braces after ‘resources:’. limits: cpu: 100m memory: 128Mi requests: cpu: 100m memory: 128Mi
autoconnect.securityContextobject{}securityContext capabilities: drop: - ALL readOnlyRootFilesystem: true runAsNonRoot: true runAsUser: 1000
autoconnect.service.portint80
autoconnect.service.typestring"ClusterIP"
autoconnect.tolerationslist[]
autoconnect.volumeMountslist[]Additional volumeMounts on the output Deployment definition. - name: foo mountPath: “/etc/foo” readOnly: true
autoendpoint.affinityobject{}
autoendpoint.image.pullPolicystring"IfNotPresent"
autoendpoint.image.registrystring"codeberg.org"
autoendpoint.image.repositorystring"wrenix/autopush/autoendpoint"
autoendpoint.image.tagstring"latest"
autoendpoint.livenessProbeobject{"httpGet":{"path":"/health","port":"http"}}This is to setup the liveness and readiness probes more information can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
autoendpoint.nodeSelectorobject{}
autoendpoint.podAnnotationsobject{}
autoendpoint.podLabelsobject{}
autoendpoint.podSecurityContextobject{}
autoendpoint.readinessProbe.httpGet.pathstring"/health"
autoendpoint.readinessProbe.httpGet.portstring"http"
autoendpoint.replicaCountint1This will set the replicaset count more information can be found here: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
autoendpoint.resourcesobject{}We usually recommend not to specify default resources and to leave this as a conscious choice for the user. This also increases chances charts run on environments with little resources, such as Minikube. If you do want to specify resources, uncomment the following lines, adjust them as necessary, and remove the curly braces after ‘resources:’. limits: cpu: 100m memory: 128Mi requests: cpu: 100m memory: 128Mi
autoendpoint.securityContextobject{}
autoendpoint.service.portint80
autoendpoint.service.typestring"ClusterIP"
autoendpoint.tolerationslist[]
autoendpoint.volumeMountslist[]Additional volumeMounts on the output Deployment definition. - name: foo mountPath: “/etc/foo” readOnly: true
config.cryptoKeystring""run https://github.com/mozilla-services/autopush-rs/blob/master/scripts/fernet_key.py
config.logs.backtraceboolfalseenable backtrace of autopush
config.logs.levelstring"warn"set log level of autopush
fullnameOverridestring""
global.image.pullPolicystringnilif set it will overwrite all pullPolicy
global.image.registrystringnilif set it will overwrite all registry entries
grafana.dashboards.annotationsobject{}
grafana.dashboards.enabledboolfalse
grafana.dashboards.labels.grafana_dashboardstring"1"
imagePullSecretslist[]This is for the secretes for pulling an image from a private repository more information can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
ingress.annotationsobject{}
ingress.classNamestring""
ingress.enabledboolfalse
ingress.hoststring"chart-example.local"
ingress.tlslist[]
nameOverridestring""This is to override the chart name.
prometheus.enabledbooltruestart statsd sidecar and configure
prometheus.image.pullPolicystring"IfNotPresent"
prometheus.image.registrystring"docker.io"
prometheus.image.repositorystring"prom/statsd-exporter"
prometheus.image.tagstring"v0.28.0"
prometheus.livenessProbeobject{"httpGet":{"path":"/","port":"metrics"}}This is to setup the liveness and readiness probes more information can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
prometheus.readinessProbe.httpGet.pathstring"/"
prometheus.readinessProbe.httpGet.portstring"metrics"
prometheus.resourcesobject{}We usually recommend not to specify default resources and to leave this as a conscious choice for the user. This also increases chances charts run on environments with little resources, such as Minikube. If you do want to specify resources, uncomment the following lines, adjust them as necessary, and remove the curly braces after ‘resources:’. limits: cpu: 100m memory: 128Mi requests: cpu: 100m memory: 128Mi
prometheus.rules.additionalRuleslist[]
prometheus.rules.default.alertLabelsobject{}
prometheus.rules.default.enabledbooltrue
prometheus.rules.enabledboolfalse
prometheus.rules.labelsobject{}
prometheus.securityContextobject{}securityContext capabilities: drop: - ALL readOnlyRootFilesystem: true runAsNonRoot: true runAsUser: 1000
prometheus.servicemonitor.enabledboolfalse
prometheus.servicemonitor.labelsobject{}
prometheus.volumeMountslist[]Additional volumeMounts on the output Deployment definition. - name: foo mountPath: “/etc/foo” readOnly: true
redis.architecturestring"standalone"
redis.auth.enabledbooltrue
redis.auth.existingSecretstringnilOr use existing secret with “redis-password” key instead of static password
redis.auth.passwordstring"autopush"XXX Change me!
redis.dbidint0Database ID for non-default database
redis.external.existingSecretPasswordKeystring"redis-password"Password key to be retrieved from existing secret
redis.external.hoststring"redis"
redis.external.portint6379
redis.internalbooltrue
redis.master.kindstring"Deployment"
redis.master.persistence.enabledboolfalse
redis.master.service.portint6379
serviceAccount.annotationsobject{}
serviceAccount.automountbooltrue
serviceAccount.createbooltrue
serviceAccount.namestring""
volumeslist[]Additional volumes on the output Deployment definition. - name: foo secret: secretName: mysecret optional: false

Autogenerated from chart metadata using helm-docs

authentik-applicationconduit