diff --git a/content/docs/reference/commands/mixc/index.html b/content/docs/reference/commands/mixc/index.html index bb92c00102..f77ee81684 100644 --- a/content/docs/reference/commands/mixc/index.html +++ b/content/docs/reference/commands/mixc/index.html @@ -37,6 +37,11 @@ which parameters in order to perform the checks and allocations.

List of name/value bytes attributes specified as name1=b0:b1:b3,name2=b4:b5:b6,... (default ``) +--concurrency <int> +-c +Controls the number of workers used to send requests to Mixer concurrently. (default `1`) + + --double_attributes <string> -d List of name/value float64 attributes specified as name1=value1,name2=value2,... (default ``) @@ -57,11 +62,21 @@ which parameters in order to perform the checks and allocations.

Address and port of a running Mixer instance (default `localhost:9091`) +--print_response + +Whether to print mixer's response, useful when generating heavy load with mixc. + + --quotas <string> -q List of quotas to allocate specified as name1=amount1,name2=amount2,... (default ``) +--rate <int> + +Maximum number of requests per second sent by each worker. (default `-1`) + + --repeat <int> -r Sends the specified number of requests in quick succession (default `1`) @@ -128,6 +143,11 @@ which parameters in order to output the telemetry.

List of name/value bytes attributes specified as name1=b0:b1:b3,name2=b4:b5:b6,... (default ``) +--concurrency <int> +-c +Controls the number of workers used to send requests to Mixer concurrently. (default `1`) + + --double_attributes <string> -d List of name/value float64 attributes specified as name1=value1,name2=value2,... (default ``) @@ -148,6 +168,16 @@ which parameters in order to output the telemetry.

Address and port of a running Mixer instance (default `localhost:9091`) +--print_response + +Whether to print mixer's response, useful when generating heavy load with mixc. + + +--rate <int> + +Maximum number of requests per second sent by each worker. (default `-1`) + + --repeat <int> -r Sends the specified number of requests in quick succession (default `1`) diff --git a/content/docs/reference/commands/pilot-agent/index.html b/content/docs/reference/commands/pilot-agent/index.html index 03f84552eb..c627fe90bd 100644 --- a/content/docs/reference/commands/pilot-agent/index.html +++ b/content/docs/reference/commands/pilot-agent/index.html @@ -165,7 +165,7 @@ number_of_entries: 5 --serviceregistry <string> -Select the platform for service registry, options are {Kubernetes, Consul, CloudFoundry, Mock, Config} (default `Kubernetes`) +Select the platform for service registry, options are {Kubernetes, Consul, MCP, Mock, Config} (default `Kubernetes`) --statsdUdpAddress <string> diff --git a/content/docs/reference/commands/pilot-discovery/index.html b/content/docs/reference/commands/pilot-discovery/index.html index 1f65346b92..ab326dc161 100644 --- a/content/docs/reference/commands/pilot-discovery/index.html +++ b/content/docs/reference/commands/pilot-discovery/index.html @@ -84,11 +84,6 @@ number_of_entries: 5 The location of the certificate file for mutual TLS (default `/etc/istio/certs/cert-chain.pem`) ---cfConfig <string> - -Cloud Foundry config file (default ``) - - --clusterRegistriesConfigMap <string> ConfigMap map for clusters config store (default ``) @@ -236,7 +231,7 @@ number_of_entries: 5 --registries <stringSlice> -Comma separated list of platform service registries to read from (choose one or more from {Kubernetes, Consul, CloudFoundry, Mock, Config}) (default `[Kubernetes]`) +Comma separated list of platform service registries to read from (choose one or more from {Kubernetes, Consul, MCP, Mock, Config}) (default `[Kubernetes]`) --resync <duration> diff --git a/content/docs/reference/config/istio.networking.v1alpha3/index.html b/content/docs/reference/config/istio.networking.v1alpha3/index.html index a2bf7f1fd4..c20ea24a69 100644 --- a/content/docs/reference/config/istio.networking.v1alpha3/index.html +++ b/content/docs/reference/config/istio.networking.v1alpha3/index.html @@ -6,7 +6,7 @@ layout: protoc-gen-docs generator: protoc-gen-docs aliases: - /docs/reference/config/istio.routing.v1alpha1/ -number_of_entries: 50 +number_of_entries: 51 ---

