Skip to content
This repository was archived by the owner on May 5, 2025. It is now read-only.

Commit 16ad2eb

Browse files
jmcxjmcx
committed
Serving install fix & tmctl supported connectors
1 parent c7ff199 commit 16ad2eb

File tree

4 files changed

+172
-6
lines changed

4 files changed

+172
-6
lines changed

‎docs/installation/kubernetes-helm.md

+83-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,89 @@ This guide takes you through installing TriggerMesh on a Kubernetes cluster usin
1414

1515
## Install Knative Serving
1616

17-
--8<-- "includes/install-knative-serving.md"
17+
<!--
18+
when we fix includes, we can do this instead:
19+
--8<-- "includes/install-knative-serving.md"
20+
-->
21+
22+
TriggerMesh relies on [Knative Serving](https://knative.dev/docs/concepts/#knative-serving) to run some of its components as Knative Services. We plan to relax this dependency in the near future. While we recommend following the official [installation instructions](https://knative.dev/docs/install/operator/knative-with-operators/), the remainder of this section serves as a quick guide for installing the Knative components.
23+
24+
Begin by installing the Knative Operator:
25+
26+
```sh
27+
kubectl apply -f https://github.com/knative/operator/releases/download/knative-v1.8.1/operator.yaml -n default
28+
```
29+
30+
Check the status of the Operator by running the command:
31+
32+
```sh
33+
kubectl get deployment knative-operator -n default
34+
```
35+
36+
Now install the Knative Serving component with the Kourier Networking layer:
37+
38+
```sh
39+
kubectl apply -f - <<EOF
40+
apiVersion: v1
41+
kind: Namespace
42+
metadata:
43+
name: knative-serving
44+
---
45+
apiVersion: operator.knative.dev/v1beta1
46+
kind: KnativeServing
47+
metadata:
48+
name: knative-serving
49+
namespace: knative-serving
50+
spec:
51+
ingress:
52+
kourier:
53+
enabled: true
54+
config:
55+
network:
56+
ingress-class: "kourier.ingress.networking.knative.dev"
57+
EOF
58+
```
59+
60+
Check the status of Knative Serving Custom Resource using the command (can take a minute before it displays as ready):
61+
62+
```sh
63+
kubectl get KnativeServing knative-serving -n knative-serving
64+
```
65+
66+
Finally configure Knative Serving to use Magic DNS (sslip.io) with:
67+
68+
```sh
69+
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.8.3/serving-default-domain.yaml
70+
```
71+
72+
Refer to the [official documentation](https://knative.dev/docs/install/operator/knative-with-operators/#configure-dns) if you want to use a real DNS instead.
73+
74+
This concludes the installation of Knative Serving.
75+
76+
**Optionally**, you can install [Knative Eventing](https://knative.dev/docs/concepts/#knative-eventing). Knative Eventing is not a prerequisite for TriggerMesh to run, but we do provide [compatibility for Knative Eventing users](triggermesh-knative.md).
77+
78+
Install Knative Eventing using the command:
79+
80+
```sh
81+
kubectl apply -f - <<EOF
82+
apiVersion: v1
83+
kind: Namespace
84+
metadata:
85+
name: knative-eventing
86+
---
87+
apiVersion: operator.knative.dev/v1beta1
88+
kind: KnativeEventing
89+
metadata:
90+
name: knative-eventing
91+
namespace: knative-eventing
92+
EOF
93+
```
94+
95+
Check the status of Knative Eventing Custom Resource using the command:
96+
97+
```sh
98+
kubectl get KnativeEventing knative-eventing -n knative-eventing
99+
```
18100

19101
## Install the TriggerMesh Helm chart
20102

‎docs/installation/kubernetes-yaml.md

+83-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,89 @@ This guide takes you through installing TriggerMesh on a Kubernetes cluster by u
1313

1414
## Install Knative Serving
1515

16-
--8<-- "includes/install-knative-serving.md"
16+
<!--
17+
when we fix includes, we can do this instead:
18+
--8<-- "includes/install-knative-serving.md"
19+
-->
20+
21+
TriggerMesh relies on [Knative Serving](https://knative.dev/docs/concepts/#knative-serving) to run some of its components as Knative Services. We plan to relax this dependency in the near future. While we recommend following the official [installation instructions](https://knative.dev/docs/install/operator/knative-with-operators/), the remainder of this section serves as a quick guide for installing the Knative components.
22+
23+
Begin by installing the Knative Operator:
24+
25+
```sh
26+
kubectl apply -f https://github.com/knative/operator/releases/download/knative-v1.8.1/operator.yaml -n default
27+
```
28+
29+
Check the status of the Operator by running the command:
30+
31+
```sh
32+
kubectl get deployment knative-operator -n default
33+
```
34+
35+
Now install the Knative Serving component with the Kourier Networking layer:
36+
37+
```sh
38+
kubectl apply -f - <<EOF
39+
apiVersion: v1
40+
kind: Namespace
41+
metadata:
42+
name: knative-serving
43+
---
44+
apiVersion: operator.knative.dev/v1beta1
45+
kind: KnativeServing
46+
metadata:
47+
name: knative-serving
48+
namespace: knative-serving
49+
spec:
50+
ingress:
51+
kourier:
52+
enabled: true
53+
config:
54+
network:
55+
ingress-class: "kourier.ingress.networking.knative.dev"
56+
EOF
57+
```
58+
59+
Check the status of Knative Serving Custom Resource using the command (can take a minute before it displays as ready):
60+
61+
```sh
62+
kubectl get KnativeServing knative-serving -n knative-serving
63+
```
64+
65+
Finally configure Knative Serving to use Magic DNS (sslip.io) with:
66+
67+
```sh
68+
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.8.3/serving-default-domain.yaml
69+
```
70+
71+
Refer to the [official documentation](https://knative.dev/docs/install/operator/knative-with-operators/#configure-dns) if you want to use a real DNS instead.
72+
73+
This concludes the installation of Knative Serving.
74+
75+
**Optionally**, you can install [Knative Eventing](https://knative.dev/docs/concepts/#knative-eventing). Knative Eventing is not a prerequisite for TriggerMesh to run, but we do provide [compatibility for Knative Eventing users](triggermesh-knative.md).
76+
77+
Install Knative Eventing using the command:
78+
79+
```sh
80+
kubectl apply -f - <<EOF
81+
apiVersion: v1
82+
kind: Namespace
83+
metadata:
84+
name: knative-eventing
85+
---
86+
apiVersion: operator.knative.dev/v1beta1
87+
kind: KnativeEventing
88+
metadata:
89+
name: knative-eventing
90+
namespace: knative-eventing
91+
EOF
92+
```
93+
94+
Check the status of Knative Eventing Custom Resource using the command:
95+
96+
```sh
97+
kubectl get KnativeEventing knative-eventing -n knative-eventing
98+
```
1799

18100
## Install the TriggerMesh CRDs
19101

‎docs/sources/azureeventgrid.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,9 @@ Consumes events from [Azure EventGrid](https://learn.microsoft.com/en-us/azure/e
44

55
With `tmctl`:
66

7-
!!! warning "Work in progress"
8-
This component is not yet available with `tmctl`.
7+
```
8+
tmctl create source azureeventgrid --scope <scope> --endpoint.eventHubs.namespaceID <namespaceID> --auth.servicePrincipal.tenantID <tenantID> --auth.servicePrincipal.clientID <clientID> --auth.servicePrincipal.clientSecret <clientSecret>
9+
```
910

1011
On Kubernetes:
1112

‎docs/sources/googlecloudbilling.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,9 @@ over a [Google Cloud Pub/Sub][gc-billing-events] topic.
55

66
With `tmctl`:
77

8-
!!! warning "Work in progress"
9-
This component is not yet available with `tmctl`.
8+
```
9+
tmctl create source googlecloudbilling --billingAccountId <billingAccountId> --budgetId <budgetId> --pubsub.project <project> --serviceAccountKey=/tmp/test
10+
```
1011

1112
On Kubernetes:
1213

0 commit comments

Comments
 (0)