Skip to content

Commit c471219

Browse files
committed
Add Ingress v2 to roadmap
1 parent 3f49d66 commit c471219

File tree

2 files changed

+2
-1
lines changed

2 files changed

+2
-1
lines changed

README.md

+1
Original file line numberDiff line numberDiff line change
@@ -192,6 +192,7 @@ For more details on how the canary analysis and promotion works please [read the
192192
193193
### Roadmap
194194
195+
* Add support for Kubernetes [Ingress v2](https://github.com/kubernetes-sigs/service-apis)
195196
* Integrate with other service mesh like Consul Connect and ingress controllers like HAProxy, ALB
196197
* Integrate with other metrics providers like InfluxDB, Stackdriver, SignalFX
197198
* Add support for comparing the canary metrics to the primary ones and do the validation based on the derivation between the two

docs/gitbook/usage/how-it-works.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
[Flagger](https://github.com/weaveworks/flagger) can be configured to automate the release process
44
for Kubernetes workloads with a custom resource named canary.
55

6-
### Canary custom resource
6+
### Canary resource
77

88
The canary custom resource defines the release process of an application running on Kubernetes
99
and is portable across clusters, service meshes and ingress providers.

0 commit comments

Comments
 (0)