Configuration affecting traffic routing. Here are a few terms useful to define in the context of traffic routing.

@@ -571,130 +571,6 @@ sizes, outlier detection).

One or more named sets that represent individual versions of a service. Traffic policies can be overridden at subset level.

- - - - - -

DestinationWeight

-
-

Each routing rule is associated with one or more service versions (see -glossary in beginning of document). Weights associated with the version -determine the proportion of traffic it receives. For example, the -following rule will route 25% of traffic for the “reviews” service to -instances with the “v2” tag and the remaining traffic (i.e., 75%) to -“v1”.

- -
apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
-  name: reviews-route
-spec:
-  hosts:
-  - reviews.prod.svc.cluster.local
-  http:
-  - route:
-    - destination:
-        host: reviews.prod.svc.cluster.local
-        subset: v2
-      weight: 25
-    - destination:
-        host: reviews.prod.svc.cluster.local
-        subset: v1
-      weight: 75
-
- -

And the associated DestinationRule

- -
apiVersion: networking.istio.io/v1alpha3
-kind: DestinationRule
-metadata:
-  name: reviews-destination
-spec:
-  host: reviews.prod.svc.cluster.local
-  subsets:
-  - name: v1
-    labels:
-      version: v1
-  - name: v2
-    labels:
-      version: v2
-
- -

Traffic can also be split across two entirely different services without -having to define new subsets. For example, the following rule forwards 25% of -traffic to reviews.com to dev.reviews.com

- -
apiVersion: networking.istio.io/v1alpha3
-kind: VirtualService
-metadata:
-  name: reviews-route-two-domains
-spec:
-  hosts:
-  - reviews.com
-  http:
-  - route:
-    - destination:
-        host: dev.reviews.com
-      weight: 25
-    - destination:
-        host: reviews.com
-      weight: 75
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -1711,7 +1587,7 @@ number of retries attempted depends on the httpReqTimeout.

HTTPRewrite can be used to rewrite specific parts of a HTTP request before forwarding the request to the destination. Rewrite primitive can -be used only with the DestinationWeights. The following example +be used only with HTTPRouteDestination. The following example demonstrates how to rewrite the URL prefix for api call (/ratings) to ratings service before making the actual API call.

@@ -1791,7 +1667,7 @@ is matched if any one of the match blocks succeed.

- + - + @@ -1882,7 +1758,167 @@ destination service.

+ + + + + + + + + + + + + + + + + +
FieldTypeDescription
destinationDestination -

REQUIRED. Destination uniquely identifies the instances of a service -to which the request/connection should be forwarded to.

- -
weightint32 -

REQUIRED. The proportion of traffic to be forwarded to the service -version. (0-100). Sum of weights across destinations SHOULD BE == 100. -If there is only one destination in a rule, the weight value is assumed to -be 100.

- -
appendHeadersmap<string, string> -

Additional HTTP headers to add before forwarding a request to the -destination service.

- -
removeResponseHeadersstring[] -

Http headers to remove before returning the response to the caller

- -
appendResponseHeadersmap<string, string> -

Additional HTTP headers to add before returning a response to the -caller.

-
routeDestinationWeight[]HTTPRouteDestination[]

