spec.replicas
changes to the primary deployment.skipAnalysis: true
), wait for the initialization to finish, and disable it afterward (skipAnalysis: false
).AlertProivder
, MetricProvider
and Gloo Upsteream
). If you're in a multi-tenant environment and wish to disable this, you can do so through the no-cross-namespace-refs
flag.podinfo
, you can define a canary like:service.name
is not specified, then targetRef.name
is used for the apex domain and canary/primary services name prefix. You should treat the service name as an immutable field; changing its could result in routing conflicts.<service.name>.<namespace>.svc.cluster.local
app=<name>-primary
<service.name>-primary.<namespace>.svc.cluster.local
app=<name>-primary
<service.name>-canary.<namespace>.svc.cluster.local
app=<name>
podinfo.test:9898
will be routed to the latest stable release of your app.podinfo-canary.test:9898
address is available only during the canary analysis and can be used for conformance testing or load testing.9090
over mTLS:8080
and 9090
will be added to the ClusterIP services.app: <DEPLOYMENT-NAME>
:app
, Flagger supports name
and app.kubernetes.io/name
selectors. If you use a different convention, you can specify your label with the -selector-labels
flag. For example:app
,name
,app.kubernetes.io/name
.-primary
. This rewrite can be used to spread the pods created by the canary and primary deployments across different availability zones.app
, name
or app.kubernetes.io/name
.Note that the metric interval should be lower or equal to the control loop interval.
reporter="source"
. For example, to calculate HTTP requests error percentage, the query would be:frontend
workload inside the mesh on frontend.test.svc.cluster.local:9898
and outside the mesh on frontend.example.com
. You'll have to specify an Istio ingress gateway for external hosts.http://backend.test.svc.cluster.local:9898
, the service spec can contain only the container port and the traffic policy:Delegation
is enabled, Flagger would generate Istio VirtualService without hosts and gateway, making the service compatible with Istio delegation./podinfo
by the above delegate VirtualService.PILOT_ENABLE_VIRTUAL_SERVICE_DELEGATE
must also be set. For the use of Istio Delegation, you can refer to the documentation of Virtual Service and pilot environment variables.mesh
gateway.ISTIO_MUTUAL
: