triggermesh / charts Goto Github PK

View Code? Open in Web Editor NEW

3.0 1.0 4.0 822 KB

Charts for TriggerMesh Deployments

License: Apache License 2.0

Mustache 14.98% Smarty 85.02%

knative serverless kubernetes

charts's Introduction

Helm Charts for TriggerMesh

Charts for TriggerMesh Integration Platform

Add Helm Charts Repository

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

Search for charts in the TriggerMesh library

$ helm search repo triggermesh

Install a chart from the TriggerMesh Library

$ helm install my-release triggermesh/<chart>

Support

We would love your feedback and help on these charts, so don't hesitate to let us know what is wrong and how we could improve them, just file an issue or join those of use who are maintaining them and submit a PR

Commercial Support

TriggerMesh Inc supports this project commercially, email [email protected] to get more details.

Code of Conduct

This plugin is by no means part of CNCF but we abide by its code of conduct

charts's People

Contributors

Stargazers

Watchers

Forkers

davidkarlsen atzawada luis-sousa-pinto diablo02000

charts's Issues

Update charts with tm/tm 1.15.2 release

Unable to install helm chart for knative 0.9.0 using helm 3.x

Hello,

I'm trying to install knative 0.9.0 on a dev environment (Kubernetes on Docker desktop for Mac) I'm following the instructions I found here:
https://triggermesh.com/2019/04/knative-helm-chart/

I'm using helm 3.x

helm version
version.BuildInfo{Version:"v3.0.2", GitCommit:"19e47ee3283ae98139d98460de796c1be1e3975f", GitTreeState:"clean", GoVersion:"go1.13.5"}

I had to do a little update on the install command syntax due to the fact that the name is now mandatory in helm 3 and the --name flag isn't supported anymore:

helm install knative-0.9.0 tm/knative --debug

I also added the --debug flag in order to debug the output.

The output is:

install.go:149: [debug] Original chart version: ""
install.go:166: [debug] CHART PATH: /Users/mdaros/Library/Caches/helm/repository/knative-0.9.0.tgz

manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "DestinationRule" in version "networking.istio.io/v1alpha3", unable to recognize "": no matches for kind "Gateway" in version "networking.istio.io/v1alpha3", unable to recognize "": no matches for kind "Image" in version "caching.internal.knative.dev/v1alpha1", unable to recognize "": no matches for kind "attributemanifest" in version "config.istio.io/v1alpha2", unable to recognize "": no matches for kind "handler" in version "config.istio.io/v1alpha2", unable to recognize "": no matches for kind "instance" in version "config.istio.io/v1alpha2", unable to recognize "": no matches for kind "rule" in version "config.istio.io/v1alpha2"]
helm.go:76: [debug] [unable to recognize "": no matches for kind "DestinationRule" in version "networking.istio.io/v1alpha3", unable to recognize "": no matches for kind "Gateway" in version "networking.istio.io/v1alpha3", unable to recognize "": no matches for kind "Image" in version "caching.internal.knative.dev/v1alpha1", unable to recognize "": no matches for kind "attributemanifest" in version "config.istio.io/v1alpha2", unable to recognize "": no matches for kind "handler" in version "config.istio.io/v1alpha2", unable to recognize "": no matches for kind "instance" in version "config.istio.io/v1alpha2", unable to recognize "": no matches for kind "rule" in version "config.istio.io/v1alpha2"]
unable to build kubernetes objects from release manifest
helm.sh/helm/v3/pkg/action.(*Install).Run
	/private/tmp/helm-20191220-82547-1gmzo4a/src/helm.sh/helm/pkg/action/install.go:231
main.runInstall
	/private/tmp/helm-20191220-82547-1gmzo4a/src/helm.sh/helm/cmd/helm/install.go:214
main.newInstallCmd.func1
	/private/tmp/helm-20191220-82547-1gmzo4a/src/helm.sh/helm/cmd/helm/install.go:116
github.com/spf13/cobra.(*Command).execute
	/private/tmp/helm-20191220-82547-1gmzo4a/pkg/mod/github.com/spf13/[email protected]/command.go:826
github.com/spf13/cobra.(*Command).ExecuteC
	/private/tmp/helm-20191220-82547-1gmzo4a/pkg/mod/github.com/spf13/[email protected]/command.go:914
