content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
This task shows you how to set up and use the Istio Dashboard to monitor mesh traffic. As part of this task, you will use the Grafana Istio addon and the web-based interface for viewing service mesh traffic data. The [Bookinfo](/docs/examples/bookinfo/) sample application is used as the example application throughout t... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/using-istio-dashboard/index.md | master | istio | [
-0.037015270441770554,
0.0056810760870575905,
-0.06220019608736038,
0.011657060123980045,
-0.038638997822999954,
-0.06382253021001816,
-0.021550647914409637,
0.0036234622821211815,
0.03419828787446022,
0.06905429065227509,
-0.022702964022755623,
-0.1394561529159546,
-0.04632081091403961,
0... | 0.443776 |
service within the mesh (HTTP/gRPC and TCP). This also provides metrics about client and service workloads for this service. 1. Individual Workloads View: This section provides metrics about requests and responses for each individual workload within the mesh (HTTP/gRPC and TCP). This also provides metrics about inbound... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/using-istio-dashboard/index.md | master | istio | [
-0.0627993643283844,
0.047582801431417465,
-0.049522001296281815,
-0.051324643194675446,
-0.07724674791097641,
-0.1064162626862526,
-0.05928670987486839,
-0.043965063989162445,
0.07676783949136734,
0.05960508808493614,
-0.049958813935518265,
-0.02712293155491352,
-0.05705516040325165,
-0.0... | 0.204291 |
This task shows how to configure Istio to automatically gather telemetry for TCP services in a mesh. At the end of this task, you can query default TCP metrics for your mesh. The [Bookinfo](/docs/examples/bookinfo/) sample application is used as the example throughout this task. ## Before you begin \* [Install Istio](/... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/tcp-metrics/index.md | master | istio | [
-0.027595186606049538,
0.007129285950213671,
-0.046906210482120514,
0.025440648198127747,
-0.09928151220083237,
-0.07235920429229736,
0.004017803817987442,
0.011654019355773926,
0.05335891619324684,
0.04443327710032463,
-0.0433918796479702,
-0.16618765890598297,
-0.010289051569998264,
0.00... | 0.370773 |
server sidecars in the mesh. ALPN negotiation resolves the protocol to `istio-peer-exchange` for connections between Istio enabled proxies, but not between an Istio enabled proxy and any other proxy. This protocol extends TCP as follows: 1. TCP client, as a first sequence of bytes, sends a magic byte string and a lengt... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/tcp-metrics/index.md | master | istio | [
-0.045474376529455185,
0.02803676575422287,
0.05139678344130516,
0.03738398849964142,
-0.08332756906747818,
-0.047874804586172104,
0.03867088258266449,
-0.04709364101290703,
0.047662824392318726,
0.013289877213537693,
-0.06569831073284149,
-0.036505453288555145,
-0.04965347424149513,
0.028... | 0.413004 |
It's useful to visualize telemetry based on the type of requests and responses handled by services in your mesh. For example, a bookseller tracks the number of times book reviews are requested. A book review request has this structure: {{< text plain >}} GET /reviews/{review\_id} {{< /text >}} Counting the number of re... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/classify-metrics/index.md | master | istio | [
-0.06378819793462753,
0.02710622549057007,
-0.0861077532172203,
0.0636332705616951,
0.004324679728597403,
-0.05319038778543472,
0.008829498663544655,
0.015136992558836937,
0.02788604237139225,
0.004313113167881966,
-0.005713994614779949,
-0.08551107347011566,
0.05316285416483879,
0.0432586... | 0.358841 |
value: filter\_state['wasm.istio\_responseClass'] providers: - name: prometheus {{< /text >}} 1. Apply your changes using the following command: {{< text bash >}} $ kubectl -n istio-system apply -f attribute\_gen\_service.yaml {{< /text >}} ## Verify the results 1. Generate metrics by sending traffic to your applicatio... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/classify-metrics/index.md | master | istio | [
-0.0023138518445193768,
0.020562725141644478,
0.015548921190202236,
0.02799670584499836,
-0.05259319022297859,
-0.060573700815439224,
0.015998244285583496,
0.001088291872292757,
0.046600691974163055,
0.016881179064512253,
-0.037610720843076706,
-0.15949121117591858,
-0.051065605133771896,
... | 0.370889 |
This task demonstrates how to \*\*securely scrape Istio sidecar and gateway metrics\*\* using Prometheus over \*\*Istio mTLS\*\*. By default, Prometheus scrapes metrics from Istio workloads and gateways over HTTP. In this task, you configure Istio and Prometheus so that metrics are scraped securely over encrypted conne... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/secure-metrics/index.md | master | istio | [
-0.1109982579946518,
0.02774881385266781,
-0.02278405986726284,
0.029959190636873245,
-0.04365772008895874,
-0.13322176039218903,
0.021931199356913567,
0.028225740417838097,
-0.014426816254854202,
-0.022587157785892487,
-0.03301243111491203,
-0.1032637506723404,
-0.023067697882652283,
0.01... | 0.417268 |
in the default namespace and deploy httpbin {{< text bash >}} $ kubectl label namespace default istio-injection=enabled --overwrite $ kubectl apply -f @samples/httpbin/httpbin.yaml {{< /text >}} 1. Annotate the httpbin pod for secure Prometheus scraping Ensure Prometheus scrapes metrics securely via the mTLS port (`150... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/secure-metrics/index.md | master | istio | [
-0.06319837272167206,
0.061584558337926865,
-0.025294680148363113,
-0.0011614995310083032,
-0.018293915316462517,
-0.08548344671726227,
0.0036498485133051872,
-0.037754133343696594,
0.03546345233917236,
0.024456419050693512,
-0.004427571780979633,
-0.12103340029716492,
-0.007763909641653299,... | 0.296766 |
This task shows you how to visualize different aspects of your Istio mesh. As part of this task, you install the [Kiali](https://www.kiali.io) addon and use the web-based graphical user interface to view service graphs of the mesh and your Istio configuration objects. {{< idea >}} This task does not cover all of the fe... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/kiali/index.md | master | istio | [
0.015528314746916294,
-0.004206209443509579,
-0.03043561801314354,
0.006354005075991154,
-0.032607000321149826,
-0.032053329050540924,
-0.007897896692156792,
0.04103394225239754,
0.01575210504233837,
-0.0016379246953874826,
-0.014372165314853191,
-0.1355391889810562,
0.029953662306070328,
... | 0.535599 |
workload in your service mesh. This graph type does not require you to use the `app` and `version` labels so if you opt to not use those labels on your components, this may be your graph type of choice. {{< image width="70%" link="./kiali-workload.png" caption="Example Workload Graph" >}} \* The \*\*Service\*\* graph t... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/kiali/index.md | master | istio | [
-0.008252604864537716,
0.011260527186095715,
-0.005443141330033541,
0.024605751037597656,
-0.022502413019537926,
-0.0357523076236248,
0.019009780138731003,
0.05001291632652283,
-0.012443984858691692,
0.056603625416755676,
-0.04702843725681305,
-0.1039598286151886,
0.004790213890373707,
0.1... | 0.479347 |
validations page](https://kiali.io/docs/features/validations/) for the list of all validation checks Kiali performs. {{< idea >}} Istio provides `istioctl analyze` which provides analysis in a way that can be used in a CI pipeline. The two approaches can be complementary. {{< /idea >}} Force an invalid configuration of... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/kiali/index.md | master | istio | [
-0.03505709394812584,
0.043185845017433167,
0.028769973665475845,
-0.03421168774366379,
-0.04119262099266052,
-0.05860510095953941,
-0.003501993604004383,
-0.015179365873336792,
0.046385228633880615,
-0.016447853296995163,
-0.02252572774887085,
-0.1284010261297226,
0.016545094549655914,
0.... | 0.328887 |
application and Kiali from your cluster. 1. To remove the Bookinfo application, refer to the [Bookinfo cleanup](/docs/examples/bookinfo/#cleanup) instructions. 1. To remove Kiali from a Kubernetes environment: {{< text bash >}} $ kubectl delete -f {{< github\_file >}}/samples/addons/kiali.yaml {{< /text >}} | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/kiali/index.md | master | istio | [
0.0338100865483284,
0.008850779384374619,
-0.008207704871892929,
-0.037729158997535706,
0.02532198280096054,
0.01776128262281418,
-0.04083476588129997,
-0.08164864778518677,
0.08370558172464371,
-0.007708846591413021,
0.043857164680957794,
-0.01306278444826603,
0.012170332483947277,
-0.041... | 0.18069 |
The simplest kind of Istio logging is [Envoy's access logging](https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/access\_log/usage). Envoy proxies print access information to their standard output. The standard output of Envoy's containers can then be printed by the `kubectl logs` command. {{< boi... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/logs/access-log/index.md | master | istio | [
0.04212028160691261,
0.053989287465810776,
-0.004696857184171677,
0.04021019861102104,
-0.012928875163197517,
-0.06952930241823196,
0.03484737500548363,
0.0027646650560200214,
0.037212640047073364,
0.06105368211865425,
-0.050205688923597336,
-0.08584900945425034,
-0.048431396484375,
0.0381... | 0.410596 |
/status/418 HTTP/1.1" 418 - via\_upstream - "-" 0 135 4 4 "-" "curl/7.73.0-DEV" "84961386-6d84-929d-98bd-c5aee93b5c88" "httpbin:8000" "10.44.1.27:80" outbound|8000||httpbin.foo.svc.cluster.local 10.44.1.23:37652 10.0.45.184:8000 10.44.1.23:46520 - default {{< /text >}} 1. Check `httpbin`'s log: {{< text bash >}} $ kube... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/logs/access-log/index.md | master | istio | [
-0.013548469170928001,
0.03535202518105507,
-0.02266726642847061,
-0.023897793143987656,
-0.027397558093070984,
-0.07710689306259155,
-0.027805062010884285,
-0.028756944462656975,
0.07613585889339447,
0.03657090663909912,
-0.027845436707139015,
-0.08447672426700592,
-0.06856878101825714,
-... | 0.230031 |
Telemetry API has been in Istio as a first-class API for quite sometime now. Previously users had to configure telemetry in the `MeshConfig` section of Istio configuration. {{< boilerplate before-you-begin-egress >}} {{< boilerplate start-httpbin-service >}} ## Installation In this example, we will send logs to [Grafan... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/logs/telemetry-api/index.md | master | istio | [
-0.06133927404880524,
0.025896985083818436,
-0.03801281377673149,
-0.016321470960974693,
-0.03665483370423317,
-0.10962414741516113,
0.019836854189634323,
0.062086813151836395,
0.04309374466538429,
0.0707627683877945,
0.0015208646655082703,
-0.12280751019716263,
-0.06595034897327423,
0.034... | 0.480731 |
The Envoy proxies can be configured to export their [access logs](https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/access\_log/usage) in [OpenTelemetry format](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/access\_loggers/open\_telemetry/v3/logs\_service.proto). In this example, t... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/logs/otel-provider/index.md | master | istio | [
0.023901421576738358,
0.04973437264561653,
-0.03120546042919159,
0.04769717901945114,
-0.014954880811274052,
-0.0846327543258667,
-0.02508612349629402,
-0.04451453313231468,
0.06196514889597893,
0.062208566814661026,
-0.060194533318281174,
-0.016471317037940025,
-0.013503589667379856,
-0.0... | 0.136899 |
text bash >}} $ kubectl exec "$SOURCE\_POD" -c curl -- curl -sS -v httpbin:8000/status/418 ... < HTTP/1.1 418 Unknown ... < server: envoy ... I'm a teapot! ... {{< /text >}} 1. Check `otel-collector`'s log: {{< text bash >}} $ kubectl logs -l app=opentelemetry-collector -n observability [2020-11-25T21:26:18.409Z] "GET ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/logs/otel-provider/index.md | master | istio | [
0.01778588257730007,
0.07908426225185394,
-0.009056574665009975,
-0.02712538093328476,
-0.004464855883270502,
-0.09628020226955414,
0.009652341715991497,
-0.07536288350820541,
0.1330524981021881,
0.03088640794157982,
0.005793696269392967,
-0.1361304223537445,
-0.01061995979398489,
-0.05207... | 0.171208 |
This task shows how to configure Istio to expose and access the telemetry addons outside of a cluster. ## Configuring remote access Remote access to the telemetry addons can be configured in a number of different ways. This task covers two basic access methods: secure (via HTTPS) and insecure (via HTTP). The secure met... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/gateways/index.md | master | istio | [
-0.06075754389166832,
0.0018178736791014671,
-0.07830612361431122,
-0.0013593994081020355,
-0.05989479646086693,
-0.06985554099082947,
0.016205180436372757,
0.05627253279089928,
-0.030261605978012085,
0.04977495223283768,
0.014382799156010151,
-0.12750191986560822,
-0.045477915555238724,
0... | 0.524854 |
>}} $ cat <}} 1. Apply the following configuration to expose the tracing service: {{< text bash >}} $ cat <}} 1. Visit the telemetry addons via your browser. \* Kiali: `http://kiali.${INGRESS\_DOMAIN}` \* Prometheus: `http://prometheus.${INGRESS\_DOMAIN}` \* Grafana: `http://grafana.${INGRESS\_DOMAIN}` \* Tracing: `htt... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/gateways/index.md | master | istio | [
-0.021102042868733406,
0.022126073017716408,
-0.04352184012532234,
-0.023938946425914764,
-0.038423631340265274,
-0.10873202979564667,
0.015962351113557816,
-0.04456789419054985,
0.05472835525870323,
0.041322238743305206,
0.014750123955309391,
-0.10154503583908081,
-0.031275734305381775,
0... | 0.404102 |
Istio provides a [Telemetry API](/docs/reference/config/telemetry/) that enables flexible configuration of [metrics](/docs/tasks/observability/metrics/), [access logs](/docs/tasks/observability/logs/), and [tracing](/docs/tasks/observability/distributed-tracing/). ## Using the API ### Scope, Inheritance, and Overrides ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/telemetry/index.md | master | istio | [
-0.059996962547302246,
-0.027657117694616318,
-0.03386274352669716,
0.02583879791200161,
-0.027840426191687584,
-0.1371292620897293,
0.03956730663776398,
0.03931458666920662,
-0.0018423983128741384,
0.01612907275557518,
-0.023998398333787918,
-0.10589410364627838,
-0.024711305275559425,
0.... | 0.486581 |
to be added to all trace spans with a name of `foo` and a value of `bar`. ### Configuring namespace-scoped tracing behavior To tailor the behavior for individual namespaces, add a `Telemetry` resource to the desired namespace. Any fields specified in the namespace resource will completely override the inherited field c... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/telemetry/index.md | master | istio | [
-0.044761285185813904,
0.02046482264995575,
0.01143031194806099,
0.049540575593709946,
-0.0004694092203862965,
-0.11357183009386063,
0.07968192547559738,
0.0071070254780352116,
0.014645062386989594,
0.0267831701785326,
0.00900648906826973,
-0.11700362712144852,
-0.0020964788272976875,
0.03... | 0.19996 |
Istio provides the ability to configure tracing options, such as sampling rate and adding custom tags to reported spans. This task shows you how to customize the tracing options with Telemetry API. ## Before you begin 1. Ensure that your applications propagate tracing headers as described [here](/docs/tasks/observabili... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/telemetry-api/index.md | master | istio | [
-0.04740554839372635,
0.010103071108460426,
-0.06975935399532318,
0.06410214304924011,
0.021805837750434875,
-0.12304025143384933,
0.025229861959815025,
0.07355070114135742,
-0.052600521594285965,
0.024966081604361534,
-0.015781797468662262,
-0.11022631078958511,
-0.030416354537010193,
0.0... | 0.465442 |
"zipkin" zipkin: service: zipkin.istio-system.svc.cluster.local port: 9411 maxTagLength: {{< /text >}} | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/telemetry-api/index.md | master | istio | [
0.0037552432622760534,
0.07805434614419937,
-0.09718313813209534,
0.02388329617679119,
0.0056889792904257774,
-0.018188823014497757,
-0.04990539327263832,
0.071139395236969,
0.0038002796936780214,
-0.0033603496849536896,
-0.027671370655298233,
0.03540702909231186,
-0.03552311658859253,
0.0... | 0.292572 |
[OpenTelemetry](https://opentelemetry.io/) (OTel) is a vendor-neutral, open source observability framework for instrumenting, generating, collecting, and exporting telemetry data. [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otlp/) (OTLP) traces can be sent to [Jaeger](/docs/tasks/observability/distribu... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/opentelemetry/index.md | master | istio | [
-0.03964276239275932,
-0.0032799006439745426,
-0.04183444380760193,
-0.006203777156770229,
-0.02289348840713501,
-0.10450085252523422,
0.05114373937249184,
0.04720994830131531,
-0.014457150362432003,
0.012699209153652191,
0.01952093094587326,
-0.14081312716007233,
-0.02718520350754261,
-0.... | 0.406807 |
>}} $ killall istioctl {{< /text >}} 1. Uninstall the OpenTelemetry Collector: {{< text syntax=bash snip\_id=cleanup\_collector >}} $ kubectl delete -f @samples/open-telemetry/otel.yaml@ -n observability $ kubectl delete namespace observability {{< /text >}} 1. If you are not planning to explore any follow-on tasks, re... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/opentelemetry/index.md | master | istio | [
0.03656677156686783,
0.055795345455408096,
0.009126851335167885,
-0.03491527959704399,
-0.03339878469705582,
-0.07744115591049194,
0.00503587955608964,
-0.06532961875200272,
0.11149407178163528,
0.03989134728908539,
0.010366217233240604,
-0.030979324132204056,
-0.049778714776039124,
-0.063... | 0.224544 |
After completing this task, you understand how to have your application participate in tracing with [Jaeger](https://www.jaegertracing.io/), regardless of the language, framework, or platform you use to build your application. This task uses the [Bookinfo](/docs/examples/bookinfo/) sample as the example application. To... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/jaeger/index.md | master | istio | [
-0.01787756010890007,
-0.049031369388103485,
-0.02761601097881794,
-0.01024163980036974,
-0.02439890056848526,
-0.004047449212521315,
0.012733430601656437,
0.05102108046412468,
-0.03158121183514595,
0.03215434029698372,
-0.00029603313305415213,
-0.14219896495342255,
0.023495370522141457,
0... | 0.363471 |
Istio provides multiple ways to configure trace sampling. In this page you will learn and understand all the different ways sampling can be configured. ## Before you begin 1. Ensure that your applications propagate tracing headers as described [here](/docs/tasks/observability/distributed-tracing/overview/). ## Availabl... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/sampling/index.md | master | istio | [
-0.0022801165468990803,
-0.017653558403253555,
-0.0505661778151989,
0.02581714652478695,
0.030266307294368744,
-0.1358274519443512,
0.08978381752967834,
0.04741507023572922,
0.020851032808423042,
0.035936035215854645,
-0.06158335506916046,
-0.13364313542842865,
-0.048320699483156204,
0.002... | 0.384315 |
is configured, it overrides all the others' methods. Additionally, the random percentage value is set to `100` and cannot be changed. This is important, because the custom sampler needs to receive 100% of spans to be able to properly perform its decision. ## Deploy the OpenTelemetry Collector {{< boilerplate start-otel... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/sampling/index.md | master | istio | [
-0.019804662093520164,
0.0028832678217440844,
-0.033609528094530106,
-0.023677164688706398,
-0.029013924300670624,
-0.0992497131228447,
0.043031029403209686,
-0.0051956758834421635,
0.0878417044878006,
0.05929040536284447,
0.039020996540784836,
-0.07980187982320786,
-0.00047299402649514377,
... | 0.162105 |
After completing this task, you understand how to have your application participate in tracing with [Zipkin](https://zipkin.io/), regardless of the language, framework, or platform you use to build your application. This task uses the [Bookinfo](/docs/examples/bookinfo/) sample as the example application. To learn how ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/zipkin/index.md | master | istio | [
-0.024441855028271675,
-0.018712811172008514,
-0.0794372484087944,
0.06952735781669617,
-0.011760701425373554,
-0.04852813854813576,
-0.00007356987771345302,
0.06583275645971298,
-0.04346785321831703,
0.04377497732639313,
-0.031148476526141167,
-0.0818457379937172,
0.03789066895842552,
0.0... | 0.409275 |
After completing this task, you will understand how to have your application participate in tracing with [Apache SkyWalking](https://skywalking.apache.org), regardless of the language, framework, or platform you use to build it. This task uses the [Bookinfo](/docs/examples/bookinfo/) sample as the example application. ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/skywalking/index.md | master | istio | [
-0.006831835024058819,
-0.06274539232254028,
-0.05347863957285881,
0.05105700343847275,
0.006771442014724016,
-0.06135844439268112,
0.02000310830771923,
0.05348597466945648,
-0.0311072189360857,
0.009828727692365646,
-0.007581461686640978,
-0.10803202539682388,
-0.07010512053966522,
0.0513... | 0.540502 |
{{< boilerplate telemetry-tracing-tips >}} Istio provides the ability to configure advanced tracing options, such as sampling rate and adding custom tags to reported spans. ## Before you begin 1. Ensure that your applications propagate tracing headers as described [here](/docs/tasks/observability/distributed-tracing/ov... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/mesh-and-proxy-config/index.md | master | istio | [
-0.03591528907418251,
-0.017356934025883675,
-0.03167551010847092,
0.05006462335586548,
-0.002952978480607271,
-0.13675948977470398,
0.041930943727493286,
0.07801183313131332,
-0.05433211475610733,
0.04537709429860115,
-0.053930990397930145,
-0.1170053780078888,
-0.041662320494651794,
0.02... | 0.507316 |
default rate is 1%. {{< warning >}} Previously, the recommended method was to change the `values.pilot.traceSampling` setting during the mesh setup or to change the `PILOT\_TRACE\_SAMPLE` environment variable in the istiod deployment. While this method to alter sampling continues to work, the following method is strong... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/mesh-and-proxy-config/index.md | master | istio | [
0.011691457591950893,
0.0030390191823244095,
-0.01954180747270584,
0.03778102621436119,
0.02227088436484337,
-0.08817566931247711,
0.05031885951757431,
0.03824489936232567,
0.03529655560851097,
0.052419744431972504,
-0.008764917030930519,
-0.13525663316249847,
-0.06271733343601227,
0.00935... | 0.339327 |
Distributed tracing enables users to track a request through mesh that is distributed across multiple services. This allows a deeper understanding about request latency, serialization and parallelism via visualization. Istio leverages [Envoy's distributed tracing](https://www.envoyproxy.io/docs/envoy/latest/intro/arch\... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/distributed-tracing/overview/index.md | master | istio | [
-0.022330136969685555,
-0.042565908282995224,
-0.022187354043126106,
0.04049089923501015,
0.017154080793261528,
-0.10366625338792801,
-0.016621919348835945,
0.0347219742834568,
-0.027608050033450127,
0.04966287687420845,
-0.06465865671634674,
-0.039232898503541946,
-0.0648057833313942,
0.0... | 0.492488 |
This task shows you how to use Envoy's native rate limiting to dynamically limit the traffic to an Istio service. In this task, you will apply a global rate-limit for the `productpage` service through ingress gateway that allows 1 requests per minute across all instances of the service. Additionally, you will apply a l... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/policy-enforcement/rate-limit/index.md | master | istio | [
-0.012910234741866589,
0.03557465225458145,
0.0074196988716721535,
-0.02183261327445507,
-0.0566909983754158,
-0.046450771391391754,
0.042622026056051254,
0.0029120827093720436,
0.045227836817502975,
0.050554726272821426,
-0.04801421985030174,
-0.06616886705160141,
0.007185033522546291,
0.... | 0.381529 |
1. Change VirtualService so the prefix `/api/v1/products` is moved to a route called `api`: {{< text bash >}} $ kubectl apply -f - <}} 1. Apply an EnvoyFilter to add the rate limits action at the route level on any 1 to 99 product and override the `ratelimit` domain: {{< text bash >}} $ kubectl apply -f - <}} ## Local ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/policy-enforcement/rate-limit/index.md | master | istio | [
0.0025838715955615044,
0.017757045105099678,
0.002996591618284583,
-0.06522521376609802,
-0.05553777143359184,
-0.0047955261543393135,
-0.04410590976476669,
-0.03518778458237648,
0.06668617576360703,
0.02126373164355755,
-0.013874121941626072,
-0.017999526113271713,
-0.014383039437234402,
... | 0.138728 |
envoyfilter filter-ratelimit-svc -nistio-system $ kubectl delete envoyfilter filter-ratelimit-svc-api -nistio-system $ kubectl delete envoyfilter filter-local-ratelimit-svc -nistio-system $ kubectl delete cm ratelimit-config $ kubectl delete -f @samples/ratelimit/rate-limit-service.yaml@ {{< /text >}} | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/policy-enforcement/rate-limit/index.md | master | istio | [
0.020898018032312393,
0.04388527199625969,
-0.017108948901295662,
-0.017095118761062622,
0.005894587375223637,
-0.04208708927035332,
-0.008167332969605923,
-0.06804869323968887,
0.08765155076980591,
0.006811791565269232,
0.03563429042696953,
-0.08689968287944794,
-0.07371871918439865,
-0.0... | 0.210213 |
{{< boilerplate alpha >}} Istio provides the ability to [extend proxy functionality using WebAssembly (Wasm)](/blog/2020/wasm-announce/). One of the key advantages of Wasm extensibility is that extensions can be loaded dynamically at runtime. These extensions must first be distributed to the Envoy proxy. Istio makes th... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/extensibility/wasm-module-distribution/index.md | master | istio | [
-0.022685594856739044,
0.02578064240515232,
-0.0839872807264328,
0.016599517315626144,
-0.006736716255545616,
-0.03691835328936577,
0.04301835596561432,
0.061040811240673065,
-0.08363465964794159,
0.06286544352769852,
0.002035126555711031,
-0.07639395445585251,
0.023871326819062233,
0.0494... | 0.374815 |
The [Accessing External Services](/docs/tasks/traffic-management/egress/egress-control) task and the [Configure an Egress Gateway](/docs/tasks/traffic-management/egress/egress-gateway/) example describe how to configure egress traffic for specific hostnames, like `edition.cnn.com`. This example shows how to enable egre... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/wildcard-egress-hosts/index.md | master | istio | [
-0.007836989127099514,
-0.03354765847325325,
-0.03713998943567276,
-0.001386729534715414,
-0.01914464309811592,
-0.04078573361039162,
0.050330858677625656,
-0.01229250431060791,
0.002111404901370406,
-0.029334506019949913,
-0.07476890832185745,
-0.06767376512289047,
0.0049879406578838825,
... | 0.203348 |
curl -- sh -c 'curl -s https://en.wikipedia.org/wiki/Main\_Page | grep -o ".\*"; curl -s https://de.wikipedia.org/wiki/Wikipedia:Hauptseite | grep -o ".\*"' Wikipedia, the free encyclopedia Wikipedia – Die freie Enzyklopädie {{< /text >}} ### Cleanup direct traffic to a wildcard host {{< text bash >}} $ kubectl delete ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/wildcard-egress-hosts/index.md | master | istio | [
0.013314290903508663,
0.03907894715666771,
-0.016177786514163017,
-0.03817492350935936,
-0.06015701964497566,
-0.0783478319644928,
0.037737179547548294,
-0.07180003076791763,
0.08151256293058395,
0.032312311232089996,
-0.019139127805829048,
-0.01709001511335373,
0.007410664577037096,
-0.04... | 0.141079 |
request. In the previous section you configured the virtual service to direct traffic to the predefined host `www.wikipedia.org`. In the general case, however, you don't know the host or IP address that can serve an arbitrary host received in a request, which leaves the original destination address of the request as th... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/wildcard-egress-hosts/index.md | master | istio | [
-0.004546864423900843,
0.043866511434316635,
-0.00028427582583390176,
-0.009806911461055279,
-0.07106027752161026,
-0.05843653157353401,
0.06022321805357933,
-0.029833361506462097,
0.02014828287065029,
0.02924373559653759,
-0.08984807878732681,
-0.06724273413419724,
-0.026139570400118828,
... | 0.355035 |
Kubernetes [ExternalName](https://kubernetes.io/docs/concepts/services-networking/service/#externalname) services and Kubernetes services with [Endpoints](https://kubernetes.io/docs/concepts/services-networking/service/#services-without-selectors) let you create a local DNS \_alias\_ to an external service. This DNS al... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-kubernetes-services/index.md | master | istio | [
-0.052302662283182144,
-0.02796095609664917,
0.02902456745505333,
-0.005986947100609541,
-0.05659889802336693,
-0.044164665043354034,
0.015608666464686394,
0.012798134237527847,
0.09845708310604095,
-0.021351508796215057,
-0.050125669687986374,
-0.08240468800067902,
-0.06370469182729721,
0... | 0.481744 |
recommend to perform [Egress TLS origination](/docs/tasks/traffic-management/egress/egress-tls-origination/) by Istio. {{< text bash >}} $ kubectl apply -f - <}} 1. Access `httpbin.org` via the Kubernetes service's hostname from the source pod with Istio sidecar. Notice the headers added by Istio sidecar, for example `... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-kubernetes-services/index.md | master | istio | [
0.01903606206178665,
0.0574810728430748,
-0.012998544611036777,
-0.013632395304739475,
-0.07195913791656494,
-0.019945984706282616,
0.0104097630828619,
-0.02740504778921604,
0.1085921972990036,
0.058480359613895416,
-0.0784909650683403,
-0.1361159235239029,
-0.06568563729524612,
-0.0075753... | 0.245136 |
1. Delete `without-istio` namespace: {{< text bash >}} $ kubectl delete namespace without-istio {{< /text >}} 1. Unset the environment variables: {{< text bash >}} $ unset SOURCE\_POD SOURCE\_POD\_WITHOUT\_ISTIO {{< /text >}} | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-kubernetes-services/index.md | master | istio | [
0.047050997614860535,
0.0470125786960125,
0.026789532974362373,
0.012368964962661266,
-0.017338166013360023,
0.002586888149380684,
0.027187470346689224,
-0.06067698821425438,
0.11630421876907349,
0.0006575759034603834,
-0.008107425644993782,
-0.12490596622228622,
-0.028761526569724083,
-0.... | 0.323367 |
The [TLS Origination for Egress Traffic](/docs/tasks/traffic-management/egress/egress-tls-origination/) example shows how to configure Istio to perform {{< gloss >}}TLS origination{{< /gloss >}} for traffic to an external service. The [Configure an Egress Gateway](/docs/tasks/traffic-management/egress/egress-gateway/) ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/index.md | master | istio | [
-0.1201535314321518,
0.011353583075106144,
-0.0188522357493639,
0.000313542754156515,
-0.07970967888832092,
-0.0726723000407219,
0.05429644510149956,
0.05239760875701904,
0.03583059087395668,
-0.011981189250946045,
-0.054411258548498154,
-0.10340192168951035,
-0.0613153912127018,
0.0339775... | 0.515871 |
>}} {{< text bash >}} $ kubectl apply -f - <}} {{< /tab >}} {{< tab name="Gateway API" category-value="gateway-api" >}} {{< text bash >}} $ kubectl apply -f - <}} {{< /tab >}} {{< /tabset >}} 5) Define a `DestinationRule` to perform TLS origination for requests to `edition.cnn.com`: {{< text bash >}} $ kubectl apply -f... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/index.md | master | istio | [
0.01622002199292183,
0.05927647650241852,
-0.032861724495887756,
-0.061978377401828766,
-0.05394575744867325,
-0.07425513118505478,
-0.01278120931237936,
-0.06220369413495064,
0.12047415971755981,
-0.016960518434643745,
-0.029606696218252182,
-0.12249234318733215,
0.010344314388930798,
-0.... | 0.074699 |
-subj '/O=example Inc./CN=example.com' -keyout example.com.key -out example.com.crt {{< /text >}} 1. Create a certificate and a private key for `my-nginx.mesh-external.svc.cluster.local`: {{< text bash >}} $ openssl req -out my-nginx.mesh-external.svc.cluster.local.csr -newkey rsa:2048 -nodes -keyout my-nginx.mesh-exte... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/index.md | master | istio | [
0.013241991400718689,
0.06555424630641937,
-0.0639747902750969,
0.014481502585113049,
0.04036732390522957,
-0.007962770760059357,
-0.07143253833055496,
0.02448795922100544,
0.05296529829502106,
-0.019735626876354218,
-0.013663413934409618,
-0.07490173727273941,
0.04678874462842941,
0.04252... | 0.000329 |
port 443, and a destination rule for sidecar requests that will be directed to the egress gateway: {{< tabset category-name="config-api" >}} {{< tab name="Istio APIs" category-value="istio-apis" >}} {{< text bash >}} $ kubectl apply -f - <}} {{< /tab >}} {{< tab name="Gateway API" category-value="gateway-api" >}} {{< t... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/index.md | master | istio | [
0.05850032716989517,
0.05514456331729889,
-0.035834938287734985,
0.0033180692698806524,
-0.06996658444404602,
-0.004701392725110054,
0.0033917196560651064,
-0.001554711489006877,
-0.0030173349659889936,
-0.0010927719995379448,
-0.026196148246526718,
-0.11891043931245804,
-0.07910191267728806... | 0.22892 |
$ kubectl delete secret nginx-server-certs nginx-ca-certs -n mesh-external $ kubectl delete configmap nginx-configmap -n mesh-external $ kubectl delete service my-nginx -n mesh-external $ kubectl delete deployment my-nginx -n mesh-external $ kubectl delete namespace mesh-external {{< /text >}} 1. Remove the gateway con... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/index.md | master | istio | [
-0.03719532489776611,
0.032101504504680634,
-0.024796107783913612,
-0.02667992375791073,
-0.04937036707997322,
-0.020968466997146606,
0.009131321683526039,
-0.028464268893003464,
0.07486269623041153,
0.0403183177113533,
-0.027009615674614906,
-0.1530391275882721,
-0.0014419121434912086,
0.... | 0.2884 |
Because all outbound traffic from an Istio-enabled pod is redirected to its sidecar proxy by default, accessibility of URLs outside of the cluster depends on the configuration of the proxy. By default, Istio configures the Envoy proxy to pass through requests for unknown services. Although this provides a convenient wa... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-control/index.md | master | istio | [
0.02566716820001602,
-0.012657169252634048,
0.019331492483615875,
0.032944872975349426,
-0.0310966856777668,
-0.049241650849580765,
0.00889489147812128,
0.046045344322919846,
0.006450704298913479,
0.04753044992685318,
-0.03562449663877487,
-0.04229569807648659,
-0.06276419013738632,
0.0328... | 0.504848 |
exec "$SOURCE\_POD" -c curl -- curl -sI https://edition.cnn.com | grep "HTTP/" HTTP/2 200 HTTP/2 200 {{< /text >}} Congratulations! You successfully sent egress traffic from your mesh. This simple approach to access external services, has the drawback that you lose Istio monitoring and control for traffic to external s... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-control/index.md | master | istio | [
-0.02790670655667782,
0.015452094376087189,
-0.012657937593758106,
0.013352254405617714,
-0.009582103230059147,
-0.04952164739370346,
0.001892130821943283,
0.025545137003064156,
-0.006887651979923248,
0.05643954128026962,
-0.02134144864976406,
-0.1030542254447937,
-0.038629621267318726,
-0... | 0.469579 |
http://httpbin.org/headers { "headers": { "Accept": "\*/\*", "Host": "httpbin.org", ... "X-Envoy-Decorator-Operation": "httpbin.org:80/\*", ... } } {{< /text >}} Note the headers added by the Istio sidecar proxy: `X-Envoy-Decorator-Operation`. 1. Check the log of the sidecar proxy of `SOURCE\_POD`: {{< text bash >}} $ ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-control/index.md | master | istio | [
0.014026165939867496,
0.05069165676832199,
0.03882753849029541,
-0.012719236314296722,
0.00046207287232391536,
-0.07751332968473434,
-0.023746805265545845,
-0.06021923944354057,
0.057573072612285614,
0.03867059946060181,
-0.012546617537736893,
-0.084651418030262,
-0.05313752964138985,
-0.0... | 0.28068 |
the `kubectl apply` command. This can also be configured on a pod by setting corresponding [annotations](/docs/reference/config/annotations/) such as `traffic.sidecar.istio.io/includeOutboundIPRanges`. After updating the `istio-sidecar-injector` configuration, it affects all future application pod deployments. {{< warn... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-control/index.md | master | istio | [
0.005048385355621576,
0.008185498416423798,
0.029147692024707794,
0.0194704532623291,
-0.046174198389053345,
-0.004514818079769611,
0.02436358854174614,
0.014081723988056183,
-0.012577425688505173,
0.02173970639705658,
-0.01995037868618965,
-0.0120659489184618,
-0.055140238255262375,
0.016... | 0.404253 |
az network vnet list -g MC\_user-rg\_user-cluster\_region | grep name "name": "aks-vnet-74242220", "name": "aks-subnet", $ az network vnet show -g MC\_user-rg\_user-cluster\_region -n aks-vnet-74242220 | grep addressPrefix "addressPrefixes": [ "addressPrefix": "10.224.0.0/16", {{< /text >}} Then use `--set values.globa... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-control/index.md | master | istio | [
0.06786106526851654,
0.09722491353750229,
-0.017989635467529297,
-0.013616194948554039,
-0.02235434204339981,
0.02326870895922184,
0.04435500502586365,
-0.0232022013515234,
0.019857484847307205,
0.055122196674346924,
-0.04163309559226036,
-0.0771082192659378,
0.0013367518549785018,
-0.0007... | 0.060721 |
configuring the proxy this way does require cluster-provider specific knowledge and configuration. Similar to the first approach, you also lose monitoring of access to external services and you can't apply Istio features on traffic to external services. ## Security note {{< warning >}} Note that configuration examples ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-control/index.md | master | istio | [
-0.03872760012745857,
0.02778494730591774,
-0.03874817118048668,
0.026260223239660263,
-0.07332806289196014,
0.02271200716495514,
0.0830451101064682,
0.043502502143383026,
-0.02812808007001877,
0.012014660984277725,
-0.04848694056272507,
-0.07018216699361801,
-0.040722526609897614,
-0.0201... | 0.458651 |
{{}} This example does not work in Minikube. {{}} The [Accessing External Services](/docs/tasks/traffic-management/egress/egress-control) task shows how to configure Istio to allow access to external HTTP and HTTPS services from applications inside the mesh. There, the external services are called directly from the cli... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md | master | istio | [
-0.026210356503725052,
0.07543355226516724,
-0.03884925693273544,
0.014362877234816551,
-0.0382203571498394,
-0.001195935532450676,
0.028321562334895134,
0.1298782229423523,
0.0013995333574712276,
0.023904353380203247,
-0.03574157878756523,
-0.055358078330755234,
-0.003906634170562029,
0.0... | 0.396824 |
fields to your configuration: {{< text yaml >}} spec: components: egressGateways: - name: istio-egressgateway enabled: true {{< /text >}} Otherwise, add the equivalent settings to your original `istioctl install` command, for example: {{< text syntax=bash snip\_id=none >}} $ istioctl install \ --set "components.egressG... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md | master | istio | [
-0.028406307101249695,
0.005364739801734686,
-0.04812191426753998,
0.01067068986594677,
-0.07936237007379532,
-0.027576077729463577,
0.04993598908185959,
-0.0015353407943621278,
0.03853389620780945,
0.000013270794624986593,
-0.044918324798345566,
-0.030815908685326576,
-0.021854743361473083,... | 0.330196 |
89 "10.244.2.10" "curl/7.64.0" "ea379962-9b5c-4431-ab66-f01994f5a5a5" "edition.cnn.com" "151.101.65.67:80" outbound|80||edition.cnn.com - 10.244.1.5:80 10.244.2.10:50482 edition.cnn.com - {{< /text >}} {{< tip >}} If [mutual TLS Authentication](/docs/tasks/security/authentication/authn-policy/) is enabled, and you have... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md | master | istio | [
-0.058146536350250244,
0.0455874502658844,
0.024115458130836487,
-0.019251158460974693,
-0.04621165618300438,
-0.04062449559569359,
-0.01367548480629921,
-0.011046593077480793,
0.07880227267742157,
-0.022772958502173424,
-0.007994947023689747,
-0.09067898988723755,
-0.03329109400510788,
0.... | 0.195268 |
the additional hosts. {{< /tip >}} {{< text bash >}} $ kubectl apply -f - <}} {{< /tab >}} {{< tab name="Gateway API" category-value="gateway-api" >}} {{< text bash >}} $ kubectl apply -f - <}} {{< /tab >}} {{< /tabset >}} 4) Send an HTTPS request to [https://edition.cnn.com/politics](https://edition.cnn.com/politics).... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md | master | istio | [
0.04656478762626648,
0.05050154775381088,
-0.02413824386894703,
-0.013409765437245369,
-0.03231647238135338,
-0.060738831758499146,
-0.012408454902470112,
-0.08601466566324234,
0.09379689395427704,
0.005534536205232143,
-0.033676017075777054,
-0.11060255765914917,
-0.020902322605252266,
-0... | 0.030321 |
or the cloud provider can prevent the allocation of public IPs to pods other than gateways and can configure NAT devices to drop packets not originating at the egress gateways. ## Apply Kubernetes network policies This section shows you how to create a [Kubernetes network policy](https://kubernetes.io/docs/concepts/ser... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md | master | istio | [
0.008478003554046154,
0.059787992388010025,
0.03545660898089409,
0.01963185891509056,
-0.05620744079351425,
0.0024718260392546654,
0.024796418845653534,
-0.05224239453673363,
0.07589887082576752,
0.08150406181812286,
-0.057673461735248566,
-0.033704884350299835,
-0.012357315979897976,
-0.0... | 0.116171 |
-- curl -v -sS https://edition.cnn.com/politics Hostname was NOT found in DNS cache Trying 151.101.65.67... Trying 2a04:4e42:200::323... Immediate connect fail for 2a04:4e42:200::323: Cannot assign requested address Trying 2a04:4e42:400::323... Immediate connect fail for 2a04:4e42:400::323: Cannot assign requested addr... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md | master | istio | [
-0.04753937944769859,
0.030168376863002777,
-0.023595696315169334,
0.00835403986275196,
-0.09455063194036484,
-0.051807716488838196,
-0.1010747030377388,
-0.06945382803678513,
-0.008683301508426666,
0.018726371228694916,
-0.002488838043063879,
-0.05594845861196518,
-0.08569782227277756,
0.... | 0.224261 |
$ kubectl delete networkpolicy allow-egress-to-istio-system-and-kube-dns -n test-egress $ kubectl label namespace kube-system kube-system- $ kubectl label namespace istio-system istio- $ kubectl delete namespace test-egress {{< /text >}} {{< /tab >}} {{< tab name="Gateway API" category-value="gateway-api" >}} {{< text ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md | master | istio | [
0.015638703480362892,
0.03313940018415451,
-0.06457757949829102,
-0.0260144229978323,
-0.06722921133041382,
0.008743255399167538,
0.021214118227362633,
-0.05896782875061035,
0.10029374808073044,
0.027649100869894028,
0.005317607428878546,
-0.12730741500854492,
-0.05682985112071037,
-0.0935... | 0.217217 |
The [Accessing External Services](/docs/tasks/traffic-management/egress/egress-control) task demonstrates how external, i.e., outside of the service mesh, HTTP and HTTPS services can be accessed from applications inside the mesh. As described in that task, a [`ServiceEntry`](/docs/reference/config/networking/service-en... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-tls-origination/index.md | master | istio | [
-0.10899245738983154,
0.04131428152322769,
-0.033530447632074356,
-0.01579628325998783,
-0.034681130200624466,
-0.06942826509475708,
0.08539139479398727,
0.05168299749493599,
0.06944960355758667,
-0.01097268145531416,
-0.04995046555995941,
-0.06834873557090759,
0.014237761497497559,
0.0446... | 0.545893 |
of the URL, \_politics\_ in this case, is sent in clear text. If there is an attacker who sniffs the communication between your application and `edition.cnn.com`, the attacker would know which specific topics of `edition.cnn.com` the application fetched. For privacy reasons, you might want to prevent such disclosure. B... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-tls-origination/index.md | master | istio | [
-0.01056700199842453,
0.08495816588401794,
0.027397122234106064,
-0.056125398725271225,
-0.0207267664372921,
-0.06298096477985382,
0.011520303785800934,
-0.03658955171704292,
0.10104319453239441,
-0.05863429978489876,
-0.07692964375019073,
-0.09643853455781937,
0.0026847582776099443,
0.005... | 0.232925 |
because it requires the following setup: 1. Generate client and server certificates 1. Deploy an external service that supports the mutual TLS protocol 1. Configure the client (curl pod) to use the credentials created in Step 1 Once this setup is complete, you can then configure the external traffic to go through the s... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-tls-origination/index.md | master | istio | [
-0.027899770066142082,
0.059539299458265305,
-0.04163418710231781,
-0.009905854240059853,
-0.0039191036485135555,
-0.04455331712961197,
-0.06771574914455414,
0.0025483109056949615,
0.08881530165672302,
0.020863505080342293,
-0.026646995916962624,
-0.026376644149422646,
0.0018521881429478526,... | 0.029146 |
/tip >}} 1. Create required `RBAC` to make sure the secret created in the above step is accessible to the client pod, which is `curl` in this case. {{< text bash >}} $ kubectl create role client-credential-role --resource=secret --verb=list $ kubectl create rolebinding client-credential-role-binding --role=client-crede... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/egress-tls-origination/index.md | master | istio | [
-0.01586766727268696,
0.07055174559354782,
-0.02248261496424675,
-0.01691124215722084,
-0.07161425799131393,
-0.017397861927747726,
-0.004146703984588385,
-0.03129378333687782,
0.03910781070590019,
-0.0036359508521854877,
-0.01141496654599905,
-0.11776935309171677,
0.02782212197780609,
-0.... | 0.046018 |
The [Configure an Egress Gateway](/docs/tasks/traffic-management/egress/egress-gateway/) example shows how to direct traffic to external services from your mesh via an Istio edge component called \_Egress Gateway\_. However, some cases require an external, legacy (non-Istio) HTTPS proxy to access external services. For... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/http-proxy/index.md | master | istio | [
-0.039970796555280685,
0.008521052077412605,
-0.019291788339614868,
0.013546246103942394,
-0.06713119149208069,
-0.02903280220925808,
0.018626179546117783,
0.03863028064370155,
0.015128915198147297,
0.01661054603755474,
-0.04684651643037796,
-0.022666510194540024,
-0.07216739654541016,
0.0... | 0.33848 |
deployed the HTTPS proxy. \* You used `curl` to access the `wikipedia.org` external service through the proxy. Next, you must configure the traffic from the Istio-enabled pods to use the HTTPS proxy. ## Configure traffic to external HTTPS proxy 1. Define a TCP (not HTTP!) Service Entry for the HTTPS proxy. Although app... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/egress/http-proxy/index.md | master | istio | [
0.010018444620072842,
0.01983526349067688,
0.000498476903885603,
-0.006068485323339701,
-0.10277535021305084,
-0.055753376334905624,
-0.002517635701224208,
0.010602152906358242,
0.04934034124016762,
0.038967471569776535,
-0.02217390574514866,
-0.08052750676870346,
-0.008187668398022652,
0.... | 0.326705 |
In a regular Istio mesh deployment, the TLS termination for downstream requests is performed at the Ingress Gateway. Although this satisfies most use cases, for some (like an API Gateway in the mesh) the Ingress Gateway is not necessarily needed. This task shows how to eliminate the additional hop introduced by the Ist... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/ingress-sidecar-tls-termination/index.md | master | istio | [
-0.041016463190317154,
0.07184061408042908,
0.0054200198501348495,
0.01639004610478878,
-0.0427970290184021,
-0.06661584973335266,
0.02851778455078602,
-0.002483148593455553,
0.039685215801000595,
0.038012631237506866,
-0.02066635899245739,
-0.07788663357496262,
-0.02148933708667755,
0.062... | 0.420206 |
`MUTUAL`. {{< text bash >}} $ kubectl -n test apply -f - <}} ## Verification Now that the httpbin server is deployed and configured, bring up two clients to test the end to end connectivity from both inside and outside of the mesh: 1. An internal client (curl) in the same namespace (test) as the httpbin service, with s... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/ingress-sidecar-tls-termination/index.md | master | istio | [
-0.0007844126666896045,
0.037275731563568115,
-0.01339226495474577,
-0.053728844970464706,
-0.06144528463482857,
-0.03812938556075096,
-0.031661078333854675,
-0.036862995475530624,
0.047860968858003616,
0.03586225211620331,
0.05319392681121826,
-0.06863687932491302,
0.0032880266662687063,
... | 0.064056 |
-n test $ kubectl delete deployment httpbin curl -n test $ kubectl delete namespace test $ kubectl delete service curl $ kubectl delete deployment curl {{< /text >}} 1. Delete the certificates and private keys: {{< text bash >}} $ rm example.com.crt example.com.key httpbin.test.svc.cluster.local.crt httpbin.test.svc.cl... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/ingress-sidecar-tls-termination/index.md | master | istio | [
0.019759422168135643,
0.03284091874957085,
-0.03824557363986969,
-0.023873625323176384,
-0.028729667887091637,
-0.026551349088549614,
-0.03553507477045059,
-0.04772571101784706,
0.09517860412597656,
0.026453668251633644,
0.037807244807481766,
-0.1124800592660904,
-0.034668855369091034,
-0.... | 0.258461 |
Along with support for Kubernetes [Ingress](/docs/tasks/traffic-management/ingress/kubernetes-ingress/) resources, Istio also allows you to configure ingress traffic using either an [Istio Gateway](/docs/concepts/traffic-management/#gateways) or [Kubernetes Gateway](https://gateway-api.sigs.k8s.io/api-types/gateway/) r... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/ingress-control/index.md | master | istio | [
-0.02755304053425789,
0.004624310415238142,
0.011059231124818325,
0.01993556320667267,
-0.04640176519751549,
-0.004832814913243055,
0.0586644783616066,
0.06911601126194,
0.021434353664517403,
0.053527090698480606,
-0.08517120033502579,
-0.09527131170034409,
-0.031948432326316833,
0.0135818... | 0.556387 |
the `Gateway`. {{< /tip >}} Because creating a Kubernetes `Gateway` resource will also [deploy an associated proxy service](/docs/tasks/traffic-management/ingress/gateway-api/#automated-deployment), run the following command to wait for the gateway to be ready: {{< text bash >}} $ kubectl wait --for=condition=programme... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/ingress-control/index.md | master | istio | [
-0.0026361546479165554,
0.017947567626833916,
-0.0212053582072258,
-0.010682370513677597,
-0.08819278329610825,
0.0020345994271337986,
0.016271185129880905,
-0.02524426020681858,
0.07858020812273026,
0.07880225032567978,
-0.05783643573522568,
-0.04806248098611832,
-0.012537614442408085,
-0... | 0.124379 |
bash >}} $ export INGRESS\_HOST=$(kubectl -n "$INGRESS\_NS" get service "$INGRESS\_NAME" -o jsonpath='{.status.loadBalancer.ingress[0].hostname}') {{< /text >}} {{< /warning >}} {{< /tab >}} {{< tab name="Gateway API" category-value="gateway-api" >}} Get the gateway address and port from the httpbin gateway resource: {... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/ingress-control/index.md | master | istio | [
0.0027547585777938366,
0.03657621517777443,
-0.06040883809328079,
-0.008054696023464203,
-0.008847399614751339,
-0.028431372717022896,
0.02854176238179207,
-0.04129309579730034,
0.06278668344020844,
0.01713375374674797,
-0.05256161466240883,
-0.1041034683585167,
-0.019093751907348633,
-0.0... | 0.103654 |
Set the ingress ports: {{< text bash >}} $ export INGRESS\_PORT=$(kubectl -n "${INGRESS\_NS}" get service "${INGRESS\_NAME}" -o jsonpath='{.spec.ports[?(@.name=="http2")].nodePort}') $ export SECURE\_INGRESS\_PORT=$(kubectl -n "${INGRESS\_NS}" get service "${INGRESS\_NAME}" -o jsonpath='{.spec.ports[?(@.name=="https")]... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/ingress-control/index.md | master | istio | [
-0.0027582950424402952,
0.05319691821932793,
-0.037675999104976654,
0.011228570714592934,
-0.00907303299754858,
-0.02790079265832901,
0.04492298141121864,
-0.018003985285758972,
0.03235182538628578,
0.03358662500977516,
-0.011823389679193497,
-0.10016319155693054,
0.004663553554564714,
-0.... | 0.100036 |
The [Securing Gateways with HTTPS](/docs/tasks/traffic-management/ingress/secure-ingress/) task describes how to configure HTTPS ingress access to an HTTP service. This example describes how to configure HTTPS ingress access to an HTTPS service, i.e., configure an ingress gateway to perform SNI passthrough, instead of ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/ingress-sni-passthrough/index.md | master | istio | [
-0.015343466773629189,
0.05467282235622406,
0.0159447118639946,
0.018818669021129608,
-0.07258377224206924,
-0.03019595332443714,
0.05100027099251747,
0.01949610747396946,
0.04732624441385269,
0.049575746059417725,
-0.07707776129245758,
-0.10495006293058395,
0.00664921710267663,
0.02915537... | 0.400902 |
apply -f - <}} {{< /tab >}} {{< tab name="Gateway API" category-value="gateway-api" >}} {{< text bash >}} $ kubectl apply -f - <}} {{< /tab >}} {{< /tabset >}} 2) Configure routes for traffic entering via the `Gateway`: {{< tabset category-name="config-api" >}} {{< tab name="Istio APIs" category-value="istio-apis" >}} ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/ingress-sni-passthrough/index.md | master | istio | [
0.04905056208372116,
0.055917732417583466,
-0.05730912461876869,
-0.031033838167786598,
-0.055368781089782715,
0.009679864160716534,
0.04904462397098541,
0.013213316909968853,
0.011804502457380295,
0.013786270283162594,
-0.030945759266614914,
-0.13166853785514832,
-0.021486759185791016,
-0... | 0.182624 |
The [Control Ingress Traffic task](/docs/tasks/traffic-management/ingress/ingress-control) describes how to configure an ingress gateway to expose an HTTP service to external traffic. This task shows how to expose a secure HTTPS service using either simple or mutual TLS. {{< boilerplate gateway-api-support >}} ## Befor... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/secure-ingress/index.md | master | istio | [
-0.03369421511888504,
0.03136083483695984,
-0.010663527064025402,
-0.016907373443245888,
-0.04896281659603119,
-0.0665598064661026,
0.00776784447953105,
-0.0032232627272605896,
0.06412599980831146,
0.041678402572870255,
-0.042852409183979034,
-0.11663348972797394,
-0.021481608971953392,
0.... | 0.392668 |
443, and specify values for `credentialName` to be `httpbin-credential`. The values are the same as the secret's name. The TLS mode should have the value of `SIMPLE`. {{< text bash >}} $ cat <}} Next, configure the gateway's ingress traffic routes by defining a corresponding virtual service: {{< text bash >}} $ cat <}}... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/secure-ingress/index.md | master | istio | [
-0.025085072964429855,
0.06321854889392853,
-0.02454538084566593,
-0.027058742940425873,
-0.09424886852502823,
-0.01339215412735939,
0.047775331884622574,
-0.0011173862731084228,
0.0859837755560875,
0.07081620395183563,
-0.07725732028484344,
-0.10548326373100281,
0.048943158239126205,
0.01... | 0.116654 |
cat <}} Configure the gateway's traffic routes by defining a corresponding virtual service. {{< text bash >}} $ cat <}} {{< /tab >}} {{< tab name="Gateway API" category-value="gateway-api" >}} Configure a `Gateway` with two listeners for port 443. Set the value of `certificateRefs` on each listener to `httpbin-credenti... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/secure-ingress/index.md | master | istio | [
0.022432077676057816,
0.023034213110804558,
-0.06055070459842682,
-0.05411884933710098,
-0.08788663893938065,
-0.08223078399896622,
0.00889919325709343,
-0.036662906408309937,
0.02458013780415058,
-0.022172024473547935,
-0.05452694371342659,
-0.10011925548315048,
0.07774623483419418,
0.073... | -0.02114 |
\* A TLS Secret with keys `tls.key` and `tls.crt`, as described above. For mutual TLS, a `ca.crt` key can be used. \* A TLS Secret with keys `tls.key` and `tls.crt`, as described above. For mutual TLS, a separate generic Secret named `-cacert`, with a `cacert` key. For example, `httpbin-credential` has `tls.key` and `t... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/secure-ingress/index.md | master | istio | [
-0.10270145535469055,
0.024687526747584343,
-0.057168107479810715,
-0.06124400720000267,
-0.04724353179335594,
-0.025623109191656113,
0.0793040320277214,
0.012049171142280102,
0.099640391767025,
-0.022652843967080116,
0.061403337866067886,
-0.12631922960281372,
0.11040960997343063,
0.02755... | 0.067415 |
{{< /text >}} {{< /tab >}} {{< /tabset >}} 2) Delete the secrets, certificates and keys: {{< text bash >}} $ kubectl delete -n istio-system secret httpbin-credential helloworld-credential $ rm -rf ./example\_certs1 ./example\_certs2 {{< /text >}} 1) Shutdown the `httpbin` and `helloworld` services: {{< text bash >}} $ ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/secure-ingress/index.md | master | istio | [
0.01505374163389206,
0.07595540583133698,
-0.058861322700977325,
-0.05021557956933975,
-0.027951864525675774,
-0.03432687744498253,
0.03435517102479935,
-0.05833609029650688,
0.05650901421904564,
0.03306977078318596,
0.03591230511665344,
-0.09566844254732132,
0.056745242327451706,
0.007909... | 0.169373 |
This task describes how to configure Istio to expose a service outside of the service mesh cluster, using the Kubernetes [Ingress Resource](https://kubernetes.io/docs/concepts/services-networking/ingress/). {{< tip >}} Using a [Gateway](/docs/tasks/traffic-management/ingress/ingress-control/), rather than Ingress, is r... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/kubernetes-ingress/index.md | master | istio | [
-0.0135758426040411,
0.01569216512143612,
0.0027959600556641817,
0.009037982672452927,
-0.029879463836550713,
0.0023817680776119232,
0.06266209483146667,
0.05429987236857414,
-0.005319192074239254,
0.06185202673077583,
-0.027985038235783577,
-0.09084805846214294,
-0.008147653192281723,
0.0... | 0.523193 |
In addition to its own traffic management API, {{< boilerplate gateway-api-future >}} This document describes the differences between the Istio and Kubernetes APIs and provides a simple example that shows you how to configure Istio to expose a service outside the service mesh cluster using the Gateway API. Note that th... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/gateway-api/index.md | master | istio | [
-0.039041850715875626,
-0.007560967933386564,
-0.014655409380793571,
0.011431095190346241,
-0.058488842099905014,
0.008943282067775726,
0.013878176920115948,
0.06976597011089325,
0.0359770804643631,
0.05628840997815132,
-0.06672780215740204,
-0.06864482909440994,
-0.014491318725049496,
-0.... | 0.557101 |
request to the ingress IP. 1. Access any other URL that has not been explicitly exposed. You should see an HTTP 404 error: {{< text bash >}} $ curl -s -I -HHost:httpbin.example.com "http://$INGRESS\_HOST/headers" HTTP/1.1 404 Not Found ... {{< /text >}} 1. Update the route rule to also expose `/headers` and to add a he... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/gateway-api/index.md | master | istio | [
0.016432322561740875,
0.07984530180692673,
0.01678483933210373,
-0.021455077454447746,
-0.03614179790019989,
-0.010955318808555603,
-0.017131321132183075,
-0.02257920429110527,
0.06701722741127014,
0.06296996772289276,
-0.04148074612021446,
-0.09610190987586975,
0.022654308006167412,
-0.06... | 0.082532 |
\* Gateway: `-` \* Waypoint: `` For example, to deploy a `Gateway` with a `HorizontalPodAutoscaler` and `PodDisruptionBudget`: {{< text yaml >}} apiVersion: gateway.networking.k8s.io/v1 kind: Gateway metadata: name: gateway spec: gatewayClassName: istio listeners: - name: default hostname: "\*.example.com" port: 80 pro... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/ingress/gateway-api/index.md | master | istio | [
0.008003578521311283,
0.008116796612739563,
0.0032751820981502533,
0.006555687170475721,
-0.044025909155607224,
-0.020272720605134964,
-0.03315233439207077,
-0.002225382486358285,
0.01814337447285652,
0.04264501854777336,
-0.0005923667922616005,
-0.044955916702747345,
-0.03245515003800392,
... | 0.214769 |
This task shows you how to set up request timeouts in Envoy using Istio. {{< boilerplate gateway-api-support >}} ## Before you begin \* Setup Istio by following the instructions in the [Installation guide](/docs/setup/). \* Deploy the [Bookinfo](/docs/examples/bookinfo/) sample application including the [service versio... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/request-timeouts/index.md | master | istio | [
-0.02982163615524769,
0.01654440350830555,
-0.07236894965171814,
0.090891033411026,
-0.0564764104783535,
-0.016098983585834503,
-0.05167626589536667,
0.0027710844296962023,
0.03624922037124634,
0.04215472564101219,
-0.06072455644607544,
-0.034091170877218246,
-0.0380198210477829,
0.0281834... | 0.419995 |
examine the [fault injection task](/docs/tasks/traffic-management/fault-injection/), you'll find out that the `productpage` microservice also has its own application-level timeout (3 seconds) for calls to the `reviews` microservice. Notice that in this task you used an Istio route rule to set the timeout to half a seco... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/request-timeouts/index.md | master | istio | [
0.014352445490658283,
0.03985658660531044,
0.004615833051502705,
0.06514834612607956,
-0.018936028704047203,
-0.051713235676288605,
-0.00404058862477541,
0.04331733658909798,
0.007589127402752638,
0.026782650500535965,
-0.015775734558701515,
-0.03141448646783829,
-0.028633203357458115,
0.0... | 0.389011 |
This task shows you how to configure circuit breaking for connections, requests, and outlier detection. Circuit breaking is an important pattern for creating resilient microservice applications. Circuit breaking allows you to write applications that limit the impact of failures, latency spikes, and other undesirable ef... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/circuit-breaking/index.md | master | istio | [
-0.05533801391720772,
0.0021132847759872675,
0.010523315519094467,
-0.00028400809969753027,
-0.06290557980537415,
-0.08085130155086517,
0.023833032697439194,
0.05298147350549698,
-0.05054229497909546,
0.059778790920972824,
-0.02395961433649063,
-0.06861884891986847,
0.01214265450835228,
0.... | 0.3881 |
Fortio 1.3.1 running at 0 queries per second, 6->6 procs, for 20 calls: http://httpbin:8000/get Starting at max qps with 2 thread(s) [gomax 6] for exactly 20 calls (10 per thread + 0) 20:33:46 W http\_client.go:679> Parsed non ok code 503 (HTTP/1.1 503) 20:33:47 W http\_client.go:679> Parsed non ok code 503 (HTTP/1.1 5... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/circuit-breaking/index.md | master | istio | [
-0.045262642204761505,
-0.007713373750448227,
-0.07438941299915314,
0.035684358328580856,
-0.05030520632863045,
-0.09312870353460312,
-0.056175608187913895,
0.07448841631412506,
0.08917245268821716,
-0.0001843758363975212,
-0.03022082895040512,
-0.02455885335803032,
-0.016328195109963417,
... | 0.23539 |
503) 20:32:30 W http\_client.go:679> Parsed non ok code 503 (HTTP/1.1 503) 20:32:30 W http\_client.go:679> Parsed non ok code 503 (HTTP/1.1 503) 20:32:30 W http\_client.go:679> Parsed non ok code 503 (HTTP/1.1 503) Ended after 51.9946ms : 30 calls. qps=576.98 Aggregated Function Time : count 30 avg 0.0040001633 +/- 0.0... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/circuit-breaking/index.md | master | istio | [
-0.040269333869218826,
0.04519647732377052,
-0.05483665317296982,
-0.001318458584137261,
-0.09791582822799683,
-0.08137086033821106,
-0.021604696288704872,
0.032924167811870575,
0.07660301774740219,
0.05645965784788132,
0.00973897147923708,
-0.014793800190091133,
0.005194506142288446,
0.00... | 0.014554 |
This task shows you how to route requests dynamically to multiple versions of a microservice. {{< boilerplate gateway-api-support >}} ## Before you begin \* Setup Istio by following the instructions in the [Installation guide](/docs/setup/). \* Deploy the [Bookinfo](/docs/examples/bookinfo/) sample application. \* Revi... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/request-routing/index.md | master | istio | [
-0.03574705868959427,
-0.05792622268199921,
-0.026320738717913628,
-0.0025645261630415916,
-0.0832628682255745,
-0.0394800566136837,
-0.02066045254468918,
-0.004729310050606728,
0.030365008860826492,
0.013090547174215317,
-0.055287446826696396,
-0.017520248889923096,
-0.027903631329536438,
... | 0.369056 |
All references resolved observedGeneration: 8 reason: ResolvedRefs status: "True" type: ResolvedRefs controllerName: istio.io/gateway-controller parentRef: group: gateway.networking.k8s.io kind: Service name: reviews port: 9080 {{< /text >}} In the resource status, make sure that the `Accepted` condition is `True` for ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/request-routing/index.md | master | istio | [
-0.04874146357178688,
-0.06425639986991882,
-0.04363485798239708,
0.049163736402988434,
-0.05325336754322052,
0.02093733474612236,
0.0006673203897662461,
-0.0008697714074514806,
-0.005820390302687883,
0.09107179194688797,
-0.019329389557242393,
-0.04506981372833252,
-0.0070149595849215984,
... | 0.276771 |
follow the same basic pattern you learned here to configure route rules to gradually send traffic from one version of a service to another. ## Cleanup 1. Remove the application route rules: {{< tabset category-name="config-api" >}} {{< tab name="Istio APIs" category-value="istio-apis" >}} {{< text bash >}} $ kubectl de... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/request-routing/index.md | master | istio | [
0.006103850435465574,
0.01293964497745037,
-0.013703905045986176,
-0.028291916474699974,
-0.03252018988132477,
-0.03414042294025421,
0.003277513198554516,
-0.05476649850606918,
0.03336739540100098,
0.0332387238740921,
-0.03780980780720711,
-0.04966580867767334,
-0.04655654355883598,
-0.020... | 0.295715 |
This task shows you how to shift TCP traffic from one version of a microservice to another. A common use case is to migrate TCP traffic gradually from an older version of a microservice to a new one. In Istio, you accomplish this goal by configuring a sequence of routing rules that redirect a percentage of TCP traffic ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/tcp-traffic-shifting/index.md | master | istio | [
-0.00853071641176939,
-0.02343730814754963,
0.013747774995863438,
0.0032182899303734303,
-0.10024348646402359,
-0.0412009060382843,
0.05183481052517891,
0.03674130141735077,
-0.005861932411789894,
0.030743073672056198,
-0.05109758675098419,
-0.16688944399356842,
-0.033675093203783035,
-0.0... | 0.433484 |
APIs" category-value="istio-apis" >}} {{< text bash >}} $ kubectl apply -f @samples/tcp-echo/tcp-echo-20-v2.yaml@ -n istio-io-tcp-traffic-shifting {{< /text >}} {{< /tab >}} {{< tab name="Gateway API" category-value="gateway-api" >}} {{< text bash >}} $ kubectl apply -f @samples/tcp-echo/gateway-api/tcp-echo-20-v2.yaml... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/tcp-traffic-shifting/index.md | master | istio | [
0.001792046008631587,
0.05122695490717888,
0.014251396991312504,
-0.02766876108944416,
-0.005692473612725735,
-0.04681461676955223,
0.03648656606674194,
-0.033909764140844345,
0.0357072651386261,
0.011328094638884068,
-0.01913749985396862,
-0.13290859758853912,
-0.04684178903698921,
-0.020... | 0.252681 |
delete namespace istio-io-tcp-traffic-shifting {{< /text >}} | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/tcp-traffic-shifting/index.md | master | istio | [
-0.05135096609592438,
0.020348960533738136,
0.009271703660488129,
0.045731376856565475,
-0.040842268615961075,
-0.049238625913858414,
0.07553575187921524,
-0.036760807037353516,
0.053048353642225266,
-0.005256911274045706,
-0.00004282784357201308,
-0.09662340581417084,
-0.06451825797557831,
... | 0.449842 |
{{< warning >}} A [template bug in the Istio website code](https://github.com/istio/istio.io/issues/15689) means that the examples on this page do not render properly. You can [view the page source](https://raw.githubusercontent.com/istio/istio.io/master/content/en/docs/tasks/traffic-management/mirroring/index.md) to s... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/mirroring/index.md | master | istio | [
-0.06837251782417297,
-0.00400187261402607,
0.017863282933831215,
0.03920113667845726,
-0.01656509004533291,
-0.08627107739448547,
0.009232423268258572,
0.04093622788786888,
-0.02103886939585209,
0.010794750414788723,
-0.07669629156589508,
-0.07837134599685669,
-0.039407119154930115,
0.001... | 0.596066 |
the `mirrorPercentage` field to mirror a fraction of the traffic, instead of mirroring all requests. If this field is absent, all traffic will be mirrored. {{< /tab >}} {{< tab name="Gateway API" category-value="gateway-api" >}} {{< text bash >}} $ kubectl apply -f - <}} This route rule sends 100% of the traffic to `v1... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/mirroring/index.md | master | istio | [
0.00473465071991086,
-0.006135262548923492,
0.041172634810209274,
-0.03626071661710739,
-0.07202580571174622,
-0.07574700564146042,
-0.03931279480457306,
-0.07622445374727249,
0.0769738107919693,
0.04073403775691986,
-0.055187929421663284,
-0.07843059301376343,
-0.021303657442331314,
-0.09... | 0.062292 |
This task shows you how to inject faults to test the resiliency of your application. ## Before you begin \* Set up Istio by following the instructions in the [Installation guide](/docs/setup/). \* Deploy the [Bookinfo](/docs/examples/bookinfo/) sample application including the [default destination rules](/docs/examples... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/fault-injection/index.md | master | istio | [
0.00899510644376278,
-0.0048695760779082775,
0.024781562387943268,
-0.007942830212414265,
-0.05753673240542412,
-0.05701250955462456,
-0.0019512687576934695,
0.04276718944311142,
-0.028635229915380478,
0.04386395588517189,
-0.04074101895093918,
-0.10709038376808167,
-0.009816747158765793,
... | 0.431513 |
/tip >}} ## Fixing the bug You would normally fix the problem by: 1. Either increasing the `productpage` to `reviews` service timeout or decreasing the `reviews` to `ratings` timeout 1. Stopping and restarting the fixed microservice 1. Confirming that the `/productpage` web page returns its response without any errors.... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/traffic-management/fault-injection/index.md | master | istio | [
-0.0566580668091774,
-0.05909092351794243,
-0.011007308028638363,
-0.004481783136725426,
0.0042849937453866005,
-0.01995028369128704,
-0.03721174970269203,
-0.08156999200582504,
-0.011366603896021843,
0.07566990703344345,
0.02223118394613266,
0.006635819561779499,
0.011609651148319244,
0.0... | -0.01359 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.