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
The field `apiVersion` refers to the API version of Datadog (v1 or v2). Default value is `v1` if this is omitted.
31
30
32
31
!!! note
33
-
Datadog is moving away from the legacy v1 API. Rate limits imposed by Datadog are therefore stricter when using v1. It is recommended to switch to v2 soon. If you switch to v2, you will not need to change any other field aside from `apiVersion`.
32
+
Datadog is moving away from the legacy v1 API. Rate limits imposed by Datadog are therefore stricter when using v1. It is recommended to switch to v2 soon. If you switch to v2, you will not be able to use formulas (operations between individual queries).
34
33
35
34
Datadog api and app tokens can be configured in a kubernetes secret in argo-rollouts namespace.
Copy file name to clipboardExpand all lines: docs/features/traffic-management/index.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,14 +16,15 @@ Service Meshes fill this missing functionality in Kubernetes. They introduce new
16
16
17
17
## How does Argo Rollouts enable traffic management?
18
18
19
-
Argo Rollouts enables traffic management by manipulating the Service Mesh resources to match the intent of the Rollout. Argo Rollouts currently supports the following service meshes:
19
+
Argo Rollouts enables traffic management by manipulating the Service Mesh resources to match the intent of the Rollout. Argo Rollouts currently supports the following traffic providers:
With the introduction of the Kubernetes Gateway API it is now possible to use Argo Rollouts with all compliant implementations that support it. The integration is available with the [Argo Rollouts Gateway API plugin](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/) currently hosted in Argo Labs.
4
+
5
+
Useful resources:
6
+
7
+
*[The Gateway API specification](https://gateway-api.sigs.k8s.io/)
8
+
*[Support of the Gateway API in Kong](https://docs.konghq.com/kubernetes-ingress-controller/latest/concepts/gateway-api/)
9
+
*[Argo Rollouts Plugin capabilities](../plugins/)
10
+
*[Plugin for the Gateway API](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi)
11
+
12
+
The process involves the following steps:
13
+
14
+
1. Installing the Gateway API CRDs in your cluster
15
+
1. Installing Kong and enabling the Gateway API support feature
16
+
1. Creating a GatewayClass and Gateway resources
17
+
1. Installing Argo Rollouts + gateway API plugin in the cluster
18
+
1. Defining a Rollout that takes advantage of the plugin
19
+
20
+
For a full application that includes all manifests see the [plugin example](https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/tree/main/examples/kong).
0 commit comments