github.com/spf13/cobra.(*Command).Execute
	/private/tmp/helm-20191220-82547-1gmzo4a/pkg/mod/github.com/spf13/[email protected]/command.go:864
main.main
	/private/tmp/helm-20191220-82547-1gmzo4a/src/helm.sh/helm/cmd/helm/helm.go:75
runtime.main
	/usr/local/Cellar/go/1.13.5/libexec/src/runtime/proc.go:203
runtime.goexit
	/usr/local/Cellar/go/1.13.5/libexec/src/runtime/asm_amd64.s:1357

I did the same thing with success a few months ago using helm 2.x and an older chart version for knative (I think it was the 0.5.0 but I'm not sure of that)

Thanks
Massimo

Split CRD chart from deployment chart

the current triggermesh chart uses the "crds" folder this is ok as long as CRDs are not revised i.e if a field is added then a new versioned kind is needed. Because charts are revised a "crd" chart with manifest in the template folder would allow CRDs to be updated in a logical way.

knative 0.2.0 doesn't handle the Image CRD too well

Getting helm-2.7.2 to recognize our helm chart exposed two major issues that will need to be addressed before we can switch over:

There are duplicate Image CRD entries in templates/knative.xml. Both will need to be removed.
The Image CRD needs to be pulled out. Either into its own file that can be loaded via kubectl first, or appended to https://storage.googleapis.com/triggermesh-charts/istio-crds.yaml which is used to support the older version of helm.

Update Charts with the latest supported releases

Elasticsearch fails to start due to RBAC list verb missing

Applying 0.2.0 from #10, elasticsearch would fail to start with an error that it can't list namespaces.

The solution was to patch knative.yaml in a way that is easier said than seded:

--- knative/templates/knative.yaml.org  2018-11-05 15:36:03.000000000 +0100
+++ knative/templates/knative.yaml  2018-11-05 15:36:06.000000000 +0100
@@ -1526,6 +1526,7 @@
   - endpoints
   verbs:
   - get
+  - list
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding

create chart for koby

Outdated version of knative

any chance of a bump to 0.9?

Add chart repo URL and instructions

We need to add the chart repo url config in the README

As well as a bit of instructions

Helm chart for Deploying TriggerMesh Cloud on-prem

CI: Test Charts

knative-serving: add TLS options

Create charts for tm-cloud infrastructure components

triggermesh: missing clusterrole permissions

Running 0.5.2 I get:

17-6502b5e7b1b5+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:56:26.020935       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.GoogleCloudPubSubTarget: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:56:27.642756       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:56:27.642783       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.AzureSentinelTarget: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:56:30.051743       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
E0816 10:56:30.051767       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaSource: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
W0816 10:56:39.570406       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:56:39.570440       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaTarget: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:56:46.145888       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:56:46.146071       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.GoogleCloudPubSubTarget: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:56:47.978727       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:56:47.978753       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.AzureSentinelTarget: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:56:48.124328       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
E0816 10:56:48.124354       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaSource: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
W0816 10:57:19.318363       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:57:19.318388       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaTarget: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:57:24.333727       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:57:24.333759       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.GoogleCloudPubSubTarget: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:57:34.136555       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
E0816 10:57:34.136578       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaSource: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
W0816 10:57:38.104449       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:57:38.104479       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.AzureSentinelTarget: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:57:52.541942       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:57:52.541975       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaTarget: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:58:12.019122       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:58:12.019159       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.AzureSentinelTarget: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:58:15.935878       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
E0816 10:58:15.935902       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaSource: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
W0816 10:58:17.827191       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:58:17.827217       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.GoogleCloudPubSubTarget: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:58:28.244603       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:58:28.244631       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaTarget: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:58:50.780708       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:58:50.780741       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.GoogleCloudPubSubTarget: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:59:04.215836       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:59:04.215960       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.AzureSentinelTarget: failed to list *v1alpha1.AzureSentinelTarget: azuresentineltargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "azuresentineltargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:59:05.565078       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
E0816 10:59:05.565110       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaSource: failed to list *v1alpha1.KafkaSource: kafkasources.sources.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkasources" in API group "sources.triggermesh.io" at the cluster scope
W0816 10:59:13.857656       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:59:13.857680       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.KafkaTarget: failed to list *v1alpha1.KafkaTarget: kafkatargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "kafkatargets" in API group "targets.triggermesh.io" at the cluster scope
W0816 10:59:23.775410       1 reflector.go:324] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope
E0816 10:59:23.775432       1 reflector.go:138] k8s.io/[email protected]+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.GoogleCloudPubSubTarget: failed to list *v1alpha1.GoogleCloudPubSubTarget: googlecloudpubsubtargets.targets.triggermesh.io is forbidden: User "system:serviceaccount:triggermesh:triggermesh-controller" cannot list resource "googlecloudpubsubtargets" in API group "targets.triggermesh.io" at the cluster scope

