You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-grid/kubernetes/create-topic-subscription.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Azure Event Grid on Kubernetes - Webhook as event handler
3
-
description: This article describes how to create an event grid topic on a Kubernetes cluster that's connected to Azure Arc and then create a subscription for the topic.
3
+
description: This article describes how to create an Event Grid topic on a Kubernetes cluster that's connected to Azure Arc and then create a subscription for the topic.
4
4
author: jfggdl
5
5
ms.subservice: kubernetes
6
6
ms.author: jafernan
@@ -11,7 +11,7 @@ ms.devlang: azurecli
11
11
---
12
12
13
13
# Route cloud events to Webhooks with Azure Event Grid on Kubernetes
14
-
In this quickstart, you'll create a topic in Event Grid on Kubernetes, create a subscription for the topic, and then send a sample event to the topic to test the scenario.
14
+
In this quickstart, you create a topic in Event Grid on Kubernetes, create a subscription for the topic, and then send a sample event to the topic to test the scenario.
@@ -23,7 +23,7 @@ In this quickstart, you'll create a topic in Event Grid on Kubernetes, create a
23
23
24
24
25
25
## Create a custom location
26
-
As an Azure location extension, a custom location lets you use your Azure Arc-enabled Kubernetes cluster as a target location for deploying resources such as Event Grid topics. A custom location represents a namespace in the cluster and it's the place where topics and event subscriptions are deployed. In this section, you'll create a custom location.
26
+
As an Azure location extension, a custom location lets you use your Azure Arc-enabled Kubernetes cluster as a target location for deploying resources such as Event Grid topics. A custom location represents a namespace in the cluster and it's the place where topics and event subscriptions are deployed. In this section, you create a custom location.
27
27
28
28
1. Declare the following variables to hold values of the Azure Arc cluster, resource group, and custom location names. Copy these statements to an editor, replace the values, and then copy/paste to the bash window.
29
29
@@ -42,7 +42,7 @@ As an Azure location extension, a custom location lets you use your Azure Arc-en
42
42
```azurecli-interactive
43
43
clusterextensionid=$(az k8s-extension show --name eventgrid-ext --cluster-type connectedClusters -c $arcclustername -g $resourcegroupname --query id -o tsv)
44
44
```
45
-
1. Create a custom location using the above two values. Update custom location and resource group names before running the command.
45
+
1. Create a custom location using the two values from the previous step. Update custom location and resource group names before running the command.
@@ -56,7 +56,7 @@ As an Azure location extension, a custom location lets you use your Azure Arc-en
56
56
For more information on creating custom locations, see [Create and manage custom locations on Azure Arc-enabled Kubernetes](../../azure-arc/kubernetes/custom-locations.md).
57
57
58
58
## Create a topic
59
-
In this section, you'll create a topic in the custom location you created in the previous step. Update resource group and event grid topic names before running the command. Update the location if you are using a location other than East US.
59
+
In this section, you create a topic in the custom location you created in the previous step. Update resource group and Event Grid topic names before running the command. Update the location if you're using a location other than East US.
60
60
61
61
1. Declare a variable to hold the topic name.
62
62
@@ -73,7 +73,7 @@ In this section, you'll create a topic in the custom location you created in the
73
73
74
74
## Create a message endpoint
75
75
76
-
Before you create a subscription for the custom topic, create an endpoint for the event message. Typically, the endpoint takes actions based on the event data. To simplify this quickstart, you deploy a [pre-built web app](https://github.com/Azure-Samples/azure-event-grid-viewer) that displays the event messages. The deployed solution includes an App Service plan, an App Service web app, and source code from GitHub.
76
+
Before you create a subscription for the custom topic, create an endpoint for the event message. Typically, the endpoint takes actions based on the event data. To simplify this quickstart, you deploy a [prebuilt web app](https://github.com/Azure-Samples/azure-event-grid-viewer) that displays the event messages. The deployed solution includes an App Service plan, an App Service web app, and source code from GitHub.
77
77
78
78
1. In the article page, select **Deploy to Azure** to deploy the solution to your subscription. In the Azure portal, provide values for the parameters.
79
79
@@ -87,7 +87,7 @@ Before you create a subscription for the custom topic, create an endpoint for th
87
87
88
88
89
89
## Create a subscription
90
-
Subscribers can register for events published to a topic. To receive any event, you'll need to create an Event Grid subscription for a topic of interest. An event subscription defines the destination to which those events are sent. To learn about all the destinations or handlers supported, see [Event handlers](event-handlers.md).
90
+
Subscribers can register for events published to a topic. To receive any event, you need to create an Event Grid subscription for a topic of interest. An event subscription defines the destination to which those events are sent. To learn about all the destinations or handlers supported, see [Event handlers](event-handlers.md).
91
91
92
92
To create an event subscription with a WebHook (HTTPS endpoint) destination, enter a name for the event subscription, update the name of the web site, and run the following command.
For more information about the CLI command, see [`az eventgrid event-subscription create`](/cli/azure/eventgrid/event-subscription#az-eventgrid-event-subscription-create).
101
101
102
102
## Send events to the topic
103
-
1. Run the following command to get the **endpoint** for the topic: After you copy and paste the command, update the **topic name** and **resource group name** before you run the command. You'll publish sample events to this topic endpoint.
103
+
1. Run the following command to get the **endpoint** for the topic: After you copy and paste the command, update the **topic name** and **resource group name** before you run the command. You publish sample events to this topic endpoint.
104
104
105
105
```azurecli
106
106
az eventgrid topic show --name $topicname -g $resourcegroupname --query "endpoint" --output tsv
@@ -132,7 +132,7 @@ For more information about the CLI command, see [`az eventgrid event-subscriptio
132
132
133
133
If the topic endpoint URL from step 1 is a private IP address, such as in the case when Event Grid broker's service type is ClusterIP, you can execute **Curl** from within another pod in the cluster to have access to that IP address. For example, you can perform the following steps:
134
134
135
-
1. Create a manifest file with the following configuration. You may want to adjust the ``dnsPolicy`` according to your needs. Consult [DNS for Services and Pods](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/) for more information.
135
+
1. Create a manifest file with the following configuration. You may want to adjust the ``dnsPolicy`` according to your needs. For more information, see [DNS for Services and Pods](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/).
136
136
137
137
```yml
138
138
apiVersion: v1
@@ -159,7 +159,7 @@ For more information about the CLI command, see [`az eventgrid event-subscriptio
159
159
kubectl exec --stdin --tty test-pod -- /bin/bash
160
160
```
161
161
162
-
At this point, you have a shell session from a running container in the cluster from which you can execute the **Curl** command described in an earlier step above.
162
+
At this point, you have a shell session from a running container in the cluster from which you can execute the **Curl** command described in an earlier step.
163
163
164
164
> [!NOTE]
165
165
> To learn how to send cloud events using programming languages, see the following samples:
Copy file name to clipboardExpand all lines: articles/event-grid/kubernetes/event-handlers.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ An event handler is any system that exposes an endpoint and is the destination f
13
13
14
14
The way to configure Event Grid to send events to a destination is through the creation of an event subscription. It can be done through [Azure CLI](/cli/azure/eventgrid/event-subscription#az-eventgrid-event-subscription-create), [management SDK](../sdk-overview.md#management-sdks), or using direct HTTPs calls using the [2020-10-15-preview API](/rest/api/eventgrid/controlplane-version2021-10-15-preview/event-subscriptions/create-or-update) version.
15
15
16
-
In general, Event Grid on Kubernetes can send events to any destination via **Webhooks**. Webhooks are HTTP(s) endpoints exposed by a service or workload to which Event Grid has access. The webhook can be a workload hosted in the same cluster, in the same network space, on the cloud, on-prem or anywhere that Event Grid can reach.
16
+
In general, Event Grid on Kubernetes can send events to any destination via **Webhooks**. Webhooks are HTTP(s) endpoints exposed by a service or workload to which Event Grid has access. The webhook can be a workload hosted in the same cluster, in the same network space, on the cloud, on-premises or anywhere that Event Grid can reach.
@@ -38,10 +38,10 @@ Event Grid on Kubernetes offers a good level of feature parity with Azure Event
38
38
39
39
1. Use [REST api version 2020-10-15-preview](/rest/api/eventgrid/controlplane-version2021-10-15-preview/event-subscriptions).
40
40
2.[Azure Event Grid trigger for Azure Functions](../../azure-functions/functions-bindings-event-grid-trigger.md?tabs=csharp%2Cconsole) isn't supported. You can use a WebHook destination type to deliver events to Azure Functions.
41
-
3. There's no [dead letter location](../manage-event-delivery.md#set-dead-letter-location) support. That means that you cannot use ``properties.deadLetterDestination`` in your event subscription payload.
41
+
3. There's no [dead letter location](../manage-event-delivery.md#set-dead-letter-location) support. That means that you can't use ``properties.deadLetterDestination`` in your event subscription payload.
42
42
4. Azure Relay's Hybrid Connections as a destination isn't supported yet.
43
43
5. Only CloudEvents schema is supported. The supported schema value is "[CloudEventSchemaV1_0](/rest/api/eventgrid/controlplane-version2021-10-15-preview/event-subscriptions/create-or-update#eventdeliveryschema)". Cloud Events schema is extensible and based on open standards.
44
-
6. Labels ([properties.labels](/rest/api/eventgrid/controlplane-version2021-10-15-preview/event-subscriptions/create-or-update#request-body)) aren't applicable to Event Grid on Kubernetes. Hence, they are not available.
44
+
6. Labels ([properties.labels](/rest/api/eventgrid/controlplane-version2021-10-15-preview/event-subscriptions/create-or-update#request-body)) aren't applicable to Event Grid on Kubernetes. Hence, they aren't available.
45
45
7.[Delivery with resource identity](/rest/api/eventgrid/controlplane-version2021-10-15-preview/event-subscriptions/create-or-update#deliverywithresourceidentity) isn't supported. So, all properties for [Event Subscription Identity](/rest/api/eventgrid/controlplane-version2021-10-15-preview/event-subscriptions/create-or-update#eventsubscriptionidentity) aren't supported.
@@ -74,7 +74,7 @@ To publish to a WebHook endpoint, set the `endpointType` to `WebHook` and provid
74
74
75
75
To publish to an Azure Event Grid cloud endpoint, set the `endpointType` to `WebHook` and provide:
76
76
77
-
* **endpointUrl**: Azure event grid topic URL in the cloud with the API version parameter set to **2018-01-01** and `aeg-sas-key` set to the URL encoded SAS key.
77
+
* **endpointUrl**: Azure Event Grid topic URL in the cloud with the API version parameter set to **2018-01-01** and `aeg-sas-key` set to the URL encoded SAS key.
78
78
79
79
```json
80
80
{
@@ -91,7 +91,7 @@ To publish to an Azure Event Grid cloud endpoint, set the `endpointType` to `Web
91
91
92
92
## Event Hubs
93
93
94
-
To publish to an Event Hub, set the `endpointType` to `eventHub` and provide:
94
+
To publish to an Event Hubs, set the `endpointType` to `eventHub` and provide:
95
95
96
96
***resourceId**: resource ID for the specific event hub.
Copy file name to clipboardExpand all lines: articles/event-grid/kubernetes/features.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.topic: conceptual
11
11
# Event Grid on Kubernetes with Azure Arc features
12
12
Event Grid on Kubernetes offers a rich set of features that help you integrate your Kubernetes workloads and realize hybrid architectures. It shares the same [rest API](/rest/api/eventgrid/controlplane-version2021-10-15-preview/topics) (starting with version 2020-10-15-preview), [Event Grid CLI](/cli/azure/eventgrid), Azure portal experience, [management SDKs](../sdk-overview.md#management-sdks), and [data plane SDKs](../sdk-overview.md#data-plane-sdks) with Azure Event Grid, the other edition of the same service. When you're ready to publish events, you can use the [data plane SDK examples provided in different languages](https://devblogs.microsoft.com/azure-sdk/event-grid-ga/) that work for both editions of Event Grid.
13
13
14
-
Although Event Grid on Kubernetes and Azure Event Grid share many features and the goal is to provide the same user experience, there are some differences given the unique requirements they seek to meet and the stage in which they are on their software lifecycle. For example, the only type of topic available in Event Grid on Kubernetes are Event Grid Topics that sometimes are also referred as custom topics. Other types of topics (see below) are either not applicable or support for them is not yet available. The main differences between the two editions of Event Grid are presented in the table below.
14
+
Although Event Grid on Kubernetes and Azure Event Grid share many features and the goal is to provide the same user experience, there are some differences given the unique requirements they seek to meet and the stage in which they are on their software lifecycle. For example, the only type of topic available in Event Grid on Kubernetes are Event Grid topics that sometimes are also referred as custom topics. Other types of topics are either not applicable or support for them isn't yet available. The main differences between the two editions of Event Grid are presented in the following table.
0 commit comments