rancher-partner-charts/charts/triggermesh/triggermesh
Samuel Attwood d6599f6f4b Fixing some chart logos 2022-12-02 02:07:34 -05:00
..
charts/triggermesh-core Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
crds Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
templates Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
.helmignore Fixing some chart logos 2022-12-02 02:07:34 -05:00
Chart.lock Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
Chart.yaml Fixing some chart logos 2022-12-02 02:07:34 -05:00
README.md Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
app-readme.md Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
values.yaml Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00

README.md

TriggerMesh

TL;DR;

$ helm repo add triggermesh https://storage.googleapis.com/triggermesh-charts
$ helm install -n triggermesh triggermesh triggermesh/triggermesh --create-namespace

To report bugs and for feedback and support please create a new issue.

Introduction

This chart installs the TriggerMesh Open Source Components on a Kubernetes cluster.

Prerequisites

  • Kubernetes 1.20+
  • Helm 3.0+
  • Knative v0.25+

Installing the Chart

Add the TriggerMesh chart repository to Helm:

$ helm repo add triggermesh https://storage.googleapis.com/triggermesh-charts

To install the chart with the release name my-release:

$ helm install --name my-release triggermesh/triggermesh

The command deploys the TriggerMesh opensource components in the default configuration. Refer to the configuration section for the complete list of parameters that can be specified to customize the deployment of the controller.

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm uninstall my-release

The Kubernetes resources associated with chart will be removed and the Helm release will be deleted.

Configuration

Parameter Description Default
nameOverride Override the name for controller resources ""
fullnameOverride Override the fullname for controller resources ""
image.registry Image registry name gcr.io/triggermesh
image.tag Image tag .Chart.AppVersion
image.pullPolicy Image pull policy IfNotPresent
imagePullSecrets Specify image pull secrets []
replicaCount Number of replicas 1
rbac.create Create RBAC resources true
serviceAccount.create Create service account for the controller true
serviceAccount.annotations Annotations to add to controller service account {}
serviceAccount.name Override the name for the service account nil
podAnnotations Annotations to add to the controller pod {}
podSecurityContext Security context for controller pods {}
securityContext Security context for controller containers {}
resources Resource requests/limits for the controller {}
nodeSelector Controller node selector {}
tolerations Tolerations for use with node taints []
affinity Assign custom affinity rules to the controller pods {}
webhook.podAnnotations Annotations to add to the webhook pod {sidecar.istio.io/inject: 'false'}
webhook.podSecurityContext Security context for webhook pods {}
webhook.securityContext Security context for webhook containers {}
webhook.resources Resource requests/limits for the webhook {}
webhook.nodeSelector Webhook node selector {}
webhook.tolerations Tolerations for use with node taints []
webhook.affinity Assign custom affinity rules to the webhook pods {}