maybe it's more safe to just use a wildcard on the resources in order to make sure they are included?

Check domain with wildcard

Can we use *.example.com or *example.com as DNS domain.

Check whether the chart fails the substitution or whether knative does not like it.

Create chart for koby

We need koby of the PNC PoC

Remove Istio and use contour

Contour is quite more light weight than Istio for a knative ingress.

Let's use it ?

not parsing knative manifest properly

when trying to install the chart:

$ helm install tm/knative --dry-run
Error: parse error in "knative/templates/knative.yaml": template: knative/templates/knative.yaml:2132: function "destination_service" not defined

related to the dashboar configuration.

https://github.com/knative/serving/releases/download/v0.1.1/release.yaml

Release triggermesh chart with appVersion: 1.10.1

Azure EventHubs source invalid image

Our latest chart is pointing to old Azure EventHub (instead of EventHubS) image:
d722d5a#diff-30d71f72ba5ddef0fe0438757bde96fcfb222ee49ce61e12651eb4c632048756R81

tm-chart: Dashboard not working properly with Ingress disabled

Update chart to use webhook resources from values file

I want to install Triggermesh using the Helm chart in a Kubernetes cluster that have OPA rules that enforce resource requests on all containers. The values.yaml file contains variables for setting this, but this is not used anywhere. An easy fix is to add it to the webhook/deployment.yaml file:

      containers:
        - name: webhook
          ...
          resources:
            {{- toYaml .Values.webhook.resources | nindent 12 }}

Add a chart that has monitoring turned on

currently we installed the release without monitoring.

Let's see if we can add a second chart that is based on the release with monitoring.

Bumping up triggermesh version on helm chart

We noticed that the latest release in helm charts is v1.26.0 see below sample of code:

$ helm search repo triggermesh
NAME                                    CHART VERSION   APP VERSION     DESCRIPTION
triggermesh/triggermesh                 0.8.3           v1.26.0         A Helm chart deploying TriggerMesh Open Source ...
triggermesh/triggermesh-core            1.2.2           v1.4.0          A Helm chart deploying TriggerMesh Core Open So...
triggermesh/aws-event-sources           0.1.14          1.10.0          AWS Event Sources controller for Kubernetes
triggermesh/imagepullsecret-patcher     0.1.2           v0.14           A Helm chart for imagepullsecret-patcher
triggermesh/istio                       0.1.7           1.13.3          A Helm chart for deploying istio
triggermesh/istio-operator              0.1.5           1.13.3          A Helm chart for deploying istio-operator
triggermesh/keycloak                    0.1.6           9.0.3           A Helm chart for deploying Keycloak
triggermesh/knative-eventing            0.5.0           1.4.1           A Helm chart for deploying knative-eventing
triggermesh/knative-operator            0.5.0           v1.4.2          A Helm chart for deploying knative-operator
triggermesh/knative-serving             0.5.0           1.4.0           A Helm chart for deploying knative-serving
triggermesh/knative-sources             0.3.1           v0.25           A Helm chart for deploying knative-sources
triggermesh/knative-targets             0.5.0           v1.4.2          A Helm chart for deploying knative-targets
triggermesh/koby                        0.1.7           v1.21.0         A Helm chart deploying TriggerMesh Koby
triggermesh/tekton                      0.2.0           0.23.0          A Helm chart for deploying tekton
triggermesh/tekton-operator             0.2.0           v0.23.0-2       A Helm chart for deploying tekton-operator
triggermesh/tm-cloud                    0.6.3           v1.10.0         A Helm chart for on-premise deployments of Trig...
triggermesh/triggerflow                 0.1.1           v1.21.0         A Helm chart deploying TriggerFlow

But the latest release in GitHub is 1.27.0.

It would be nice if the chart can deploy the latest version.