A http rule can either redirect or forward (default) traffic. The forwarding target can be one of several versions of a service (see @@ -1869,12 +1745,12 @@ for further details about cross origin resource sharing.
appendHeaders map<string, string> -

Additional HTTP headers to add before forwarding a request to the -destination service.

+

Use of append_headers is deprecated. Use the append_request_headers +field instead.
removeResponseHeaders string[] -

Http headers to remove before returning the response to the caller.

+

HTTP headers to remove before returning a response to the caller.

+ +
appendResponseHeadersmap<string, string> +

Additional HTTP headers to add before returning a response to the +caller.

+ +
removeRequestHeadersstring[] +

HTTP headers to remove before forwarding forwarding a request to the +destination service.

+ +
appendRequestHeadersmap<string, string> +

Additional HTTP headers to add before forwarding a request to the +destination service.

+ +
+
+

HTTPRouteDestination

+
+

Each routing rule is associated with one or more service versions (see +glossary in beginning of document). Weights associated with the version +determine the proportion of traffic it receives. For example, the +following rule will route 25% of traffic for the “reviews” service to +instances with the “v2” tag and the remaining traffic (i.e., 75%) to +“v1”.

+ +
apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+  name: reviews-route
+spec:
+  hosts:
+  - reviews.prod.svc.cluster.local
+  http:
+  - route:
+    - destination:
+        host: reviews.prod.svc.cluster.local
+        subset: v2
+      weight: 25
+    - destination:
+        host: reviews.prod.svc.cluster.local
+        subset: v1
+      weight: 75
+
+ +

And the associated DestinationRule

+ +
apiVersion: networking.istio.io/v1alpha3
+kind: DestinationRule
+metadata:
+  name: reviews-destination
+spec:
+  host: reviews.prod.svc.cluster.local
+  subsets:
+  - name: v1
+    labels:
+      version: v1
+  - name: v2
+    labels:
+      version: v2
+
+ +

Traffic can also be split across two entirely different services without +having to define new subsets. For example, the following rule forwards 25% of +traffic to reviews.com to dev.reviews.com

+ +
apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+  name: reviews-route-two-domains
+spec:
+  hosts:
+  - reviews.com
+  http:
+  - route:
+    - destination:
+        host: dev.reviews.com
+      weight: 25
+    - destination:
+        host: reviews.com
+      weight: 75
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2334,6 +2370,42 @@ matching or selection for final routing.

+ + +
FieldTypeDescription
destinationDestination +

REQUIRED. Destination uniquely identifies the instances of a service +to which the request/connection should be forwarded to.

+ +
weightint32 +

REQUIRED. The proportion of traffic to be forwarded to the service +version. (0-100). Sum of weights across destinations SHOULD BE == 100. +If there is only one destination in a rule, the weight value is assumed to +be 100.

+ +
removeResponseHeadersstring[] +

HTTP headers to remove before returning a response to the caller.

+ +
appendResponseHeadersmap<string, string> +

Additional HTTP headers to add before returning a response to the +caller.

+ +
removeRequestHeadersstring[] +

HTTP headers to remove before forwarding forwarding a request to the +destination service.

+ +
appendRequestHeadersmap<string, string> +

Additional HTTP headers to add before forwarding a request to the +destination service.

Valid port number

+
+
+

RouteDestination

+
+

L4 routing rule weighted destination.

+ + + + + + + + + + + + + + + + + + + @@ -2565,7 +2637,7 @@ client certificates for authentication.

ServiceEntry enables adding additional entries into Istio’s internal service registry, so that auto-discovered services in the mesh can access/route to these manually specified services. A service entry -describes the properties of a service (DNS name, VIPs ,ports, protocols, +describes the properties of a service (DNS name, VIPs, ports, protocols, endpoints). These services could be external to the mesh (e.g., web APIs) or mesh-internal services that are not part of the platform’s service registry (e.g., a set of VMs talking to services in Kubernetes).

@@ -3205,7 +3277,7 @@ is matched if any one of the match blocks succeed.

- + - +
FieldTypeDescription
destinationDestination +

REQUIRED. Destination uniquely identifies the instances of a service +to which the request/connection should be forwarded to.

+ +
weightint32 +

REQUIRED. The proportion of traffic to be forwarded to the service +version. (0-100). Sum of weights across destinations SHOULD BE == 100. +If there is only one destination in a rule, the weight value is assumed to +be 100.

+
routeDestinationWeight[]RouteDestination[]

The destination to which the connection should be forwarded to. Currently, only one destination is allowed for TCP services. When TCP @@ -3340,7 +3412,7 @@ is matched if any one of the match blocks succeed.

routeDestinationWeight[]RouteDestination[]

The destination to which the connection should be forwarded to. Currently, only one destination is allowed for TLS services. When TCP diff --git a/content/docs/reference/config/policy-and-telemetry/adapters/apigee/index.html b/content/docs/reference/config/policy-and-telemetry/adapters/apigee/index.html index adab24b60f..606034e249 100644 --- a/content/docs/reference/config/policy-and-telemetry/adapters/apigee/index.html +++ b/content/docs/reference/config/policy-and-telemetry/adapters/apigee/index.html @@ -4,6 +4,14 @@ description: Adapter for Apigee's distributed policy checks and analytics. location: https://istio.io/docs/reference/config/policy-and-telemetry/adapters/apigee.html layout: partner-component generator: protoc-gen-docs +provider: Apigee +contact_email: +support_link: https://apigee.com/about/support/portal +source_link: https://github.com/apigee/istio-mixer-adapter +latest_release_link: https://github.com/apigee/istio-mixer-adapter/releases +helm_chart_link: +istio_versions: "1.0.0, 1.0.2" +supported_templates: authorization, analytics number_of_entries: 3 ---

The Apigee Mixer adapter provides Apigee’s distributed authentication and quota policy checks diff --git a/content/docs/reference/config/policy-and-telemetry/adapters/cloudmonitor/index.html b/content/docs/reference/config/policy-and-telemetry/adapters/cloudmonitor/index.html index 97b14a8bb5..ec32c06e9f 100644 --- a/content/docs/reference/config/policy-and-telemetry/adapters/cloudmonitor/index.html +++ b/content/docs/reference/config/policy-and-telemetry/adapters/cloudmonitor/index.html @@ -2,7 +2,7 @@ title: CloudMonitor description: Adapter for cloudmonitor metrics. location: https://istio.io/docs/reference/config/policy-and-telemetry/adapters/cloudmonitor.html -layout: partner-adapter +layout: partner-component generator: protoc-gen-docs aliases: - /docs/reference/config/adapters/cloudmonitor.html diff --git a/content/docs/reference/config/policy-and-telemetry/adapters/wavefront/index.html b/content/docs/reference/config/policy-and-telemetry/adapters/wavefront/index.html index 287bacbdf0..513d0fee5e 100644 --- a/content/docs/reference/config/policy-and-telemetry/adapters/wavefront/index.html +++ b/content/docs/reference/config/policy-and-telemetry/adapters/wavefront/index.html @@ -2,7 +2,7 @@ title: Wavefront by VMware description: Adapter to deliver metrics to Wavefront by VMware. location: https://istio.io/docs/reference/config/policy-and-telemetry/adapters/wavefront.html -layout: partner-adapter +layout: partner-component generator: protoc-gen-docs aliases: - /docs/reference/config/adapters/wavefront.html diff --git a/content/docs/reference/config/policy-and-telemetry/templates/analytics/index.html b/content/docs/reference/config/policy-and-telemetry/templates/analytics/index.html index d3d6331a83..f7f5c8e6ca 100644 --- a/content/docs/reference/config/policy-and-telemetry/templates/analytics/index.html +++ b/content/docs/reference/config/policy-and-telemetry/templates/analytics/index.html @@ -2,7 +2,7 @@ title: Analytics description: The Analytics template is used to dispatch runtime telemetry to Apigee. location: https://istio.io/docs/reference/config/policy-and-telemetry/templates/analytics.html -layout: partner-adapter +layout: partner-component generator: protoc-gen-docs number_of_entries: 1 --- diff --git a/layouts/_default/partner-component.html b/layouts/_default/partner-component.html index 3075f3ee3b..096b0564b4 100644 --- a/layouts/_default/partner-component.html +++ b/layouts/_default/partner-component.html @@ -41,7 +41,6 @@ {{ $base := .Site.BaseURL }} {{ range $i, $t := $templates }} - {{- if ne $i 0 -}},{{- end -}} {{ trim $t " " }} {{ end }}