content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
service to inspect the data sent from the clients. The malicious user deploys a forged server with the certificate and key for the `test-team` identity. Suppose the malicious user successfully hijacked (through DNS spoofing, BGP/route hijacking, ARP spoofing, etc.) the traffic sent to the `datastore` and redirected it ... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/security/index.md | master | istio | [
-0.09739044308662415,
0.06496649980545044,
0.016208304092288017,
-0.0057735503651201725,
-0.07714302092790604,
-0.09099163115024567,
0.056944966316223145,
-0.061583176255226135,
0.08663362264633179,
0.03124992921948433,
0.0033176245633512735,
0.06283596158027649,
0.09360525012016296,
0.091... | 0.08487 |
{{< /text >}} #### Policy storage Istio stores mesh-scope policies in the root namespace. These policies have an empty selector apply to all workloads in the mesh. Policies that have a namespace scope are stored in the corresponding namespace. They only apply to workloads within their namespace. If you configure a `sel... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/security/index.md | master | istio | [
-0.0845160037279129,
0.0655730739235878,
-0.027443788945674896,
-0.021379372105002403,
0.04053924232721329,
0.008816740475594997,
0.11901868134737015,
-0.026559364050626755,
0.03554968163371086,
0.03709529712796211,
0.005343909375369549,
-0.050257209688425064,
0.012426421977579594,
0.04406... | 0.311316 |
on port `80` for the `app:example-app` workload, and uses the mutual TLS settings of the namespace-wide peer authentication policy for all other ports: {{< text yaml >}} apiVersion: security.istio.io/v1 kind: PeerAuthentication metadata: name: "example-workload-policy" namespace: "foo" spec: selector: matchLabels: app:... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/security/index.md | master | istio | [
-0.0887279286980629,
0.07599041610956192,
0.026104427874088287,
-0.05196036398410797,
-0.023514501750469208,
-0.10654204338788986,
0.028599988669157028,
-0.01185658574104309,
0.030961645767092705,
0.011061481200158596,
-0.008491692133247852,
-0.008803041651844978,
0.03582033887505531,
0.09... | 0.221851 |
(`ALLOW` and `DENY`) is enforced natively on Envoy. - High compatibility: supports gRPC, HTTP, HTTPS and HTTP/2 natively, as well as any plain TCP protocols. ### Authorization architecture The authorization policy enforces access control to the inbound traffic in the server side Envoy proxy. Each Envoy proxy runs an au... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/security/index.md | master | istio | [
-0.04165971279144287,
0.05349667742848396,
-0.01776021532714367,
0.0031879055313766003,
-0.032854825258255005,
-0.05806319788098335,
0.02809443324804306,
-0.03758144751191139,
-0.00808282382786274,
0.02349567413330078,
-0.03315182402729988,
0.03509094566106796,
-0.024609621614217758,
0.100... | 0.385072 |
policy applies to the namespace in the `metadata/namespace` field. If set its value to the root namespace, the policy applies to all namespaces in a mesh. The value of the root namespace is configurable, and the default is `istio-system`. If set to any other namespace, the policy only applies to the specified namespace... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/security/index.md | master | istio | [
-0.052521515637636185,
0.031143277883529663,
-0.06079474836587906,
0.017372122034430504,
0.023751793429255486,
0.020748699083924294,
0.11054651439189911,
-0.014718045480549335,
0.01705481857061386,
0.02960185706615448,
-0.017625564709305763,
-0.0399574376642704,
0.02322031557559967,
0.0608... | 0.37059 |
security practice to start with the `allow-nothing` policy and incrementally add more `ALLOW` policies to open more access to the workload. {{< /tip >}} {{< text yaml >}} apiVersion: security.istio.io/v1 kind: AuthorizationPolicy metadata: name: allow-nothing spec: action: ALLOW # the rules field is not specified, and ... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/security/index.md | master | istio | [
-0.051431804895401,
0.10138575732707977,
-0.03204299882054329,
0.036904241889715195,
0.03516722843050957,
-0.07176490128040314,
0.03095778450369835,
-0.028954189270734787,
0.014549896121025085,
0.017931809648871422,
-0.001176037359982729,
0.03873923420906067,
-0.01900709792971611,
0.085349... | 0.373631 |
Istio will ignore HTTP-only fields in the authorization policy. Assuming you have a MongoDB service on port `27017`, the following example configures an authorization policy to only allows the `bookinfo-ratings-v2` service in the Istio mesh to access the MongoDB workload. {{< text yaml >}} apiVersion: security.istio.io... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/security/index.md | master | istio | [
-0.01265890896320343,
0.09400206059217453,
-0.06151108071208,
0.04950721934437752,
-0.007281194441020489,
-0.04844490438699722,
0.0011208883952349424,
-0.01682201214134693,
0.025109460577368736,
0.0026894453912973404,
-0.029493290930986404,
-0.08934198319911957,
0.006468712352216244,
0.075... | 0.410597 |
Istio generates detailed telemetry for all service communications within a mesh. This telemetry provides \*observability\* of service behavior, empowering operators to troubleshoot, maintain, and optimize their applications -- without imposing any additional burdens on service developers. Through Istio, operators gain ... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/observability/index.md | master | istio | [
-0.042616430670022964,
-0.030943037942051888,
-0.030498389154672623,
-0.006310340482741594,
0.00274968845769763,
-0.11088572442531586,
0.06736483424901962,
0.031003611162304878,
0.03627638518810272,
0.045144908130168915,
-0.06575285643339157,
-0.08271130174398422,
-0.01316928118467331,
0.0... | 0.604425 |
metrics. The [standard Istio metrics](/docs/reference/config/metrics/) are exported to [Prometheus](/docs/ops/integrations/prometheus/) by default. Use of the service-level metrics is entirely optional. Operators may choose to turn off generation and collection of these metrics to meet their individual needs. Example s... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/observability/index.md | master | istio | [
-0.058268144726753235,
-0.018771423026919365,
-0.05829589441418648,
0.05367583408951759,
-0.05104731395840645,
-0.08118089288473129,
0.021942028775811195,
0.043787725269794464,
0.016140790656208992,
-0.012776916846632957,
-0.04302314296364784,
-0.12458833307027817,
-0.03452248498797417,
0.... | 0.477438 |
Istio provides two primary extension mechanisms. Envoy extensions, described below, and [Extension Providers](/docs/reference/config/istio.mesh.v1alpha1/#MeshConfig-extension\_providers). ## Extending Envoy Proxies Istio provides two mechanisms for extending the Envoy-based proxies: WebAssembly (Wasm) and Lua. Both are... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/extensibility/index.md | master | istio | [
-0.067159004509449,
-0.021173330023884773,
0.025488952174782753,
0.024555403739213943,
-0.008474853821098804,
-0.051302775740623474,
0.02091946080327034,
0.04278524965047836,
-0.022069070488214493,
-0.011182938702404499,
-0.054048843681812286,
-0.044805776327848434,
-0.06542349606752396,
0... | 0.476273 |
show Lua consuming roughly 20–26 MiB regardless of concurrency, while WebAssembly ranges from ~110 MiB at low concurrency to ~290 MiB at high concurrency: | Concurrency | Lua (MiB) | Wasm (MiB) | |---|---|---| | 1 | 19.79 | 117.7 | | 2 | 23.07 | 132.5 | | 4 | 22.63 | 152.0 | | 8 | 23.97 | 190.9 | | 16 | 25.66 | 291.8 | | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/extensibility/index.md | master | istio | [
0.011898618191480637,
-0.06539195775985718,
-0.031642068177461624,
0.008426165208220482,
-0.028855694457888603,
-0.11497082561254501,
-0.03946860134601593,
0.07137248665094376,
-0.01139402948319912,
0.01958480477333069,
0.016644194722175598,
-0.0525457039475441,
-0.0586128868162632,
-0.043... | 0.024197 |
Istio’s traffic routing rules let you easily control the flow of traffic and API calls between services. Istio simplifies configuration of service-level properties like circuit breakers, timeouts, and retries, and makes it easy to set up important tasks like A/B testing, canary rollouts, and staged rollouts with percen... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/traffic-management/index.md | master | istio | [
-0.04999064281582832,
0.007991356775164604,
0.024198805913329124,
0.03684133291244507,
-0.07430686801671982,
-0.043353643268346786,
0.044295381754636765,
0.04068015143275261,
-0.01689995639026165,
0.0720367282629013,
-0.09161596745252609,
-0.04083073139190674,
-0.02220393531024456,
0.02558... | 0.607078 |
the key building blocks of Istio’s traffic routing functionality. A virtual service lets you configure how requests are routed to a service within an Istio service mesh, building on the basic connectivity and discovery provided by Istio and your platform. Each virtual service consists of a set of routing rules that are... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/traffic-management/index.md | master | istio | [
-0.04054543748497963,
0.015055018477141857,
0.0049713184125721455,
-0.018197033554315567,
-0.04258817434310913,
-0.05067434161901474,
0.04616613686084747,
0.011662259697914124,
0.0401817187666893,
0.04960312321782112,
-0.10405579209327698,
-0.08725868910551071,
-0.0544494166970253,
0.03815... | 0.628897 |
in combination with [gateways](/docs/concepts/traffic-management/#gateways) to control ingress and egress traffic. In some cases you also need to configure destination rules to use these features, as these are where you specify your service subsets. Specifying service subsets and other destination-specific policies in ... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/traffic-management/index.md | master | istio | [
-0.040441203862428665,
0.014989973977208138,
-0.026959015056490898,
-0.01647075079381466,
-0.03170381486415863,
-0.02190307527780533,
0.07474179565906525,
-0.01591573841869831,
0.00687381299212575,
0.06245727464556694,
-0.08455917984247208,
-0.06940670311450958,
-0.025078903883695602,
0.04... | 0.36962 |
namespace of the virtual service that contains the routing rule to get the fully qualified name for the host. Using short names in our examples also means that you can copy and try them in any namespace you like. {{< warning >}} Using short names like this only works if the destination hosts and the virtual service are... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/traffic-management/index.md | master | istio | [
-0.0014527782332152128,
0.03157458081841469,
0.07223044335842133,
-0.03006008267402649,
-0.02981792576611042,
-0.02975466661155224,
0.04567128047347069,
-0.043672818690538406,
0.02849651128053665,
0.026420753449201584,
-0.05131732299923897,
-0.10559046268463135,
0.003269929438829422,
-0.01... | 0.098529 |
Rewrite the URL. - Set a [retry policy](#retries) for calls to this destination. To learn more about the actions available, see the [`HTTPRoute` reference](/docs/reference/config/networking/virtual-service/#HTTPRoute). ## Destination rules {#destination-rules} Along with [virtual services](#virtual-services), [destinat... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/traffic-management/index.md | master | istio | [
-0.03874312341213226,
0.00013041791680734605,
-0.00990414060652256,
-0.045066166669130325,
-0.07911020517349243,
-0.04492203891277313,
0.04726701229810715,
0.0011635241098701954,
-0.019310826435685158,
0.024874603375792503,
-0.05392388999462128,
-0.0473070964217186,
-0.03298164904117584,
0... | 0.498409 |
Envoy proxies running alongside your service workloads. Unlike other mechanisms for controlling traffic entering your systems, such as the Kubernetes Ingress APIs, Istio gateways let you use the full power and flexibility of Istio’s traffic routing. You can do this because Istio’s Gateway resource just lets you configu... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/traffic-management/index.md | master | istio | [
-0.031569451093673706,
-0.0072621311992406845,
0.007063264027237892,
0.029715154320001602,
-0.07816177606582642,
-0.018509600311517715,
0.050265122205019,
0.04487687349319458,
0.028998706489801407,
0.06333798915147781,
-0.10159318894147873,
-0.06038440018892288,
-0.052785273641347885,
0.01... | 0.54758 |
dependency to Istio’s service registry: {{< text yaml >}} apiVersion: networking.istio.io/v1 kind: ServiceEntry metadata: name: svc-entry spec: hosts: - ext-svc.example.com ports: - number: 443 name: https protocol: HTTPS location: MESH\_EXTERNAL resolution: DNS {{< /text >}} You specify the external resource using the... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/traffic-management/index.md | master | istio | [
-0.057405829429626465,
0.0007418543682433665,
-0.06234925240278244,
-0.01570468209683895,
-0.036980561912059784,
-0.0654313862323761,
0.03785984218120575,
0.061939336359500885,
0.02759472467005253,
0.028244590386748314,
-0.06919582188129425,
-0.10323672741651535,
-0.048788100481033325,
0.1... | 0.460143 |
subset of the ratings service: {{< text yaml >}} apiVersion: networking.istio.io/v1 kind: VirtualService metadata: name: ratings spec: hosts: - ratings http: - route: - destination: host: ratings subset: v1 timeout: 10s {{< /text >}} ### Retries {#retries} A retry setting specifies the maximum number of times an Envoy ... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/traffic-management/index.md | master | istio | [
-0.045614346861839294,
0.016363156959414482,
-0.010226165875792503,
0.06191130355000496,
-0.04147423058748245,
-0.029637310653924942,
-0.022846270352602005,
0.01523138489574194,
0.032442856580019,
0.0433337576687336,
-0.06001916900277138,
-0.0423244945704937,
-0.04148782417178154,
0.055006... | 0.485763 |
Problems](/docs/ops/common-problems/network-issues/#virtual-service-with-fault-injection-and-retrytimeout-policies-not-working-as-expected). {{< /warning >}} Unlike other mechanisms for introducing errors, such as delaying packets or killing pods at the network layer, Istio lets you inject faults at the application lay... | https://github.com/istio/istio.io/blob/master/content/en/docs/concepts/traffic-management/index.md | master | istio | [
-0.03670685365796089,
0.04760122299194336,
0.035371724516153336,
0.050128258764743805,
0.0167859960347414,
-0.042542245239019394,
0.024587489664554596,
0.04918829724192619,
0.0075031667947769165,
0.045878153294324875,
0.006733329966664314,
-0.0966632217168808,
-0.029250312596559525,
0.0263... | 0.570269 |
From [Kubernetes mutating and validating webhook mechanisms](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/): {{< tip >}} Admission webhooks are HTTP callbacks that receive admission requests and do something with them. You can define two types of admission webhooks, validatin... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/mesh/webhook/index.md | master | istio | [
-0.017160480841994286,
0.05706247687339783,
0.03563544899225235,
-0.04235456511378288,
-0.04443194344639778,
-0.05122114345431328,
0.05658533051609993,
-0.001245046965777874,
-0.029803387820720673,
0.01699102856218815,
-0.01983477920293808,
-0.07899032533168793,
-0.009681065566837788,
-0.0... | 0.29607 |
[Kubernetes liveness and readiness probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/) describes several ways to configure liveness and readiness probes: 1. [Command](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/mesh/app-health-check/index.md | master | istio | [
-0.009743135422468185,
-0.01505522895604372,
-0.008087319321930408,
0.009476871229708195,
0.048456963151693344,
-0.052317555993795395,
-0.008553177118301392,
-0.04781275615096092,
-0.0006080403691157699,
0.053884461522102356,
0.011820671148598194,
-0.04309767112135887,
-0.03895171731710434,
... | 0.17043 |
either for specific pods, or globally. ### Disable the probe rewrite for a pod {#disable-the-http-probe-rewrite-for-a-pod} You can [annotate the pod](/docs/reference/config/annotations/) with `sidecar.istio.io/rewriteAppHTTPProbers: "false"` to disable the probe rewrite option. Make sure you add the annotation to the [... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/mesh/app-health-check/index.md | master | istio | [
0.06185006722807884,
0.07177796214818954,
0.06751523911952972,
0.054819196462631226,
0.0028214440681040287,
-0.050201866775751114,
-0.0371021032333374,
-0.03592769801616669,
0.040220074355602264,
0.04712267592549324,
-0.007767215371131897,
-0.0502486415207386,
-0.06550305336713791,
-0.0095... | 0.239591 |
In order to program the service mesh, the Istio control plane (Istiod) reads a variety of configurations, including core Kubernetes types like `Service` and `Node`, and Istio's own types like `Gateway`. These are then sent to the data plane (see [Architecture](/docs/ops/deployment/architecture/) for more information). ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/mesh/configuration-scoping/index.md | master | istio | [
0.0006586528616026044,
-0.032244451344013214,
0.01604888029396534,
0.0355120413005352,
-0.054421018809080124,
-0.018269076943397522,
0.02298196777701378,
0.0077627976424992085,
0.06517601013183594,
0.04528062418103218,
-0.07990172505378723,
-0.02487867884337902,
-0.06396878510713577,
-0.04... | 0.483904 |
are a few general guidelines: Configuration \*changes\* are expensive in Istio, as they require recomputation. While `Endpoints` changes (generally from a Pod scaling up or down) are heavily optimized, most other configurations are fairly expensive. This can be especially harmful when controllers are constantly making ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/mesh/configuration-scoping/index.md | master | istio | [
0.02588886208832264,
-0.025187797844409943,
-0.008614090271294117,
0.017206521704792976,
-0.029287759214639664,
-0.04669163003563881,
-0.02736142836511135,
0.011036958545446396,
0.04459717869758606,
0.028175950050354004,
-0.018445074558258057,
-0.067215196788311,
-0.09696606546640396,
-0.0... | 0.45622 |
Istio's [default images](https://hub.docker.com/r/istio/base) are based on `ubuntu` with some extra tools added. An alternative image based on [distroless images](https://github.com/GoogleContainerTools/distroless) is also available. These images strip all non-essential executables and libraries, offering the following... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/security/harden-docker-images/index.md | master | istio | [
-0.04601603373885155,
0.045723848044872284,
0.04668300598859787,
-0.006560622714459896,
0.05258415639400482,
-0.0783216804265976,
0.021285543218255043,
0.09109223634004593,
-0.05389908328652382,
-0.008463047444820404,
0.0022791132796555758,
-0.06776539236307144,
0.026723602786660194,
0.077... | 0.518817 |
## Background This page shows common patterns of using Istio security policies. You may find them useful in your deployment or use this as a quick reference to example policies. The policies demonstrated here are just examples and require changes to adapt to your actual environment before applying. Also read the [authe... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/security/security-policy-examples/index.md | master | istio | [
-0.07470351457595825,
0.030035827308893204,
0.016987288370728493,
-0.004513947293162346,
0.019277336075901985,
-0.06733223795890808,
0.044454026967287064,
-0.001396877458319068,
-0.009478329680860043,
0.0085006607696414,
-0.0736173763871193,
-0.09860897809267044,
0.0637679323554039,
0.0603... | 0.364367 |
requests if the request principal is non-empty. `"\*"` means non-empty match and using with `notRequestPrincipals` means matching on empty request principal. {{< text yaml >}} apiVersion: security.istio.io/v1 kind: AuthorizationPolicy metadata: name: require-jwt namespace: istio-system spec: selector: matchLabels: isti... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/security/security-policy-examples/index.md | master | istio | [
-0.061508141458034515,
0.03754042461514473,
-0.031718991696834564,
0.018478073179721832,
-0.016731971874833107,
-0.05180024728178978,
0.06059452146291733,
0.00555202504619956,
0.02899911440908909,
0.0006598623003810644,
-0.0023458111099898815,
-0.1292780190706253,
0.01870296522974968,
0.02... | 0.496117 |
The Envoy proxy keeps detailed statistics about network traffic. Envoy's statistics only cover the traffic for a particular Envoy instance. See [Observability](/docs/tasks/observability/) for persistent per-service Istio telemetry. The statistics the Envoy proxies record can provide more information about specific pod ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/telemetry/envoy-stats/index.md | master | istio | [
0.045138824731111526,
-0.00862127635627985,
0.010525244288146496,
0.06527421623468399,
-0.05054266005754471,
-0.043025605380535126,
0.030084311962127686,
-0.018712220713496208,
0.07430636882781982,
0.07761158794164658,
-0.08753827214241028,
-0.04997667297720909,
-0.027286838740110397,
0.00... | 0.302484 |
## Overview This guide is meant to provide operational guidance on how to configure monitoring of Istio meshes comprised of two or more individual Kubernetes clusters. It is not meant to establish the \*only\* possible path forward, but rather to demonstrate a workable approach to multicluster telemetry with Prometheus... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/telemetry/monitoring-multicluster-prometheus/index.md | master | istio | [
-0.024794910103082657,
-0.004011904820799828,
0.001649116980843246,
0.004726985935121775,
0.011651611886918545,
-0.1072688177227974,
0.007301353849470615,
0.005284816026687622,
0.01663113757967949,
0.03613215684890747,
-0.03600938990712166,
-0.136845201253891,
0.007987601682543755,
0.02731... | 0.446555 |
Production Prometheus on an in-mesh cluster If you prefer to run the production Prometheus in one of the clusters, you need to establish connectivity from it to the other cluster-local Prometheus instances in the mesh. This is really just a variation of the configuration for external federation. In this case the config... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/telemetry/monitoring-multicluster-prometheus/index.md | master | istio | [
-0.015990616753697395,
0.0068253097124397755,
0.004145256243646145,
-0.004465932492166758,
0.027905547991394997,
-0.10629566758871078,
-0.035527054220438004,
-0.006881057750433683,
0.04686965420842171,
0.055184878408908844,
-0.004169912543147802,
-0.13304577767848969,
0.005350116640329361,
... | 0.287184 |
{{< boilerplate alpha >}} The [WasmPlugin API](/docs/reference/config/proxy\_extensions/wasm-plugin) provides a method for [distributing Wasm modules](/docs/tasks/extensibility/wasm-modules) to proxies. Since each proxy will pull Wasm modules from a remote registry or an HTTP server, understanding how Istio chooses to ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/extensibility/wasm-pull-policy/index.md | master | istio | [
-0.024982687085866928,
-0.002129376633092761,
0.004114790353924036,
0.04092741757631302,
0.007795403711497784,
-0.046361926943063736,
0.07208060473203659,
0.07489326596260071,
-0.03860577195882797,
0.023804251104593277,
0.0008286066586151719,
-0.021358169615268707,
-0.037983428686857224,
0... | 0.525263 |
One of Istio's most important features is the ability to lock down and secure network traffic to, from, and within the mesh. However, configuring TLS settings can be confusing and a common source of misconfiguration. This document attempts to explain the various connections involved when sending requests in Istio and h... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/tls-configuration/index.md | master | istio | [
-0.07286524027585983,
0.070283442735672,
0.006958166602998972,
0.0600174255669117,
-0.024821102619171143,
-0.047521717846393585,
0.0706973746418953,
0.009776609018445015,
0.01816898211836815,
-0.03662935271859169,
-0.013237755745649338,
-0.056702032685279846,
-0.02086719125509262,
0.034830... | 0.474135 |
or a web browser. This is often called the "downstream" connection. 1. The outbound request, initiated by the gateway to some backend. This is often called the "upstream" connection. Both of these connections have independent TLS configurations. Note that the configuration of ingress and egress gateways are identical. ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/tls-configuration/index.md | master | istio | [
-0.06279202550649643,
0.02328052744269371,
-0.04058167338371277,
0.03321026265621185,
-0.050638895481824875,
-0.08721575140953064,
0.051207415759563446,
0.04218737781047821,
0.1125103086233139,
0.015063331462442875,
-0.052529316395521164,
-0.02081492356956005,
-0.03108116053044796,
0.02464... | 0.524528 |
Istio supports proxying any TCP traffic. This includes HTTP, HTTPS, gRPC, as well as raw TCP protocols. In order to provide additional capabilities, such as routing and rich metrics, the protocol must be determined. This can be done automatically or explicitly specified. Non-TCP based protocols, such as UDP, are not pr... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/protocol-selection/index.md | master | istio | [
-0.02888612076640129,
-0.0199680645018816,
0.012393676675856113,
-0.003803395899012685,
-0.09407202154397964,
-0.03712528198957443,
0.07327099144458771,
0.024528583511710167,
0.002641476457938552,
0.028393378481268883,
-0.06988386064767838,
-0.08423212170600891,
-0.024082276970148087,
0.04... | 0.572038 |
{{< boilerplate alpha >}} {{< boilerplate gateway-api-support >}} ## Forwarding external client attributes (IP address, certificate info) to destination workloads Many applications require knowing the client IP address and certificate information of the originating request to behave properly. Notable cases include logg... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/network-topologies/index.md | master | istio | [
-0.0633092001080513,
0.006864258553832769,
0.0240151546895504,
-0.03898538649082184,
0.03799926117062569,
0.003736987942829728,
0.06290918588638306,
0.01182647980749607,
0.039052899926900864,
-0.029256276786327362,
-0.039259832352399826,
-0.030864225700497627,
0.030667640268802643,
0.01503... | 0.24909 |
numTrustedProxies: 2 EOF $ istioctl install -f topology.yaml {{< /text >}} {{< idea >}} If you previously installed an Istio ingress gateway, restart all ingress gateway pods after step 1. {{}} 1. Create an `httpbin` namespace: {{< text syntax=bash snip\_id=create\_httpbin\_namespace >}} $ kubectl create namespace http... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/network-topologies/index.md | master | istio | [
-0.00009113273699767888,
0.008572145365178585,
0.007493129000067711,
0.023617176339030266,
-0.07544652372598648,
0.019812224432826042,
0.005528808571398258,
-0.0008509671315550804,
-0.017216570675373077,
0.06843465566635132,
-0.0058766999281942844,
-0.10222211480140686,
-0.02349701151251793,... | 0.348474 |
certificate information and send it to the next hop. This is the default value for a gateway. | | `ALWAYS\_FORWARD\_ONLY` | Always forward the XFCC header in the request, regardless of whether the client connection is mTLS. | See the [Envoy documentation](https://www.envoyproxy.io/docs/envoy/latest/configuration/http/h... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/network-topologies/index.md | master | istio | [
-0.08659987896680832,
0.07792627811431885,
-0.014040878973901272,
0.06098594143986702,
-0.020141635090112686,
-0.016155123710632324,
0.052907176315784454,
0.021949579939246178,
0.03831969201564789,
-0.016647275537252426,
-0.07075154036283493,
-0.04183115065097809,
0.05867279693484306,
-0.0... | 0.149282 |
In addition to capturing application traffic, Istio can also capture DNS requests to improve the performance and usability of your mesh. When proxying DNS, all DNS requests from an application will be redirected to the sidecar or ztunnel proxy, which stores a local mapping of domain names to IP addresses. If the reques... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/dns-proxy/index.md | master | istio | [
-0.05632871761918068,
-0.005151445046067238,
0.07589572668075562,
-0.04325877130031586,
-0.1123386025428772,
-0.034469980746507645,
-0.0033161004539579153,
0.005125497933477163,
0.0844670906662941,
0.012581069022417068,
-0.09748634696006775,
-0.052936453372240067,
-0.06423185765743256,
-0.... | 0.427044 |
response, and will need to forward DNS requests upstream. This is especially problematic with TCP traffic. Unlike HTTP requests, which are routed based on `Host` headers, TCP carries much less information; you can only route on the destination IP and port number. Because you don't have a stable IP for the backend, you ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/dns-proxy/index.md | master | istio | [
-0.08596343547105789,
-0.02574872598052025,
0.0010632596677169204,
-0.03383743762969971,
-0.15342161059379578,
-0.0612085796892643,
0.0420045331120491,
0.0258368868380785,
-0.0023362687788903713,
-0.008611467666924,
-0.11937328428030014,
-0.06841767579317093,
-0.04689507186412811,
0.044717... | 0.462406 |
to `mysql-instance2` because it has no way of distinguishing whether traffic arriving at `0.0.0.0:{port}` is bound for `mysql-instance1` or `mysql-instance2`. The following example shows how DNS proxying can be used to solve this problem. A virtual IP address will be assigned to every service entry so that client sidec... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/dns-proxy/index.md | master | istio | [
-0.016076553612947464,
-0.018479662016034126,
0.0025853831321001053,
-0.04314765706658363,
-0.0996047779917717,
-0.032683007419109344,
0.06271065026521683,
-0.000618800288066268,
0.03872152790427208,
0.0031910534016788006,
-0.07091906666755676,
-0.15829719603061676,
0.04164955019950867,
-0... | 0.276761 |
Within a multicluster mesh, traffic rules specific to the cluster topology may be desirable. This document describes a few ways to manage traffic in a multicluster mesh. Before reading this guide: 1. Read [Deployment Models](/docs/ops/deployment/deployment-models/#multiple-clusters) 1. Make sure your deployed services ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/multicluster/index.md | master | istio | [
0.016672266647219658,
-0.02693856693804264,
-0.0026814790908247232,
-0.03726908192038536,
-0.03802350163459778,
-0.02647634968161583,
0.006417443510144949,
-0.013314621523022652,
0.0018593992572277784,
0.06899908930063248,
-0.0663861483335495,
-0.11740102618932724,
0.018665501847863197,
0.... | 0.291472 |
Istio interacts with DNS in different ways that can be confusing to understand. This document provides a deep dive into how Istio and DNS work together. {{< warning >}} This document describes low level implementation details. For a higher level overview, check out the traffic management [Concepts](/docs/concepts/traff... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/dns/index.md | master | istio | [
-0.09014489501714706,
0.005734010133892298,
0.040798164904117584,
0.012070323340594769,
-0.08130302280187607,
-0.08556284010410309,
0.004060767590999603,
0.04733773693442345,
0.0881209522485733,
-0.01954631134867668,
-0.07327835261821747,
-0.03456546738743782,
-0.04380640387535095,
0.03056... | 0.641737 |
the configured hostnames and uses those results for all requests. This interval is fixed at 30 seconds and cannot be changed at this time. DNS resolution occurs even if the proxy never sends any requests to the associated services. For meshes with many proxies or many `resolution: DNS` type `ServiceEntries`, especially... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/dns/index.md | master | istio | [
-0.0906849279999733,
0.032017987221479416,
0.05406331643462181,
0.020960837602615356,
-0.13673347234725952,
-0.0958925262093544,
0.000839346379507333,
0.0011012956965714693,
0.01901222951710224,
0.0075756944715976715,
-0.07798372209072113,
-0.004485124256461859,
-0.06451523303985596,
0.010... | 0.395395 |
One of the goals of Istio is to act as a "transparent proxy" which can be dropped into an existing cluster, allowing traffic to continue to flow as before. However, there are powerful ways Istio can manage traffic differently than a typical Kubernetes cluster because of the additional features such as request load bala... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/traffic-routing/index.md | master | istio | [
0.0046871439553797245,
-0.004176406189799309,
0.024532660841941833,
0.027833549305796623,
-0.04116512089967728,
-0.02955944649875164,
0.042468562722206116,
0.025862891227006912,
0.0454593226313591,
0.046034298837184906,
-0.1014125719666481,
-0.10984732210636139,
-0.06504913419485092,
0.011... | 0.569943 |
upstream services than requested. ### TLS When processing TLS traffic, Istio has slightly more information available than raw TCP: we can inspect the [SNI](https://en.wikipedia.org/wiki/Server\_Name\_Indication) field presented during the TLS handshake. For standard Services, the same IP:Port matching is used as for ra... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/traffic-routing/index.md | master | istio | [
-0.10015465319156647,
0.057657044380903244,
-0.01200307346880436,
-0.03824496641755104,
-0.056230973452329636,
-0.06783910095691681,
0.022460846230387688,
0.03051171451807022,
0.05793026089668274,
0.007659013848751783,
-0.08949711173772812,
-0.05994129553437233,
-0.03902020305395126,
0.031... | 0.40172 |
to traffic matching in Istio. When Istio receives the request, they will see the IP for `concrete.example.com`. If this is a service Istio knows about, it will be routed as described [above](#tcp). If not, it will be handled as [unmatched traffic](#unmatched-traffic) For HTTP and TLS, which match on hostname, things ar... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/traffic-routing/index.md | master | istio | [
-0.06653176248073578,
-0.011559241451323032,
0.00928518082946539,
-0.0030356140341609716,
-0.043138355016708374,
-0.07727643847465515,
0.07678450644016266,
0.025787927210330963,
0.053746297955513,
-0.03959540277719498,
-0.056751493364572525,
-0.12315507978200912,
-0.017940768972039223,
0.0... | 0.523965 |
{{< boilerplate experimental >}} Many users need to manage the types of the certificates used within their environment. For example, some users require the use of Elliptical Curve Cryptography (ECC) while others may need to use a stronger bit length for RSA certificates. Configuring certificates within your environment... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/configuration/traffic-management/manage-mesh-certificates/index.md | master | istio | [
-0.030383039265871048,
0.04219847545027733,
-0.01609603688120842,
0.057179734110832214,
-0.05829586833715439,
-0.05282830074429512,
-0.03100256435573101,
0.10260506719350815,
0.033589158207178116,
-0.02852148376405239,
-0.021136708557605743,
-0.10447684675455093,
-0.004848912823945284,
0.1... | 0.479426 |
Istio components are built with a flexible logging framework which provides a number of features and controls to help operate these components and facilitate diagnostics. You control these logging features by passing command-line options when starting the components. ## Logging scopes Logging messages output by a compo... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/component-logging/index.md | master | istio | [
0.03419949859380722,
-0.03380877524614334,
-0.03832194581627846,
0.08962881565093994,
0.03019767813384533,
-0.09546583890914917,
0.10066010057926178,
0.050337955355644226,
0.0286696944385767,
-0.0036354782059788704,
-0.021934058517217636,
-0.10481879115104675,
-0.0052647641859948635,
0.058... | 0.499845 |
`istioctl analyze` is a diagnostic tool that can detect potential issues with your Istio configuration. It can run against a live cluster or a set of local configuration files. It can also run against a combination of the two, allowing you to catch problems before you apply changes to a cluster. ## Getting started in u... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/istioctl-analyze/index.md | master | istio | [
0.023813582956790924,
0.009516982361674309,
0.021698864176869392,
0.07282710075378418,
0.025807207450270653,
-0.01286162156611681,
-0.004544850904494524,
-0.013055556453764439,
0.004978951998054981,
0.006331321317702532,
-0.058082520961761475,
-0.14213469624519348,
-0.04847316816449165,
0.... | 0.478797 |
the same logic and error messages as when using `istioctl analyze`. Validation messages from the analysis are written to the status subresource of the affected Istio resource. For example. if you have a misconfigured gateway on your "ratings" virtual service, running `kubectl get virtualservice ratings` would give you ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/istioctl-analyze/index.md | master | istio | [
-0.016233058646321297,
0.0546385832130909,
-0.013709488324820995,
0.07126729190349579,
0.019245028495788574,
-0.007231879513710737,
0.004613958299160004,
-0.005220924969762564,
0.04204244166612625,
0.01699196547269821,
-0.04873806983232498,
-0.12443948537111282,
-0.015754228457808495,
0.04... | 0.467876 |
able to automatically flag this problem so that others can discover and avoid the problem in the first place. To do this, [open an issue](https://github.com/istio/istio/issues) describing your scenario. For example: - Look at all the virtual services - For each, look at their list of gateways - If some of the gateways ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/istioctl-analyze/index.md | master | istio | [
0.010083653964102268,
0.00045011279871687293,
-0.018557526171207428,
0.03639092296361923,
0.03378896415233612,
-0.05635158345103264,
-0.0012483022874221206,
-0.022528868168592453,
-0.012432211078703403,
-0.0037859641015529633,
-0.0217268243432045,
-0.11709386110305786,
-0.07126744836568832,
... | 0.537909 |
Istio provides two very valuable commands to help diagnose traffic management configuration problems, the [`proxy-status`](/docs/reference/commands/istioctl/#istioctl-proxy-status) and [`proxy-config`](/docs/reference/commands/istioctl/#istioctl-proxy-config) commands. The `proxy-status` command allows you to get an ov... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/proxy-cmd/index.md | master | istio | [
0.025052696466445923,
-0.0162530317902565,
0.045595526695251465,
0.0205554086714983,
-0.08128905296325684,
-0.04715539887547493,
0.024755306541919708,
-0.001717220526188612,
-0.017367668449878693,
0.07618110626935959,
-0.08286435902118683,
-0.09603706002235413,
-0.07490164786577225,
0.0485... | 0.477824 |
for listeners or routes when required): {{< text bash >}} $ istioctl proxy-config cluster -n istio-system istio-ingressgateway-7d6874b48f-qxhn5 SERVICE FQDN PORT SUBSET DIRECTION TYPE DESTINATION RULE BlackHoleCluster - - - STATIC agent - - - STATIC details.default.svc.cluster.local 9080 - outbound EDS details.default ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/proxy-cmd/index.md | master | istio | [
0.005405139178037643,
-0.014718358404934406,
-0.06993428617715836,
0.02670852094888687,
-0.030214762315154076,
-0.04797445237636566,
0.023883026093244553,
0.0067855617962777615,
-0.003925108816474676,
0.012939752079546452,
-0.045617956668138504,
-0.07279105484485626,
-0.03281724452972412,
... | 0.499146 |
original destination of the request, if it can find a matching one. Otherwise, it sends the request to the `PassthroughCluster` which connects to the destination directly. {{< text bash json >}} $ istioctl proxy-config listeners productpage-v1-6c886ff494-7vxhs --port 15001 -o json [ { "name": "virtualOutbound", "addres... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/proxy-cmd/index.md | master | istio | [
-0.04875229299068451,
0.0015801137778908014,
-0.029942085966467857,
-0.009080827236175537,
-0.029550934210419655,
-0.04030250385403633,
0.08205382525920868,
-0.0793430507183075,
-0.006315993145108223,
-0.026444774121046066,
-0.035144444555044174,
-0.0741872787475586,
-0.01416816283017397,
... | 0.253807 |
"INSTANCE\_IPS": "10.244.0.7", "ISTIO\_PROXY\_SHA": "istio-proxy:f98b7e538920abc408fbc91c22a3b32bc854d9dc", "ISTIO\_VERSION": "1.7.0", "LABELS": { "app": "istio-ingressgateway", "chart": "gateways", "heritage": "Tiller", "istio": "ingressgateway", "pod-template-hash": "68bf7d7f94", "release": "istio", "service.istio.io... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/proxy-cmd/index.md | master | istio | [
0.00378818460740149,
-0.005760879721492529,
-0.02796749956905842,
0.00870627909898758,
-0.015363435260951519,
-0.027920778840780258,
0.0164644755423069,
0.026418395340442657,
0.0113563546910882,
0.02623937651515007,
-0.006747601553797722,
-0.11242807656526566,
-0.06084088981151581,
0.03868... | 0.623312 |
`istioctl experimental check-inject` is a diagnostic tool that helps you verify if specific webhooks will perform Istio sidecar injection in your pods. Use this tool to check if the sidecar injection configuration is correctly applied to a live cluster. ## Quick Start To check why Istio sidecar injection did/didn't (or... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/check-inject/index.md | master | istio | [
0.03196031227707863,
0.03298608958721161,
-0.0038008103147149086,
0.034634627401828766,
0.0033440119586884975,
-0.051666855812072754,
0.027100693434476852,
-0.0017334676813334227,
-0.0527367927134037,
0.029843328520655632,
0.053250815719366074,
-0.13717907667160034,
-0.008705256506800652,
... | 0.472229 |
{{< boilerplate experimental-feature-warning >}} In Istio 1.3, we included the [`istioctl experimental describe`](/docs/reference/commands/istioctl/#istioctl-experimental-describe-pod) command. This CLI command provides you with the information needed to understand the configuration impacting a {{< gloss >}}pod{{< /glo... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/istioctl-describe/index.md | master | istio | [
-0.05017368867993355,
0.019540658220648766,
0.06934074312448502,
0.04101954773068428,
0.011251600459218025,
-0.04830973967909813,
0.07676279544830322,
-0.005509616807103157,
0.0030417407397180796,
0.02321133390069008,
0.003946981392800808,
-0.1532025784254074,
-0.001964936265721917,
0.0074... | 0.388572 |
The command now shows additional output: - The `ratings` destination rule applies to request to the `ratings` service. - The subset of the `ratings` destination rule that matches the pod, `v1` in this example. - The other subsets defined by the destination rule. - The pod accepts either HTTP or mutual TLS requests but ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/istioctl-describe/index.md | master | istio | [
-0.006338242907077074,
0.04139610752463341,
-0.018100623041391373,
-0.007907385937869549,
-0.018685350194573402,
-0.034529898315668106,
0.008060067892074585,
-0.050230130553245544,
0.06590859591960907,
0.04071125015616417,
-0.04775610193610191,
-0.08002135902643204,
0.008310729637742043,
0... | 0.182619 |
v1` pod: {{< text bash >}} $ istioctl x describe pod $REVIEWS\_V1\_POD ... VirtualService: reviews Weight 90% {{< /text >}} The output shows that the `reviews` virtual service has a weight of 90% for the `v1` subset. This function is also helpful for other types of routing. For example, you can deploy header-specific r... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/istioctl-describe/index.md | master | istio | [
0.05523477867245674,
0.0356779508292675,
0.007888205349445343,
-0.012455333024263382,
0.0035551695618778467,
-0.011848441325128078,
0.04973902925848961,
-0.01913219690322876,
0.07079388201236725,
0.03222256898880005,
-0.02703804150223732,
-0.11637983471155167,
0.0031188686843961477,
-0.030... | 0.218466 |
Istiod is built with a flexible introspection framework, called ControlZ, which makes it easy to inspect and manipulate the internal state of an istiod instance. Istiod opens a port which can be used from a web browser to get an interactive view into its state, or via REST for access and control from external tools. Wh... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/controlz/index.md | master | istio | [
-0.05305817350745201,
0.032406099140644073,
-0.07548252493143082,
0.021276431158185005,
0.004900864325463772,
-0.017187021672725677,
0.036447297781705856,
0.09232521057128906,
-0.012388710863888264,
0.03480752930045128,
-0.012608323246240616,
-0.07146790623664856,
-0.015254471451044083,
0.... | 0.57549 |
This page describes how to troubleshoot issues with the Istio CNI plugin. Before reading this, you should read the [CNI installation and operation guide](/docs/setup/additional-setup/cni/). ## Log The Istio CNI plugin log provides information about how the plugin configures application pod traffic redirection based on ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/cni/index.md | master | istio | [
0.010203464888036251,
-0.04123564809560776,
0.030561182647943497,
-0.005689597688615322,
-0.016057012602686882,
-0.06413242965936661,
-0.03041975013911724,
0.0436849482357502,
-0.029087726026773453,
0.0393746979534626,
-0.039247870445251465,
-0.15517805516719818,
-0.061661362648010254,
0.0... | 0.452881 |
on why the plugin could not be properly installed. | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/cni/index.md | master | istio | [
-0.04378693550825119,
-0.0711563304066658,
-0.04531509056687355,
-0.05300535634160042,
0.021040357649326324,
-0.018124200403690338,
-0.060915619134902954,
0.013315665535628796,
-0.0427790991961956,
0.02765464037656784,
0.10623964667320251,
0.01917528174817562,
-0.08508943766355515,
0.09744... | 0.031979 |
You can gain insights into what individual components are doing by inspecting their [logs](/docs/ops/diagnostic-tools/component-logging/) or peering inside via [introspection](/docs/ops/diagnostic-tools/controlz/). If that's insufficient, the steps below explain how to get under the hood. The [`istioctl`](/docs/referen... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/istioctl/index.md | master | istio | [
-0.0190848708152771,
-0.01762276701629162,
0.007480012718588114,
0.05702000483870506,
0.018156347796320915,
-0.032690536230802536,
0.068478524684906,
0.05330292880535126,
-0.026913080364465714,
0.038797203451395035,
-0.02185644768178463,
-0.08241882175207138,
-0.05547064542770386,
0.074292... | 0.530826 |
with the following command: {{< text bash >}} $ brew install zsh-completions {{< /text >}} Once the `zsh-completions package` has been installed on your macOS system, add the following to your `~/.zshrc` file: {{< text plain >}} if type brew &>/dev/null; then FPATH=$(brew --prefix)/share/zsh-completions:$FPATH autoload... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/istioctl/index.md | master | istio | [
-0.0038032589945942163,
0.01908942684531212,
-0.013425822369754314,
-0.06286921352148056,
0.07353191077709198,
-0.017406174913048744,
0.015398959629237652,
0.013916263356804848,
-0.018573276698589325,
0.0031727859750390053,
0.013493020087480545,
-0.053156301379203796,
-0.007851235568523407,
... | -0.02102 |
This page describes how to troubleshoot issues with Istio deployed to multiple clusters and/or networks. Before reading this, you should take the steps in [Multicluster Installation](/docs/setup/install/multicluster/) and read the [Deployment Models](/docs/ops/deployment/deployment-models/) guide. ## Cross-Cluster Load... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/multicluster/index.md | master | istio | [
0.011176791042089462,
-0.044656142592430115,
0.03537365049123764,
-0.023841004818677902,
-0.05462941154837608,
-0.054130300879478455,
-0.06041533499956131,
0.001712657161988318,
0.03695455566048622,
0.006601438391953707,
-0.04356316104531288,
-0.1794036626815796,
-0.03005400486290455,
-0.0... | 0.349249 |
issues. If it does not, the cause of the problem may lie outside your Istio configuration. ### Locality Load Balancing [Locality load balancing](/docs/tasks/traffic-management/locality-load-balancing/failover/#configure-locality-failover) can be used to make clients prefer that traffic go to the nearest destination. If... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/multicluster/index.md | master | istio | [
0.00899745523929596,
-0.03622860088944435,
0.027171161025762558,
0.04015142098069191,
-0.0405106246471405,
-0.07851283252239227,
0.0009038615971803665,
0.06796152144670486,
-0.013476048596203327,
-0.007597542833536863,
-0.0626736581325531,
-0.13123585283756256,
-0.020442014560103416,
0.075... | 0.484857 |
remote `kubeconfig`. \* If the secret looks correct, check the logs of `istiod` for connectivity or permissions issues reaching the remote Kubernetes API server. Log messages may include `Failed to add remote cluster from secret` along with an error reason. \* If the secret is present and the endpoint is a Pod in the \... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/multicluster/index.md | master | istio | [
0.01267863716930151,
-0.011027765460312366,
0.03615657240152359,
0.02558736503124237,
-0.055786263197660446,
0.037525713443756104,
-0.02977995201945305,
-0.009707029908895493,
0.05957012251019478,
0.10571321845054626,
-0.03451269119977951,
-0.1178855448961258,
-0.03384532779455185,
0.05252... | 0.335457 |
This page describes how to troubleshoot issues with Istio deployed to Virtual Machines. Before reading this, you should take the steps in [Virtual Machine Installation](/docs/setup/install/virtual-machine/). Additionally, [Virtual Machine Architecture](/docs/ops/deployment/vm-architecture/) can help you understand how ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/virtual-machines/index.md | master | istio | [
0.045775990933179855,
0.016316721215844154,
0.01913968287408352,
0.017461948096752167,
-0.015469277277588844,
-0.0648324266076088,
-0.021104846149683,
0.053476687520742416,
-0.08313526958227158,
0.028477849438786507,
0.025302574038505554,
-0.09929980337619781,
-0.09352869540452957,
-0.0047... | 0.508302 |
2021-01-28T18:07:21Z ROOTCA CA ACTIVE true 81663936513052336343895977765039160718 2031-01-26T17:54:44Z 2021-01-28T17:54:44Z {{< /text >}} Additionally, these are persisted to disk to ensure downtime or restarts do not lose state. {{< text bash >}} $ ls /etc/certs cert-chain.pem key.pem root-cert.pem {{< /text >}} | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/diagnostic-tools/virtual-machines/index.md | master | istio | [
-0.018159372732043266,
0.07925085723400116,
-0.02945510856807232,
0.026166649535298347,
0.06433633714914322,
-0.022932972759008408,
-0.06034058332443237,
0.02397697977721691,
0.057573240250349045,
0.009975571185350418,
0.06154192239046097,
0.03179938346147537,
0.07688452303409576,
0.023128... | 0.006001 |
[Kiali](https://kiali.io/) is an observability console for Istio with service mesh configuration and validation capabilities. It helps you understand the structure and health of your service mesh by monitoring traffic flow to infer the topology and report errors. Kiali provides detailed metrics and a basic [Grafana](/d... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/kiali/index.md | master | istio | [
-0.0034232742618769407,
-0.010591474361717701,
0.0034348717890679836,
0.00765129504725337,
0.0020529618486762047,
-0.051004525274038315,
-0.004259465262293816,
0.03806290775537491,
-0.006821202579885721,
-0.0049166129902005196,
-0.02601003460586071,
-0.1318599432706833,
0.02204333245754242,
... | 0.543403 |
Istiod exposes debug endpoints (e.g., `/debug/syncz`, `/debug/registryz`, `/debug/config\_dump`) on multiple ports that provide monitoring and status information useful for integrations. ## Ports and protocols - \*\*Port 15010\*\*: XDS debug endpoints via plaintext gRPC (`syncz`, `config\_dump`) - \*\*Port 15012\*\*: X... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/integration-guide/debug-endpoints/index.md | master | istio | [
-0.029376065358519554,
0.013241994194686413,
-0.019289037212729454,
-0.03206603601574898,
-0.021355319768190384,
-0.08329495042562485,
-0.003521991427987814,
0.023981880396604538,
0.015903275460004807,
0.026813343167304993,
0.004006606992334127,
-0.16691365838050842,
-0.03500821441411972,
... | 0.414621 |
[Jaeger](https://www.jaegertracing.io/) is an open source end to end distributed tracing system, allowing users to monitor and troubleshoot transactions in complex distributed systems. ## Installation ### Option 1: Quick start Istio provides a basic sample installation to quickly get Jaeger up and running: {{< text bas... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/jaeger/index.md | master | istio | [
0.0034375987015664577,
-0.022648708894848824,
0.0022099358029663563,
-0.013815979473292828,
-0.01830120198428631,
-0.018579382449388504,
-0.0030423211865127087,
0.05285053700208664,
-0.0025375396944582462,
0.02471814677119255,
0.007526748348027468,
-0.11493240296840668,
-0.004532734863460064... | 0.436536 |
[Grafana](https://grafana.com/) is an open source monitoring solution that can be used to configure dashboards for Istio. You can use Grafana to monitor the health of Istio and of applications within the service mesh. ## Configuration While you can build your own dashboards, Istio offers a set of preconfigured dashboar... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/grafana/index.md | master | istio | [
-0.06744829565286636,
-0.005838957615196705,
-0.10059723258018494,
0.0017527559539303184,
0.009331168606877327,
-0.06378194689750671,
0.02633288875222206,
0.07435186207294464,
0.030214950442314148,
0.056782063096761703,
-0.05391712859272957,
-0.0677046924829483,
-0.033162180334329605,
0.05... | 0.484695 |
[SPIRE](https://spiffe.io/docs/latest/spire-about/spire-concepts/) is a production-ready implementation of the SPIFFE specification that performs node and workload attestation in order to securely issue cryptographic identities to workloads running in heterogeneous environments. SPIRE can be configured as a source of c... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/spire/index.md | master | istio | [
-0.10005246102809906,
-0.0036477160174399614,
-0.03401774540543556,
0.0491490513086319,
-0.013647740706801414,
-0.0433877632021904,
0.029468638822436333,
0.00014784441736992449,
0.017016658559441566,
0.010528765618801117,
-0.05432427302002907,
-0.06822709739208221,
-0.002948981476947665,
0... | 0.447171 |
they can request identities. #### Istio Gateway `ClusterSPIFFEID` The following will create a `ClusterSPIFFEID`, which will auto-register any Istio Ingress gateway pod with SPIRE if it is scheduled into the `istio-system` namespace, and has a service account named `istio-ingressgateway-service-account`. These selectors... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/spire/index.md | master | istio | [
-0.058188751339912415,
-0.02758978307247162,
-0.06405404955148697,
0.06150399148464203,
-0.015604124404489994,
0.04653623327612877,
0.08186576515436172,
0.007639849092811346,
0.006109678186476231,
0.0035906340926885605,
-0.02281828597187996,
-0.11257890611886978,
0.008195973001420498,
-0.0... | 0.331361 |
EOF {{< /text >}} {{< warning >}} The sidecar template above patches `initContainers` because [native sidecars](/blog/2023/native-sidecars/) (the default on Kubernetes 1.33+) inject `istio-proxy` as an initContainer. If you have explicitly disabled native sidecar support in the Istio control plane, change `initContaine... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/spire/index.md | master | istio | [
0.02676263079047203,
0.06765962392091751,
0.051805004477500916,
0.035967785865068436,
-0.009529275819659233,
0.025931859388947487,
0.03448821231722832,
0.0432586595416069,
-0.03693429008126259,
0.02385936677455902,
-0.019539648666977882,
-0.07684816420078278,
-0.059586286544799805,
-0.0000... | 0.336534 |
uses it for all TLS and mTLS communications. ### Check that the workload identity was issued by SPIRE 1. Get pod information: {{< text syntax=bash snip\_id=set\_curl\_pod\_var >}} $ CURL\_POD=$(kubectl get pod -l app=curl -o jsonpath="{.items[0].metadata.name}") {{< /text >}} 1. Retrieve curl's SVID identity document u... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/spire/index.md | master | istio | [
-0.09701922535896301,
0.11512195318937302,
-0.007094063796103001,
0.026999853551387787,
-0.027534298598766327,
-0.058346938341856,
0.011666078120470047,
-0.02137700468301773,
0.12275799363851547,
0.023992521688342094,
-0.05310996249318123,
-0.0342252142727375,
-0.0020390867721289396,
-0.00... | 0.221719 |
[Zipkin](https://zipkin.io/) is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in service architectures. Features include both the collection and lookup of this data. ## Installation ### Option 1: Quick start Istio provides a basic sample installation to quickly get Zi... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/zipkin/index.md | master | istio | [
-0.011288820765912533,
0.010036165826022625,
-0.012183288112282753,
0.04289300739765167,
-0.016310304403305054,
-0.062381722033023834,
-0.018838783726096153,
0.01524931751191616,
0.021719835698604584,
0.015940777957439423,
-0.03382008895277977,
-0.07469744980335236,
0.0061212508007884026,
... | 0.427859 |
[cert-manager](https://cert-manager.io/) is a tool that automates certificate management. This can be integrated with Istio gateways to manage TLS certificates. ## Configuration Consult the [cert-manager installation documentation](https://cert-manager.io/docs/installation/kubernetes/) to get started. No special change... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/certmanager/index.md | master | istio | [
-0.0204665157943964,
0.02931090258061886,
0.0160951167345047,
0.05518920719623566,
-0.041940607130527496,
-0.024217354133725166,
-0.00158083310816437,
0.022875694558024406,
0.06841274350881577,
-0.0048140487633645535,
-0.04115089029073715,
-0.146057590842247,
0.027731850743293762,
0.063669... | 0.361236 |
Istio provides both an ingress and service mesh implementation, which can be used together or separately. While these are designed to work together seamlessly, there are times when integrating with a third party ingress is required. This could be for migration purposes, feature requirements, or personal preferences. ##... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/loadbalancers/index.md | master | istio | [
-0.0845060795545578,
0.003962676040828228,
0.030187426134943962,
0.015824057161808014,
-0.009332187473773956,
-0.04344412311911583,
0.01075062993913889,
0.08137884736061096,
0.01684647798538208,
0.006000184454023838,
0.04819938912987709,
-0.10505762696266174,
0.016552340239286423,
0.030422... | 0.520168 |
[Prometheus](https://prometheus.io/) is an open source monitoring system and time series database. You can use Prometheus with Istio to record metrics that track the health of Istio and of applications within the service mesh. You can visualize metrics using tools like [Grafana](/docs/ops/integrations/grafana/) and [Ki... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/prometheus/index.md | master | istio | [
-0.024411095306277275,
0.005563891492784023,
-0.0140763558447361,
0.02593706175684929,
-0.0029781449120491743,
-0.07294222712516785,
-0.009531280025839806,
0.014491820707917213,
0.04219532757997513,
0.012404095381498337,
-0.02455536276102066,
-0.09406951814889908,
-0.03965982794761658,
0.0... | 0.402325 |
job can be added to scrape its `http-monitoring` port: {{< text yaml >}} - job\_name: 'istiod' kubernetes\_sd\_configs: - role: endpoints namespaces: names: - istio-system relabel\_configs: - source\_labels: [\_\_meta\_kubernetes\_service\_name, \_\_meta\_kubernetes\_endpoint\_port\_name] action: keep regex: istiod;htt... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/prometheus/index.md | master | istio | [
-0.019739899784326553,
0.03254462778568268,
-0.010256866924464703,
0.04039827361702919,
0.013682280667126179,
-0.05904774367809296,
0.009986412711441517,
-0.05398815870285034,
-0.003563032718375325,
0.023260872811079025,
0.002560422057285905,
-0.07537443935871124,
-0.06750805675983429,
0.0... | 0.2398 |
[Apache SkyWalking](http://skywalking.apache.org) is an application performance monitoring (APM) system, especially designed for microservices, cloud native and container-based architectures. SkyWalking is a one-stop solution for observability that not only provides distributed tracing ability like Jaeger and Zipkin, m... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/integrations/skywalking/index.md | master | istio | [
0.01873495802283287,
-0.03882923722267151,
-0.008807714097201824,
0.03299391642212868,
0.019756415858864784,
-0.06731458008289337,
0.005261311307549477,
-0.01410133671015501,
-0.01418410986661911,
0.039804842323064804,
-0.037797778844833374,
-0.08922357857227325,
-0.04336896911263466,
-0.0... | 0.403728 |
Before reading this document, be sure to review [Istio's architecture](/docs/ops/deployment/architecture/) and [deployment models](/docs/ops/deployment/deployment-models/). This page builds on those documents to explain how Istio can be extended to support joining virtual machines into the mesh. Istio's virtual machine... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/vm-architecture/index.md | master | istio | [
-0.02263399213552475,
0.045071594417095184,
0.03603239730000496,
-0.006269198376685381,
-0.0338565893471241,
-0.034631796181201935,
0.009508508257567883,
0.027594197541475296,
0.02838166430592537,
0.010115822777152061,
-0.05936021730303764,
-0.07703905552625656,
-0.037224479019641876,
0.00... | 0.621323 |
of a workload, similar to a pod in Kubernetes. When the workload is removed from the mesh, the `WorkloadEntry` resource will be automatically removed. Additionally, if any probes are configured in the `WorkloadGroup` resource, the Istio control plane automatically updates the health status of associated `WorkloadEntry`... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/vm-architecture/index.md | master | istio | [
0.00035995812504552305,
0.0044501894153654575,
0.0038721030578017235,
0.06936755031347275,
-0.005148431286215782,
-0.03697579354047775,
0.0573582798242569,
-0.019347380846738815,
0.08038769662380219,
0.010029918514192104,
-0.03454379737377167,
-0.009373690001666546,
-0.07969594746828079,
0... | 0.529853 |
## Kernel Module Requirements on Cluster Nodes Regardless of the Istio {{< gloss >}}data plane{{< /gloss >}} mode, in Kubernetes contexts Istio generally requires Kubernetes nodes running Linux kernels with support for traffic interception and routing. Istio supports two backends for traffic management: `iptables` (def... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/platform-requirements/index.md | master | istio | [
0.032268133014440536,
-0.023680072277784348,
-0.01774885132908821,
0.010618641041219234,
-0.007250680588185787,
-0.004181257449090481,
0.028188403695821762,
0.06652389466762543,
-0.034094661474227905,
0.019518353044986725,
-0.04794754460453987,
-0.10713246464729309,
-0.08455657958984375,
-... | 0.566567 |
configuration, see the relevant data plane mode documentation. | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/platform-requirements/index.md | master | istio | [
0.06302069127559662,
-0.06526380777359009,
-0.03401420637965202,
-0.022956358268857002,
-0.07985392212867737,
-0.0008358394261449575,
-0.0233119186013937,
0.026081539690494537,
-0.1024719774723053,
0.03459277004003525,
0.05592551454901695,
0.06579437851905823,
-0.031189484521746635,
-0.045... | -0.015435 |
Multicluster deployments with ambient mode enable you to offer truly globally resilient applications at scale with minimal overhead. In addition to its normal functions, the Istio control plane creates watches on all remote clusters to keep an up-to-date listing of what global services each cluster offers. The Istio da... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/ambient-mc-perf/index.md | master | istio | [
0.0017731210682541132,
-0.039154279977083206,
0.028331326320767403,
0.06864060461521149,
0.030345626175403595,
-0.11622056365013123,
-0.013344778679311275,
0.06034691631793976,
0.020368726924061775,
0.0632774606347084,
-0.05053546652197838,
-0.08596326410770416,
0.01919730193912983,
0.0100... | 0.463108 |
Istio provides a great deal of functionality to applications with little or no impact on the application code itself. Many Kubernetes applications can be deployed in an Istio-enabled cluster without any changes at all. However, there are some implications of Istio's sidecar model that may need special consideration whe... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/application-requirements/index.md | master | istio | [
0.015673715621232986,
-0.0012574128340929747,
0.032948847860097885,
-0.0035456805489957333,
-0.04365001991391182,
0.002456158399581909,
0.005125090014189482,
0.06276081502437592,
-0.042356885969638824,
0.025337575003504753,
0.0027351779863238335,
-0.08253692835569382,
-0.034386228770017624,
... | 0.555733 |
| Yes | | 15004 | HTTP | Debug port | Yes | | 15006 | TCP | Envoy inbound | No | | 15008 | HTTP2 | {{< gloss >}}HBONE{{}} mTLS tunnel port | No | | 15020 | HTTP | Merged Prometheus telemetry from Istio agent, Envoy, and application | No | | 15021 | HTTP | Health checks | No | | 15053 | DNS | DNS port, if capture is ena... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/application-requirements/index.md | master | istio | [
-0.06133263558149338,
0.023972896859049797,
-0.04244661331176758,
-0.039069030433893204,
-0.0371176116168499,
-0.09554587304592133,
-0.015241038985550404,
0.014588668942451477,
-0.014088088646531105,
0.027878863736987114,
0.040706753730773926,
-0.06513307988643646,
-0.013949859887361526,
0... | 0.47002 |
Routing](/docs/ops/configuration/traffic-management/traffic-routing) page for more information. | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/application-requirements/index.md | master | istio | [
0.048454221338033676,
-0.05881156772375107,
-0.0746670514345169,
-0.017015371471643448,
-0.07882411777973175,
-0.01573726162314415,
0.001882766606286168,
0.015645762905478477,
-0.08100999146699905,
0.0004991794121451676,
-0.018590886145830154,
0.08855818957090378,
-0.01607421599328518,
-0.... | 0.210785 |
An Istio service mesh is logically split into a \*\*data plane\*\* and a \*\*control plane\*\*. \* The \*\*data plane\*\* is composed of a set of intelligent proxies ([Envoy](https://www.envoyproxy.io/)) deployed as sidecars. These proxies mediate and control all network communication between microservices. They also c... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/architecture/index.md | master | istio | [
-0.04932089522480965,
0.006277922540903091,
-0.007302023936063051,
0.004330435302108526,
-0.04483487457036972,
-0.07569673657417297,
0.05814108997583389,
0.025580069050192833,
0.012834976427257061,
0.06317171454429626,
-0.02566911280155182,
0.0008679087040945888,
-0.041237980127334595,
0.0... | 0.590368 |
Kubernetes has a unique and permissive networking model. In order to configure L2-L4 networking between Pods, [a Kubernetes cluster requires an \_interface\_ Container Network Interface (CNI) plugin](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/). This plugin runs whenever a... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/architecture/cni/index.md | master | istio | [
0.04635874181985855,
-0.027395620942115784,
0.037112243473529816,
0.020310545340180397,
0.002024319488555193,
0.044131290167570114,
-0.037271760404109955,
0.03429586440324783,
0.02426927164196968,
0.04001245275139809,
-0.028720008209347725,
-0.10279685258865356,
-0.03559435158967972,
0.003... | 0.429111 |
Istio makes it easy to create a network of deployed services with rich routing, load balancing, service-to-service authentication, monitoring, and more - all without any changes to the application code. Istio strives to provide these benefits with minimal resource overhead and aims to support very large meshes with hig... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/performance-and-scalability/index.md | master | istio | [
-0.024595940485596657,
0.006875728722661734,
-0.0015345802530646324,
0.05804069712758064,
-0.06123968958854675,
-0.07275906950235367,
0.039168890565633774,
0.04030948132276535,
0.013142818585038185,
0.07102686911821365,
-0.06769750267267227,
-0.031430382281541824,
-0.04196877032518387,
0.0... | 0.591467 |
request does not contribute to the total time taken to complete that request. However, since the worker is busy handling the request, the worker won't start handling the next request immediately. This process adds to the queue wait time of the next request and affects average and tail latencies. The actual tail latency... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/performance-and-scalability/index.md | master | istio | [
-0.05029842630028725,
0.030031681060791016,
0.0515291653573513,
0.09578121453523636,
0.0048779635690152645,
-0.16134494543075562,
0.019960954785346985,
0.0448572039604187,
0.00873459130525589,
-0.04369974881410599,
-0.02764696069061756,
-0.0009513081167824566,
-0.04503944516181946,
-0.0008... | 0.264338 |
When configuring a production deployment of Istio, you need to answer a number of questions. Will the mesh be confined to a single {{< gloss >}}cluster{{< /gloss >}} or distributed across multiple clusters? Will all the services be located in a single fully connected network, or will gateways be required to connect ser... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/deployment-models/index.md | master | istio | [
-0.011535417288541794,
-0.08650387823581696,
-0.014859321527183056,
-0.000008635720405436587,
-0.03270483389496803,
0.004377291072160006,
-0.02658742666244507,
0.006127081345766783,
0.019117332994937897,
0.016942545771598816,
-0.020627541467547417,
-0.05952441692352295,
0.014246545732021332,... | 0.342674 |
a single cluster deployment: - Fault isolation and fail over: `cluster-1` goes down, fail over to `cluster-2`. - Location-aware routing and fail over: Send requests to the nearest service. - Various [control plane models](#control-plane-models): Support different levels of availability. - Team or project isolation: Eac... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/deployment-models/index.md | master | istio | [
0.04027664288878441,
-0.04835290461778641,
0.017358293756842613,
0.0023411691654473543,
0.05515831708908081,
-0.03310108557343483,
-0.09147366136312485,
0.02535017766058445,
0.04417533054947853,
0.025178629904985428,
-0.018116503953933716,
-0.03705858066678047,
0.04599412530660629,
-0.0171... | 0.114043 |
is a Kubernetes Enhancement Proposal (KEP) that defines an API for exporting services to multiple clusters. This effectively pushes the responsibility of service visibility and DNS resolution for the entire `clusterset` onto Kubernetes. There is also work in progress to build layers of `MCS` support into Istio, which w... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/deployment-models/index.md | master | istio | [
-0.053060080856084824,
-0.031137801706790924,
0.054439473897218704,
0.03499389812350273,
-0.002654029754921794,
0.008296065963804722,
-0.003816506825387478,
0.031278278678655624,
0.06148109585046768,
0.015293567441403866,
-0.0717439353466034,
-0.06881173700094223,
-0.01740291342139244,
-0.... | 0.562132 |
case, you can run your mesh with a control plane on a single cluster. {{< image width="50%" link="single-cluster.svg" alt="A single cluster with a control plane" title="Single control plane" caption="A single cluster with a control plane" >}} A cluster like this one, with its own local control plane, is referred to as ... | https://github.com/istio/istio.io/blob/master/content/en/docs/ops/deployment/deployment-models/index.md | master | istio | [
0.012875979766249657,
-0.06897945702075958,
-0.02233082801103592,
0.053622860461473465,
0.025508839637041092,
0.010861869901418686,
-0.03878449648618698,
-0.0252083633095026,
0.09569843113422394,
0.06752543151378632,
-0.004947383422404528,
-0.03335200250148773,
0.018296202644705772,
0.0020... | 0.044702 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.