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 |
|---|---|---|---|---|---|
event log. ### x509 certificate related errors {{< text plain >}} Warning FailedCreate 3m (x17 over 8m) replicaset-controller Error creating: Internal error occurred: \ failed calling admission webhook "sidecar-injector.istio.io": Post https://istiod.istio-system.svc:443/inject: \ x509: certificate signed by unknown au... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/injection/index.md | master | istio | [
-0.02499462105333805,
0.07757701724767685,
-0.006431096699088812,
0.004068898037075996,
0.04171343147754669,
-0.05975574254989624,
-0.03681756556034088,
-0.011166242882609367,
0.01639585755765438,
0.027340177446603775,
0.04755663871765137,
-0.16363361477851868,
0.029463328421115875,
0.0403... | 0.187708 |
is to include `istio-sidecar-injector.istio-system.svc` or `.svc` in the `no\_proxy` value. Make sure that `kube-apiserver` is restarted after each workaround. An [issue](https://github.com/kubernetes/kubeadm/issues/666) was filed with Kubernetes related to this and has since been closed. [https://github.com/kubernetes... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/injection/index.md | master | istio | [
0.009539546445012093,
0.014936654828488827,
0.01871778815984726,
-0.0010841167531907558,
-0.021814359351992607,
-0.01164258737117052,
-0.017810039222240448,
-0.004281830042600632,
0.008409116417169571,
0.0996270626783371,
-0.024667460471391678,
-0.06027288734912872,
-0.05554459989070892,
-... | 0.272504 |
## No traces appearing in Zipkin when running Istio locally on Mac Istio is installed and everything seems to be working except there are no traces showing up in Zipkin when there should be. This may be caused by a known [Docker issue](https://github.com/docker/for-mac/issues/1260) where the time inside containers may ... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/observability-issues/index.md | master | istio | [
-0.010848063044250011,
0.05652378872036934,
0.03587138280272484,
0.06441637128591537,
0.06542336195707321,
-0.08908005803823471,
-0.015718501061201096,
0.02321828529238701,
-0.011466225609183311,
0.016654781997203827,
-0.04737409949302673,
-0.08720242977142334,
-0.04888693243265152,
0.0926... | 0.378642 |
## End-user authentication fails With Istio, you can enable authentication for end users through [request authentication policies](/docs/tasks/security/authentication/authn-policy/#end-user-authentication). Follow these steps to troubleshoot the policy specification. 1. If `jwksUri` isn’t set, make sure the JWT issuer ... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/security-issues/index.md | master | istio | [
-0.10367583483457565,
0.011961901560425758,
0.0036798755172640085,
-0.02825121022760868,
-0.007609768770635128,
-0.06119013577699661,
-0.007248749025166035,
0.02520674653351307,
-0.03687675669789314,
-0.00543363718315959,
-0.06722912192344666,
-0.07747570425271988,
-0.011994503438472748,
0... | 0.339878 |
HTTP-only fields on the port, make sure the port name has the `http-` prefix. ### Make sure the policy is applied to the correct target Check the workload selector and namespace to confirm it's applied to the correct targets. You can determine the authorization policy in effect by running `istioctl x authz check POD-NA... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/security-issues/index.md | master | istio | [
0.003219215665012598,
0.06572310626506805,
-0.013803146779537201,
-0.021119732409715652,
-0.00030300545040518045,
-0.0609978586435318,
0.04225757345557213,
-0.07583274692296982,
0.005569258239120245,
0.04367142915725708,
-0.004212248604744673,
0.020473506301641464,
-0.03177052363753319,
0.... | 0.224567 |
TCP filters to filter chain 2 \* added 1 TCP filters to filter chain 3 \* added 1 TCP filters to filter chain 4 2021-04-23T20:53:29.510903Z info ads LDS: PUSH for node:curl-557747455f-6dxbl.foo resources:18 size:85.0kB 2021-04-23T20:53:29.511487Z info ads LDS: PUSH for node:httpbin-74fb669cc6-lpscm.foo resources:18 siz... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/security-issues/index.md | master | istio | [
-0.051791489124298096,
0.06644844263792038,
0.009526923298835754,
0.006251170299947262,
0.03740504011511803,
-0.06060243770480156,
0.0579725056886673,
-0.07586660981178284,
0.00899474136531353,
0.016398129984736443,
0.0052934191189706326,
-0.09390512853860855,
-0.04094303026795387,
-0.0144... | 0.265653 |
{ fields { key: "request.auth.principal" value { string\_value: "cluster.local/ns/foo/sa/curl" } } fields { key: "source.namespace" value { string\_value: "foo" } } fields { key: "source.principal" value { string\_value: "cluster.local/ns/foo/sa/curl" } } fields { key: "source.user" value { string\_value: "cluster.loca... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/security-issues/index.md | master | istio | [
-0.004524827003479004,
0.05901787802577019,
-0.03209661692380905,
0.03321431949734688,
0.00021726952400058508,
-0.019122222438454628,
0.024248600006103516,
-0.06638956815004349,
0.019916711375117302,
0.06346119940280914,
0.0005121548310853541,
-0.05510716140270233,
0.02152862399816513,
0.0... | 0.107606 |
client sidecars are misbehaved, report an issue on GitHub. | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/security-issues/index.md | master | istio | [
-0.042455147951841354,
-0.020540334284305573,
-0.037629056721925735,
0.03801035135984421,
0.02647963911294937,
-0.03427750989794731,
-0.09737227112054825,
-0.026084784418344498,
-0.0050270333886146545,
-0.01554790697991848,
0.05931304022669792,
0.08809467405080795,
-0.029606467112898827,
0... | -0.031269 |
## EnvoyFilter migration `EnvoyFilter` is an alpha API that is tightly coupled to the implementation details of Istio xDS configuration generation. Production use of the `EnvoyFilter` alpha API must be carefully curated during the upgrade of Istio's control or data plane. In many instances, `EnvoyFilter` can be replace... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/upgrade-issues/index.md | master | istio | [
-0.03968938812613487,
-0.018978731706738472,
0.017071356996893883,
-0.007482669781893492,
-0.027899114415049553,
-0.12157762050628662,
0.043370433151721954,
0.026537707075476646,
-0.014260479249060154,
0.012536457739770412,
-0.011359214782714844,
-0.09381110221147537,
-0.05181722715497017,
... | 0.42104 |
applyTo: BOOTSTRAP patch: operation: MERGE value: stats\_config: histogram\_bucket\_settings: - match: prefix: istiocustom buckets: [1,5,50,500,5000,10000] {{< /text >}} Use the equivalent pod annotation: {{< text yaml >}} metadata: annotations: "sidecar.istio.io/statsHistogramBuckets": '{"istiocustom":[1,5,50,500,5000... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/upgrade-issues/index.md | master | istio | [
0.036446548998355865,
0.09359757602214813,
0.02373594231903553,
0.02447224222123623,
0.03742316737771034,
0.03279527649283409,
0.015162259340286255,
0.06687688827514648,
-0.03137555345892906,
0.04482845962047577,
-0.00785418413579464,
-0.07955557107925415,
-0.017509786412119865,
-0.0163450... | 0.266716 |
## Seemingly valid configuration is rejected Use [istioctl validate -f](/docs/reference/commands/istioctl/#istioctl-validate) and [istioctl analyze](/docs/reference/commands/istioctl/#istioctl-analyze) for more insight into why the configuration is rejected. Use an \_istioctl\_ CLI with a similar version to the control... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/validation/index.md | master | istio | [
-0.034875184297561646,
-0.030875258147716522,
-0.03203035891056061,
0.01296051312237978,
-0.026967715471982956,
-0.04041152074933052,
0.026719730347394943,
0.04398072138428688,
-0.04453321546316147,
0.020032882690429688,
0.0047209057956933975,
-0.16895976662635803,
0.004620420280843973,
0.... | 0.498152 |
the `istiod` pod(s) are running and endpoints are ready. {{< text bash >}} $ kubectl -n istio-system get pod -lapp=istiod NAME READY STATUS RESTARTS AGE istiod-5dbbbdb746-d676g 1/1 Running 0 2d {{< /text >}} {{< text bash >}} $ kubectl -n istio-system get endpoints istiod NAME ENDPOINTS AGE istiod 10.48.6.108:15014,10.... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/common-problems/validation/index.md | master | istio | [
0.07196816802024841,
0.007011112757027149,
0.01990543305873871,
-0.021260330453515053,
-0.02118460275232792,
-0.03178809583187103,
-0.03073495253920555,
-0.011353100650012493,
0.04034348577260971,
0.0696713924407959,
0.004305473528802395,
-0.12556076049804688,
-0.0869038999080658,
0.024180... | 0.37268 |
Istio security features provide strong identity, powerful policy, transparent TLS encryption, and authentication, authorization and audit (AAA) tools to protect your services and data. However, to fully make use of these features securely, care must be taken to follow best practices. It is recommended to review the [Se... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
-0.10444407910108566,
0.04442395269870758,
0.0063989171758294106,
0.003912695217877626,
-0.05003242567181587,
-0.08561703562736511,
0.07464641332626343,
0.01889079436659813,
0.016776176169514656,
-0.022628486156463623,
-0.004138598218560219,
-0.05280894413590431,
0.0106004374101758,
0.0755... | 0.471498 |
policy bound to the `istio-waypoint` `GatewayClass` should be used in addition to the "classic" default-deny policy. The "classic" default-deny policy will be enforced by ztunnel against the workloads in your mesh and still provides meaningful value. {{< /tip >}} #### Use `ALLOW-with-positive-matching` and `DENY-with-n... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
-0.07218045741319656,
0.09724775701761246,
-0.010509640909731388,
0.023296630010008812,
-0.0012859012931585312,
-0.05401802062988281,
0.06200406327843666,
-0.03209352493286133,
0.006007230840623379,
-0.0006962927873246372,
0.03325090557336807,
-0.021456904709339142,
0.036600787192583084,
0... | 0.213118 |
Refer to [Customize your system on path normalization](/docs/ops/best-practices/security/#customize-your-system-on-path-normalization) to understand the detail of each normalization option. \* Refer to [Mitigation for unsupported normalization](/docs/ops/best-practices/security/#mitigation-for-unsupported-normalization... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
0.011823312379419804,
0.03235612064599991,
-0.0388406366109848,
-0.0177018865942955,
-0.00939294882118702,
-0.055153198540210724,
0.002752200234681368,
-0.01008271798491478,
-0.07902763783931732,
0.003312149550765753,
0.04042729735374451,
0.02535829320549965,
0.05709858983755112,
0.0609911... | 0.038108 |
`%5c`) are decoded to `/` or `\`, before the `MERGE\_SLASHES` normalization. | `/a%2fb` is normalized to `/a/b`. | {{< tip >}} The configuration is specified via the [`pathNormalization`](/docs/reference/config/istio.mesh.v1alpha1/#MeshConfig-ProxyPathNormalization) field in the [mesh config](/docs/reference/config/ist... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
-0.03900265321135521,
-0.0015794598730280995,
-0.0185097586363554,
0.007030642591416836,
-0.0013319195713847876,
-0.0582791231572628,
-0.029396045953035355,
0.029231255874037743,
-0.029933856800198555,
0.020822936668992043,
0.03516669198870659,
-0.026017550379037857,
-0.04083152860403061,
... | 0.363245 |
manner. For example, treating `https://myurl/get` and `https://myurl/GeT` as equivalent. In those cases, the `EnvoyFilter` shown below can be used to insert a Lua filter to normalize the path to lower case. This filter will change both the path used for comparison and the path presented to the application. {{< text syn... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
-0.016192849725484848,
0.05464787408709526,
0.036314595490694046,
0.0037785836029797792,
-0.02682773396372795,
-0.09223674237728119,
-0.006031691562384367,
0.022776590660214424,
0.008184487000107765,
-0.01218494400382042,
-0.02856387197971344,
-0.06784629821777344,
-0.013734213076531887,
0... | 0.274358 |
the client. Currently, the authorization policy only supports enforcing access control on inbound traffic and not the outbound traffic. It also does not support server-first TCP protocols because the first bytes are sent by the server application even before it received any data from the client. In this case, the initi... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
-0.028441229835152626,
0.07114747911691666,
0.00754372077062726,
-0.019223928451538086,
-0.03545920178294182,
-0.01820172183215618,
0.13846789300441742,
0.011361577548086643,
-0.03757640719413757,
0.04361884668469429,
0.028336936607956886,
-0.018700338900089264,
0.012974254786968231,
0.052... | 0.269193 |
should be considered best-effort. While this is useful to prevent accidental dependencies, if you want to secure egress traffic, and enforce all outbound traffic goes through a proxy, you should instead rely on an [Egress Gateway](/docs/tasks/traffic-management/egress/egress-gateway/). When combined with a [Network Pol... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
-0.03695056214928627,
0.08818533271551132,
0.05776113644242287,
-0.03467802703380585,
-0.06072600930929184,
0.00424531102180481,
0.0757700651884079,
-0.013906878419220448,
0.0430118702352047,
0.031931072473526,
-0.028127240017056465,
-0.03295722231268883,
-0.06692001968622208,
0.0019372582... | 0.218638 |
be desired to enforce stricter physical isolation for sensitive services. For example, you may want to run a [dedicated gateway instance](/docs/setup/install/istioctl/#configure-gateways) for a sensitive `payments.example.com`, while utilizing a single shared gateway instance for less sensitive domains like `blog.examp... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
-0.047653522342443466,
0.045062556862831116,
-0.03836057335138321,
-0.004802867770195007,
-0.04313259944319725,
-0.07608857750892639,
0.041886456310749054,
-0.02829006500542164,
0.010212975554168224,
0.0033762867096811533,
-0.03843432292342186,
-0.06963091343641281,
0.03452769294381142,
0.... | 0.250165 |
are exposed by the `pilot\_total\_xds\_rejects` metric, in addition to logs. \* Test your configuration to ensure it gives the expected results. For a security policy, it is useful to run positive and negative tests to ensure you do not accidentally restrict too much or too few traffic. ## Avoid alpha and experimental ... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
0.02749544009566307,
-0.011827792972326279,
0.008386936038732529,
0.03936818242073059,
0.040399350225925446,
-0.050551701337099075,
0.009910302236676216,
0.047456979751586914,
-0.09322967380285263,
0.02154562994837761,
0.029625779017806053,
-0.07702028751373291,
-0.033921532332897186,
0.05... | 0.515141 |
To work around you this, you must configure an appropriate connection limit for your environment. ### Configure `global\_downstream\_max\_connections` value The following configuration can be supplied during installation: {{< text yaml >}} meshConfig: defaultConfig: runtimeValues: "overload.global\_downstream\_max\_con... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/security/index.md | master | istio | [
0.06214519217610359,
-0.003159962361678481,
-0.01092579122632742,
-0.018297618255019188,
-0.03167019411921501,
-0.08140861243009567,
-0.08539500087499619,
0.018978990614414215,
0.032909080386161804,
0.048444610089063644,
0.0016938963672146201,
0.005902050528675318,
-0.06410882622003555,
0.... | -0.013001 |
## Using Prometheus for production-scale monitoring The recommended approach for production-scale monitoring of Istio meshes with Prometheus is to use [hierarchical federation](https://prometheus.io/docs/prometheus/latest/federation/#hierarchical-federation) in combination with a collection of [recording rules](https:/... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/observability/index.md | master | istio | [
-0.02595425397157669,
-0.00029644177993759513,
0.009876251220703125,
0.03552626818418503,
0.004735380411148071,
-0.11647789180278778,
-0.006385469809174538,
-0.0010831319959834218,
-0.008773612789809704,
0.03615088388323784,
-0.019045419991016388,
-0.10085167735815048,
-0.002807173179462552,... | 0.395055 |
metrics collection with recording rules](/docs/ops/best-practices/observability/#optimizing-metrics-collection-with-recording-rules). {{< /tip >}} ### Federation using workload-level aggregated metrics To establish Prometheus federation, modify the configuration of your production-ready deployment of Prometheus to scra... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/observability/index.md | master | istio | [
-0.031180988997220993,
0.03472669795155525,
-0.009769327938556671,
0.029752103611826897,
-0.03344950079917908,
-0.05764473229646683,
0.03902082145214081,
0.00045001873513683677,
0.015167352743446827,
0.01392186526209116,
-0.01800166815519333,
-0.13756243884563446,
-0.03617045655846596,
0.0... | 0.355524 |
We have identified the following general principles to help you get the most out of your Istio deployments. These best practices aim to limit the impact of bad configuration changes and make managing your deployments easier. ## Deploy fewer clusters Deploy Istio across a small number of large clusters, rather than a la... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/deployment/index.md | master | istio | [
0.05999409779906273,
-0.05993156135082245,
-0.0032520988024771214,
0.03116496093571186,
-0.030262457206845284,
-0.03492653742432594,
-0.0011743531795218587,
0.061946287751197815,
-0.06902206689119339,
0.041864488273859024,
-0.01451356802135706,
-0.1231292262673378,
0.03039505146443844,
0.0... | 0.441293 |
This section provides specific deployment or configuration guidelines to avoid networking or traffic management issues. ## Set default routes for services Although the default Istio behavior conveniently sends traffic from any source to all versions of a destination service without any rules being set, creating a `Virt... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/traffic-management/index.md | master | istio | [
0.004783095326274633,
-0.019685188308358192,
0.02993207983672619,
0.013733869418501854,
-0.04140421003103256,
-0.01554903481155634,
0.04181002080440521,
0.013248831033706665,
-0.01938909851014614,
0.03151433914899826,
-0.07410866767168045,
-0.055620938539505005,
-0.05615667626261711,
0.045... | 0.50509 |
the namespace also needs to be on the destination rule lookup path: 1. client namespace 1. service namespace 1. the configured `meshconfig.rootNamespace` namespace (`istio-system` by default) For example, consider the following destination rule: {{< text yaml >}} apiVersion: networking.istio.io/v1 kind: DestinationRule... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/traffic-management/index.md | master | istio | [
-0.05469663441181183,
-0.04921570047736168,
-0.035837773233652115,
0.015277457423508167,
-0.02373727597296238,
-0.06440052390098572,
0.07541297376155853,
0.005733033642172813,
0.04158025607466698,
0.03065650165081024,
-0.04219996929168701,
-0.08485673367977142,
-0.0036475840024650097,
0.06... | 0.355896 |
preferable to break up the configuration of `myapp.com` into several `VirtualService` fragments, one per backend service. For example: {{< text yaml >}} apiVersion: networking.istio.io/v1 kind: VirtualService metadata: name: myapp-service1 spec: hosts: - myapp.com gateways: - myapp-gateway http: - match: - uri: prefix:... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/traffic-management/index.md | master | istio | [
-0.033903952687978745,
-0.01704859733581543,
0.006647811271250248,
-0.016299664974212646,
-0.01865432970225811,
-0.08842117339372635,
0.002243764465674758,
0.002085764892399311,
0.02454517036676407,
0.026601405814290047,
-0.021331127732992172,
-0.0591665543615818,
-0.04899495840072632,
0.0... | 0.313303 |
the rule using `kubectl` or any platform-specific tooling. 1. Wait a few seconds for the `DestinationRule` configuration to propagate to the Envoy sidecars 1. Update the `VirtualService` to refer to the newly added subsets. \* When removing subsets: 1. Update `VirtualServices` to remove any references to a subset, befo... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/traffic-management/index.md | master | istio | [
0.051302433013916016,
-0.012413416989147663,
0.015752069652080536,
-0.024157844483852386,
0.0020654352847486734,
-0.032221220433712006,
0.02166033163666725,
-0.12036894261837006,
0.03803938627243042,
0.0007174342172220349,
0.052955761551856995,
-0.03507983684539795,
-0.02361319027841091,
-... | 0.110393 |
This page describes how to use [Cosign](https://github.com/sigstore/cosign) to validate the provenance of Istio image artifacts. Cosign is a tool developed as part of the [sigstore](https://www.sigstore.dev) project, which simplifies signing and validation of signed Open Container Initiative (OCI) artifacts, such as co... | https://github.com/istio/istio.io/blob/master//content/en/docs/ops/best-practices/image-signing-validation/index.md | master | istio | [
-0.028013644739985466,
0.09273133426904678,
-0.016663849353790283,
-0.06472314894199371,
0.009034156799316406,
-0.14036273956298828,
-0.011486547067761421,
0.05217211693525314,
-0.05159498751163483,
-0.01873389258980751,
0.031217945739626884,
-0.07511568814516068,
0.0003641933435574174,
0.... | 0.269291 |
Thanks for your interest in Istio! Istio has two primary modes: \*\*ambient mode\*\* and \*\*sidecar mode\*\*. \* [Ambient mode](/docs/overview/dataplane-modes/#ambient-mode) is the new and improved model, created to address the shortcomings of sidecar mode. In ambient mode, a secure tunnel is installed on each node, a... | https://github.com/istio/istio.io/blob/master//content/en/docs/overview/quickstart/index.md | master | istio | [
-0.07279224693775177,
0.01827256754040718,
0.04145551100373268,
0.05038873106241226,
-0.041360482573509216,
-0.04705372080206871,
0.04587666317820549,
0.03313383460044861,
-0.006332112941890955,
0.02610224299132824,
-0.04072517901659012,
-0.04884329065680504,
-0.02036498300731182,
-0.01727... | 0.539691 |
An Istio service mesh is logically split into a data plane and a control plane. The {{< gloss >}}data plane{{< /gloss >}} is the set of proxies that mediate and control all network communication between microservices. They also collect and report telemetry on all mesh traffic. The {{< gloss >}}control plane{{< /gloss >... | https://github.com/istio/istio.io/blob/master//content/en/docs/overview/dataplane-modes/index.md | master | istio | [
-0.04624836519360542,
-0.02960888482630253,
0.0090520353987813,
0.02398865856230259,
-0.06554662436246872,
-0.03982192650437355,
0.05322134867310524,
0.004257347900420427,
-0.028178350999951363,
0.05358292534947395,
0.011128327809274197,
-0.03721608966588974,
-0.047452718019485474,
-0.0134... | 0.58406 |
[configuration of the scope of each sidecar](/docs/ops/configuration/mesh/configuration-scoping/) to reduce configuration | Works without custom configuration | | Supports "server-first" protocols | [Requires configuration](/docs/ops/deployment/application-requirements/#server-first-protocols) | Yes | | Support for Kub... | https://github.com/istio/istio.io/blob/master//content/en/docs/overview/dataplane-modes/index.md | master | istio | [
0.021604521200060844,
0.030160224065184593,
0.043954577296972275,
-0.0014743893407285213,
-0.010529964230954647,
0.037147801369428635,
-0.05938452482223511,
0.004153392277657986,
-0.03002198040485382,
0.026799578219652176,
-0.011027234606444836,
0.0015541855245828629,
-0.009409932419657707,
... | 0.175096 |
connections. | Full application and connection-level faults ([timeouts, delays, specific response codes](/docs/tasks/traffic-management/fault-injection/)). | | Traffic mirroring | N/A—HTTP only | [Percentage-based mirroring of requests to multiple backends](/docs/tasks/traffic-management/mirroring/). | ## Unsupported f... | https://github.com/istio/istio.io/blob/master//content/en/docs/overview/dataplane-modes/index.md | master | istio | [
0.015513361431658268,
-0.037956926971673965,
0.03504800796508789,
0.026565855368971825,
-0.023913277313113213,
-0.043312687426805496,
-0.05812351405620575,
-0.013083131983876228,
-0.13514259457588196,
-0.009433379396796227,
0.03175879642367363,
-0.021306032314896584,
-0.03963621333241463,
... | 0.13731 |
Istio is an open source service mesh that layers transparently onto existing distributed applications. Istio’s powerful features provide a uniform and more efficient way to secure, connect, and monitor services. Istio is the path to load balancing, service-to-service authentication, and monitoring – with few or no serv... | https://github.com/istio/istio.io/blob/master//content/en/docs/overview/what-is-istio/index.md | master | istio | [
-0.06984308362007141,
0.006793650798499584,
-0.02091570757329464,
0.0031820926815271378,
-0.007692279294133186,
-0.03425218537449837,
0.07438351213932037,
0.04682318493723869,
0.04720601066946983,
0.033300284296274185,
-0.06926839053630829,
-0.09468900412321091,
-0.017954126000404358,
0.00... | 0.65491 |
Istio pioneered the concept of a sidecar-based service mesh when it launched in 2017. Out of the gate, the project included the features that would come to define a service mesh, including standards-based mutual TLS for zero-trust networking, smart traffic routing, and observability through metrics, logs and tracing. S... | https://github.com/istio/istio.io/blob/master//content/en/docs/overview/why-choose-istio/index.md | master | istio | [
-0.05887417495250702,
0.018079057335853577,
0.04855632409453392,
-0.0007918774499557912,
-0.029271503910422325,
-0.07378882169723511,
0.02127399854362011,
0.04975501447916031,
0.03393850848078728,
0.03982488438487053,
-0.07054341584444046,
-0.08911903947591782,
-0.0018741359235718846,
0.03... | 0.517376 |
is a science project and unlikely to have real world practicality. Other meshes that claim to "use eBPF" actually use a per-node Envoy proxy, or other user space tools, for much of their functionality. ### Why not use a per-node proxy? Envoy is not inherently multi-tenant. As a result, we have major security and stabil... | https://github.com/istio/istio.io/blob/master//content/en/docs/overview/why-choose-istio/index.md | master | istio | [
0.03478654846549034,
-0.02881120704114437,
0.08414027094841003,
0.027825644239783287,
-0.009984578005969524,
-0.005584546830505133,
-0.040612660348415375,
-0.022564005106687546,
0.02116486057639122,
0.10981183499097824,
-0.08838950097560883,
-0.06552193313837051,
-0.02563885971903801,
-0.0... | 0.097411 |
The following are the standard service level metrics exported by Istio. The telemetry component is implemented as a [Proxy extension](https://github.com/istio/proxy/tree/master/source/extensions/filters/http/istio\_stats). A `COUNTER` is a strictly increasing integer. A `DISTRIBUTION` maps ranges of values to frequency... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/metrics/index.md | master | istio | [
-0.038073062896728516,
-0.04102965071797371,
-0.05181356519460678,
0.024278046563267708,
-0.09377240389585495,
-0.08387404680252075,
0.03448208048939705,
0.047277163714170456,
0.05329578369855881,
0.0015929018845781684,
-0.04918463155627251,
-0.09267264604568481,
-0.029751650989055634,
0.0... | 0.535188 |
(`destination\_version`): This identifies the version of the destination workload, or `unknown` if the destination information is missing. \* \*\*Destination Service\*\* (`destination\_service`): This identifies destination service host responsible for an incoming request. Ex: `details.default.svc.cluster.local`. \* \*... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/metrics/index.md | master | istio | [
-0.000986199826002121,
-0.02300901524722576,
-0.10657037049531937,
0.0017820874927565455,
0.02835630252957344,
-0.006850384641438723,
0.06337698549032211,
-0.040810152888298035,
0.022529780864715576,
0.0076704989187419415,
-0.018497250974178314,
-0.028138449415564537,
-0.07206356525421143,
... | 0.233354 |
This message occurs when an Istio resource references another resource that does not exist. This will lead to errors when Istio tries to look up the referenced resource but cannot find it. For example, you receive this error: {{< text plain >}} Error [IST0101] (VirtualService httpbin.default) Referenced gateway not fou... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0101/index.md | master | istio | [
-0.023102156817913055,
-0.0049002221785485744,
-0.054991789162158966,
0.016832154244184494,
0.008928081952035427,
-0.030081843957304955,
0.037883345037698746,
-0.008933641016483307,
0.026667285710573196,
-0.014546679332852364,
-0.029459070414304733,
-0.11928519606590271,
-0.02946026064455509... | 0.51817 |
This message occurs when your Istio configuration does not successfully pass schema validation. For example, you receive this error: {{< text plain >}} Error [IST0106] (VirtualService ratings-bogus-weight-default.default) Schema validation error: percentage 888 is not in range 0..100 {{< /text >}} and your Istio config... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0106/index.md | master | istio | [
0.012077485211193562,
0.038903649896383286,
-0.036219362169504166,
0.08957453072071075,
-0.01029322948306799,
-0.02588779665529728,
0.023026006296277046,
0.046526748687028885,
0.0018990824464708567,
-0.0012756387004628778,
-0.006078239995986223,
-0.16905200481414795,
-0.00789183285087347,
... | 0.417061 |
This message occurs when a virtual service contains a match rule that will never be used because a previous rule specifies the same match. It also occurs when there is more than one rule without any match at all. ## Example You will receive this message: {{< text plain >}} Warning [IST0130] (VirtualService sample-foo-c... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0130/index.md | master | istio | [
0.01719694584608078,
0.031027549877762794,
-0.0011783693917095661,
0.020942747592926025,
0.07722784578800201,
-0.03383689746260643,
0.008447947911918163,
-0.02034110762178898,
0.028700929135084152,
0.027823027223348618,
0.0015070370864123106,
-0.09979059547185898,
-0.02325942926108837,
0.0... | 0.336979 |
This message occurs when two services select the same workload with the same `targetPort` but different `port`s. ## An example Consider an Istio mesh with the following services: {{< text yaml >}} apiVersion: v1 kind: Service metadata: name: nginx-a spec: ports: - port: 8080 protocol: TCP targetPort: 80 selector: app: ... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0137/index.md | master | istio | [
-0.052912067621946335,
0.0183841772377491,
0.013526706025004387,
-0.043585099279880524,
-0.036300938576459885,
-0.06198927015066147,
0.04800485819578171,
-0.0496363528072834,
0.03958186134696007,
-0.020856549963355064,
-0.017783895134925842,
-0.029197392985224724,
-0.001011108746752143,
0.... | 0.182261 |
This message occurs when the address provided for the ingress gateway on the external control plane is not valid. The address could be invalid for several reasons including: the hostname address is malformed, the hostname cannot be resolved to an IP address via a DNS lookup, or the hostname resolves to zero IP addresse... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0163/index.md | master | istio | [
-0.05519409105181694,
0.021455714479088783,
-0.027220848947763443,
0.030088139697909355,
-0.003111965022981167,
-0.043983954936265945,
0.019355086609721184,
0.02751712128520012,
-0.032382383942604065,
0.02840007282793522,
0.06292954832315445,
-0.147661954164505,
-0.013553940691053867,
-0.0... | 0.353289 |
in a failure to resolve lookups. New DNS records may take up to 72 hours to propagate across the web depending on your DNS provider and specific configuration. If your hostname resolves to zero IP addresses, check that the webhook URLs are using the correct hostname and that your DNS provider correctly has at least one... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0163/index.md | master | istio | [
-0.0394732803106308,
0.010318923741579056,
0.01216917671263218,
-0.011247568763792515,
-0.013322708196938038,
-0.16914387047290802,
-0.13219265639781952,
-0.08781049400568008,
0.04478972405195236,
0.00908130593597889,
0.024767085909843445,
-0.02335955575108528,
-0.03256398066878319,
-0.092... | -0.014949 |
This message occurs when the address provided for the ingress gateway on the external control plane is an IP address and not a hostname. ## Example You will receive this message: {{< text plain >}} Info [IST0164] (MutatingWebhookConfiguration istio-sidecar-injector-external-istiod testing.yml:28) The address (https://9... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0164/index.md | master | istio | [
-0.03692148998379707,
0.05861850455403328,
-0.012449918314814568,
0.0670914426445961,
0.027668748050928116,
-0.05507409945130348,
0.010400368832051754,
0.011907951906323433,
-0.009309227578341961,
0.0414297990500927,
0.05049697682261467,
-0.13741888105869293,
-0.019324231892824173,
-0.0112... | 0.33331 |
This message occurs when an `EnvoyFilter` uses the `REPLACE` operation and `ApplyTo` is set to `HTTP\_FILTER` or `NETWORK\_FILTER`. This will cause the `REPLACE` operation to be ignored as `HTTP\_FILTER` and `NETWORK\_FILTER` are not valid for `REPLACE`. ## An example Consider an `EnvoyFilter` with the patch operation ... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0152/index.md | master | istio | [
-0.05115702375769615,
0.042930278927087784,
0.0666140541434288,
0.02273416891694069,
0.008532463572919369,
-0.06481354683637619,
0.021431274712085724,
-0.055112920701503754,
0.020742539316415787,
0.027567481622099876,
-0.004929311573505402,
-0.06687894463539124,
-0.06043174862861633,
-0.00... | 0.156897 |
This message occurs when an `EnvoyFilter` does not have a priority and uses a relative patch operation (`INSERT\_BEFORE/AFTER`, `REPLACE`, `MERGE`, `DELETE`) and `proxyVersion` set which can cause the `EnvoyFilter` not to be applied during an upgrade. Using the `INSERT\_FIRST` or `ADD` option or setting the priority ma... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0155/index.md | master | istio | [
-0.03625655174255371,
-0.010504977777600288,
0.07347561419010162,
-0.003269529901444912,
0.012565513141453266,
-0.055484235286712646,
-0.0011510283220559359,
-0.04727404564619064,
-0.008272835053503513,
0.0640294998884201,
0.01601281575858593,
0.012974339537322521,
-0.055469587445259094,
0... | 0.140491 |
This message occurs when an Istio or Kubernetes resource has an Istio annotation that is new, has been incompletely implemented, or lacks performance testing. Consult Istio's [Feature Status documentation](/docs/releases/feature-stages/) for information on the relative maturity and support level of Istio features. ## H... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0136/index.md | master | istio | [
0.04421349614858627,
-0.019949404522776604,
0.050282735377550125,
0.04558349773287773,
0.023389870300889015,
-0.04382580146193504,
-0.012843788601458073,
-0.0017804736271500587,
-0.032891761511564255,
0.010079311206936836,
-0.004639849066734314,
-0.1415957659482956,
-0.076234370470047,
0.0... | 0.516289 |
This message occurs when Istio detects an overlap between [virtual service](/docs/reference/config/networking/virtual-service) resources that conflict with one another. For example, multiple virtual services defined to use the same hostname and attached to a mesh gateway will generate an error message. Note that Istio ... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0109/index.md | master | istio | [
-0.036201734095811844,
-0.01540426816791296,
-0.030048202723264694,
0.0038567367009818554,
0.005223581567406654,
-0.05150838568806648,
0.03766278550028801,
-0.02404787577688694,
0.03353586420416832,
0.028057105839252472,
-0.005327262450009584,
-0.10061158984899521,
-0.013880877755582333,
0... | 0.463802 |
This message occurs when a virtual service contains a match rule that will never be used because a previous rule specifies the same match. ## Example You will receive this message: {{< text plain >}} Info [IST0131] (VirtualService tls-routing.default) VirtualService rule #1 match #0 is not used (duplicates a match in r... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0131/index.md | master | istio | [
-0.027911745011806488,
0.04569963738322258,
0.02112889289855957,
-0.025867845863103867,
0.010819756425917149,
-0.07254723459482193,
0.021367711946368217,
-0.0892941951751709,
0.04453972727060318,
0.002816716441884637,
0.015187354758381844,
-0.08017929643392563,
0.022956347092986107,
0.0294... | 0.232173 |
This message occurs when an `EnvoyFilter` uses the `REMOVE` operation and `ApplyTo` is set to `ROUTE\_CONFIGURATION` or `HTTP\_ROUTE`. This will cause the `REMOVE` operation to be ignored. At the moment only the `MERGE` operation can be used for `ROUTE\_CONFIGURATION`. ## An example Consider an `EnvoyFilter` with the p... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0154/index.md | master | istio | [
-0.0160997174680233,
0.053554654121398926,
0.012105405330657959,
0.04816262796521187,
0.007049465086311102,
-0.04945647343993187,
0.031146535649895668,
-0.06693403422832489,
0.02082258276641369,
0.027272388339042664,
-0.0020435641054064035,
-0.022892359644174576,
-0.011834573931992054,
0.0... | 0.181601 |
This message occurs when an `EnvoyFilter` uses the `ADD` operation and `ApplyTo` is set to `ROUTE\_CONFIGURATION` or `HTTP\_ROUTE`. This will cause the `ADD` operation to be ignored. At the moment only the `MERGE` operation can be used for `ROUTE\_CONFIGURATION`. ## An example Consider an `EnvoyFilter` with the patch o... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0153/index.md | master | istio | [
-0.02256619557738304,
0.02063317969441414,
0.0040492042899131775,
0.0555635429918766,
-0.03253237158060074,
-0.05093787610530853,
0.05336426943540573,
-0.04113113507628441,
-0.03502463921904564,
0.02223193645477295,
0.030117880553007126,
-0.08435271680355072,
-0.025521401315927505,
0.03714... | 0.237713 |
This message occurs when a gateway (usually `istio-ingressgateway`) offers a port that the Kubernetes service workload selected by the gateway does not. For example, your Istio configuration contains these values: {{< text yaml >}} # Gateway with bogus ports apiVersion: networking.istio.io/v1 kind: Gateway metadata: na... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0162/index.md | master | istio | [
-0.0005780772771686316,
0.0500887893140316,
0.022882938385009766,
0.005940374452620745,
-0.031215615570545197,
-0.03894713521003723,
0.051825426518917084,
-0.017263172194361687,
0.07088395953178406,
0.03593647852540016,
-0.043718092143535614,
-0.09779202193021774,
-0.05163901671767235,
0.0... | 0.493959 |
This message occurs when an `annotation` mentions `istio.io` but the annotation - isn't an annotation known to this version of Istio - is known, but has a disallowed value, such as a string where a number is needed - is applied to the wrong kind of resource, such as a pod-specific resource applied to a service Consult ... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0125/index.md | master | istio | [
-0.02430741861462593,
0.04448802396655083,
0.007577693089842796,
0.036308322101831436,
0.05726888030767441,
-0.011628828942775726,
0.08164264261722565,
0.005183801986277103,
0.049254901707172394,
-0.005610580090433359,
-0.040044769644737244,
-0.13159072399139404,
-0.027364341542124748,
0.0... | 0.536316 |
This message occurs when a namespace specifies Istio sidecar auto-injection using \*\*both\*\* the new and legacy style labels. ## Example You will receive this message: {{< text plain >}} Warning [IST0123] (Namespace busted) The namespace has both new and legacy injection labels. Run 'kubectl label namespace busted is... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0123/index.md | master | istio | [
0.016997506842017174,
0.04157998785376549,
0.038182634860277176,
0.04030078276991844,
-0.028979633003473282,
0.004904318135231733,
0.01997685246169567,
-0.027138715609908104,
0.006462560500949621,
-0.048233725130558014,
0.035768453031778336,
-0.12038499116897583,
-0.021232251077890396,
-0.... | 0.447294 |
This message occurs when the namespace is enabled for automatic sidecar injection, but some pods in the namespace are not having the correct sidecar injected. If any of the pods in the namespace are not running the correct sidecar version, this message will be reported. The names of the pods are listed in the message d... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0158/index.md | master | istio | [
0.02256377972662449,
0.00042964963358826935,
0.07667867094278336,
0.03544112667441368,
-0.036438118666410446,
-0.013571348041296005,
0.00099341687746346,
-0.02027004212141037,
0.015159351751208305,
0.039665933698415756,
0.035554759204387665,
-0.09279205650091171,
-0.05637194961309433,
0.01... | 0.31717 |
This message occurs when a policy applied in your Istio service mesh has no impact. This might be due to the policy's configuration incorrectly targeting any workloads or namespaces in your service mesh. ## Example You will receive a message like this: {{< text plain >}} Warning [IST0167] (Sidecar ns-ambient/namespace-... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0167/index.md | master | istio | [
0.01269062701612711,
0.0432024784386158,
0.06377691775560379,
0.10477680712938309,
0.08093588799238205,
-0.05625579506158829,
0.0625348687171936,
-0.02974708005785942,
-0.02533360756933689,
0.030341140925884247,
0.060033850371837616,
-0.08742664009332657,
-0.05404522642493248,
0.0568282008... | 0.335051 |
The `MultipleTelemetriesWithoutWorkloadSelectors` message occurs when there are multiple Telemetry resources in the same namespace that do not define any workload selector. Without workload selectors, these Telemetry resources apply to all workloads in the namespace by default. Having multiple such resources can lead t... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0160/index.md | master | istio | [
0.007373101077973843,
-0.018582573160529137,
0.05642234906554222,
-0.010228186845779419,
-0.015444405376911163,
-0.11578509956598282,
0.03885723277926445,
-0.11479698866605759,
0.06460560113191605,
0.02158680558204651,
-0.030129900202155113,
-0.0826365128159523,
-0.044611766934394836,
-0.0... | 0.104309 |
This message occurs when an `EnvoyFilter` does not have a priority and uses a relative patch operation (`INVALID`, `MERGE`, `REMOVE`, `INSERT\_BEFORE`, `INSERT\_AFTER`, `REPLACE`). Using a relative patch operation means that the operation depends on another filter being there when the current `EnvoyFilter` filter is ev... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0151/index.md | master | istio | [
-0.05574590340256691,
-0.0016340984730049968,
0.06172573193907738,
0.023786379024386406,
0.0009267383720725775,
-0.05967431142926216,
0.03094734624028206,
-0.008244804106652737,
0.020644836127758026,
0.047475192695856094,
0.04103356599807739,
-0.04241204261779785,
-0.03632670268416405,
0.0... | 0.196564 |
This message occurs when a namespace is missing either the `istio-injection` label, which enables/disables sidecar injection, or the `istio.io/rev` label, which specifies the Istio control plane revision for the sidecar, or when `.values.sidecarInjectorWebhook.enableNamespacesByDefault` is not enabled. For example, you... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0102/index.md | master | istio | [
0.002498744986951351,
0.048006247729063034,
0.011965665966272354,
0.07929708063602448,
-0.056029438972473145,
0.01855781115591526,
0.015265100635588169,
-0.005166754592210054,
-0.02269100956618786,
-0.015970442444086075,
0.027409471571445465,
-0.14813187718391418,
-0.05452834814786911,
-0.... | 0.391106 |
This message occurs when a `ServiceEntry` with the `protocol` field not set, or set to `TCP`, doesn't have `addresses` defined. ## Example You will receive this message: {{< text plain >}} Warning [IST0134] (ServiceEntry service-entry.default serviceentry.yaml:13) ServiceEntry addresses are required for this protocol. ... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0134/index.md | master | istio | [
-0.01702309213578701,
0.030309375375509262,
-0.01641005463898182,
0.05306297540664673,
0.04192456230521202,
-0.03415701165795326,
0.012505638413131237,
-0.023698819801211357,
0.02697901986539364,
0.006873148027807474,
-0.01529701054096222,
-0.11819195747375488,
0.019861510023474693,
0.0990... | 0.437672 |
This message occurs for services of type ExternalName when the port doesn't follow Istio service port naming convention, the port is unnamed or the port is named tcp. ## Example You will receive this message: {{< text plain >}} Warning [IST0150] (Service nginx.default) Port name for ExternalName service is invalid. Pro... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0150/index.md | master | istio | [
-0.06423315405845642,
0.024629749357700348,
0.016439421102404594,
-0.014140552841126919,
-0.050033677369356155,
-0.005770768970251083,
0.035290054976940155,
-0.01505933329463005,
0.014282704330980778,
0.011752880178391933,
-0.05889210104942322,
-0.06459631770849228,
0.01537401508539915,
0.... | 0.300063 |
The `InvalidGatewayCredential` message occurs when a Gateway resource references a secret for its TLS configuration, but the secret is either not found or contains an invalid TLS certificate. This message helps identify issues with the TLS configuration of a Gateway resource, which may lead to insecure or non-functiona... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0161/index.md | master | istio | [
-0.04406629130244255,
0.037682052701711655,
-0.019658150151371956,
-0.01833592914044857,
-0.10192044824361801,
-0.02946535311639309,
0.025382449850440025,
-0.04313233867287636,
0.14107629656791687,
0.00242088595405221,
-0.047046925872564316,
-0.10066544264554977,
0.05207427218556404,
0.037... | 0.011971 |
The `ConflictingTelemetryWorkloadSelectors` message occurs when multiple Telemetry resources in the same namespace have overlapping workload selectors, causing ambiguity in determining which Telemetry resource should be applied to a specific pod. This can lead to unintended telemetry configuration for the affected work... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0159/index.md | master | istio | [
0.017362212762236595,
-0.009934626519680023,
0.08138913661241531,
0.005188560113310814,
-0.02411515638232231,
-0.12003020197153091,
0.06161750108003616,
-0.103939950466156,
0.062217891216278076,
0.020795075222849846,
-0.015270179137587547,
-0.0726601704955101,
-0.048925064504146576,
-0.007... | 0.082876 |
This message occurs when a workload selector in policies like `AuthorizationPolicy`, `RequestAuthentication`, `Telemetry`, or `WasmPlugin` does not effectively target any pods within the Kubernetes Gateway. ## Example You will receive similar messages like: {{< text plain >}} Warning [IST0166] (AuthorizationPolicy defa... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0166/index.md | master | istio | [
0.03773431107401848,
0.07511042803525925,
0.04332198202610016,
0.0017577896360307932,
-0.015543085522949696,
-0.041288185864686966,
0.0691206306219101,
-0.03516995534300804,
0.07625429332256317,
0.07262907177209854,
-0.03574037179350853,
-0.08030186593532562,
-0.002794047351926565,
0.01585... | 0.249269 |
This message occurs when a `host` defined in a virtual service is not found in the corresponding gateway. ## Example You will receive this message: {{< text plain >}} Warning [IST0132] (VirtualService testing-service.default testing.yaml:8) one or more host [wrong.com] defined in VirtualService default/testing-service ... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0132/index.md | master | istio | [
0.008622268214821815,
0.011818484403192997,
-0.03572696074843407,
0.0486348494887352,
-0.005191473290324211,
-0.032616350799798965,
0.0007387684308923781,
0.0064796037040650845,
0.019292758777737617,
0.015657082200050354,
-0.0042034899815917015,
-0.10671240836381912,
-0.029445623978972435,
... | 0.509731 |
This message occurs when no `caCertificates` are set in a destination rule, but they are needed for the traffic policy. ## Example You will receive this message: {{< text plain >}} Error [IST0128] (DestinationRule db-tls.default) DestinationRule default/db-tls in namespace default has TLS mode set to SIMPLE but no caCe... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0128/index.md | master | istio | [
0.02985771931707859,
0.008294348604977131,
-0.039076969027519226,
0.025855323299765587,
-0.017036644741892815,
-0.03189058601856232,
0.08973222970962524,
0.00592462532222271,
0.050967343151569366,
0.039201002568006516,
-0.021344492211937904,
-0.13896490633487701,
0.06347706913948059,
0.115... | 0.2171 |
This message occurs when a workload is running as User ID (UID) `1337`. Application pods should not run as user ID (UID) `1337` because the istio-proxy container runs as UID `1337`. Running your application containers using the same UID would result in conflicts with its `iptables` configurations. {{< warning >}} User ... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0144/index.md | master | istio | [
0.03841255605220795,
0.044140592217445374,
0.02173091098666191,
-0.015535067766904831,
-0.0339696928858757,
-0.05784217640757561,
0.03711392357945442,
0.04483099654316902,
-0.03664889559149742,
0.00614016130566597,
-0.018193015828728676,
-0.0899539664387703,
-0.0349452905356884,
0.03150584... | 0.36358 |
This message occurs when a workload is listening on a `localhost` network interface, but the port is exposed in the Service. When this occurs, the port will not be accessible to other pods. This check is primarily added to detect workloads on older Istio versions that may break when upgrading to Istio 1.10 or later. Th... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0143/index.md | master | istio | [
0.01545742154121399,
0.0700136125087738,
0.04932189732789993,
0.023133710026741028,
0.029221568256616592,
-0.052560046315193176,
0.023634804412722588,
-0.00752706965431571,
0.04755863547325134,
0.038907431066036224,
-0.024225443601608276,
-0.09451721608638763,
-0.05903288349509239,
0.05217... | 0.49268 |
This message occurs when `caCertificates` is not set in a destination rule, but is needed for the traffic policy. ## Example You will receive this message: {{< text plain >}} Error [IST0129] (DestinationRule db-tls.default) DestinationRule default/db-tls in namespace default has TLS mode set to SIMPLE but no caCertific... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0129/index.md | master | istio | [
0.035811204463243484,
0.008148031309247017,
-0.039824195206165314,
0.023822154849767685,
-0.023638632148504257,
-0.03921626880764961,
0.0565355084836483,
0.00021647104586008936,
0.05135852098464966,
0.04001615568995476,
-0.012307566590607166,
-0.14123104512691498,
0.056389324367046356,
0.1... | 0.216635 |
This message occurs when pods of a deployment are associated with multiple services using the same port but different protocols. ## An example Consider an Istio mesh with the following services: {{< text yaml >}} apiVersion: v1 kind: Service metadata: name: productpage-tcp-v1 spec: ports: - port: 9080 name: tcp protoco... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0116/index.md | master | istio | [
0.0008388641872443259,
0.034560538828372955,
0.0317954383790493,
-0.06446417421102524,
-0.01802152767777443,
-0.05325851961970329,
0.0197089072316885,
-0.04766198620200157,
0.043853625655174255,
0.009932797402143478,
0.020891768857836723,
-0.06209627538919449,
-0.009195446968078613,
0.0717... | 0.310505 |
This message occurs when the port doesn't follow the [Istio service port naming convention](/docs/ops/configuration/traffic-management/protocol-selection/) or the port is unnamed. ## Example You will receive this message: {{< text plain >}} Info [IST0118] (Service httpbin.default) Port name foo-http (port: 80, targetPo... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0118/index.md | master | istio | [
0.00006379089609254152,
0.025757918134331703,
-0.011658711358904839,
-0.00534998020157218,
-0.039641138166189194,
-0.03456465154886246,
0.03197551518678665,
-0.005928180180490017,
0.0034638657234609127,
0.029778022319078445,
-0.009165850467979908,
-0.08927799761295319,
-0.023949451744556427,... | 0.361648 |
This message occurs when an authorization policy's selector does not match any pods. ## Example You will receive this message: {{< text plain >}} Warning [IST0127] (AuthorizationPolicy httpbin-nopods.httpbin) No matching workloads for this resource with the following labels: app=bogus-label,version=v1 {{< /text >}} whe... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/analysis/ist0127/index.md | master | istio | [
0.018867358565330505,
0.06730968505144119,
0.0036078656557947397,
0.04123362898826599,
0.028475739061832428,
-0.022155044600367546,
0.03903157263994217,
-0.060304418206214905,
0.052303582429885864,
0.037033531814813614,
-0.004586418159306049,
-0.08966854959726334,
-0.019614381715655327,
0.... | 0.30898 |
This page describes all the supported normalizations in the authorization policy. The normalized request will be used for both the evaluation of authorization policies and the request that is ultimately sent to the backend server. For more information, please refer to [authorization normalization best practices](/docs/... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/security/normalization/index.md | master | istio | [
0.006012121681123972,
-0.016276516020298004,
-0.05961773917078972,
0.010627471841871738,
-0.07310070842504501,
-0.03835700452327728,
0.020900355651974678,
0.03631389141082764,
-0.0278756283223629,
-0.01380785834044218,
0.02336292900145054,
-0.010468445718288422,
0.024948084726929665,
0.078... | 0.342049 |
Header name related This applies to the header name specified in the `request.headers[]` condition. ### 1. Case-insensitive matching Istio authorization policy will compare the header name with a case-insensitive approach. This is enabled by default. ### 2. Duplicate headers Istio will merge duplicate headers to a sing... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/security/normalization/index.md | master | istio | [
-0.05560816451907158,
0.09841868281364441,
0.003439676482230425,
-0.03349471837282181,
-0.015278460457921028,
-0.032547228038311005,
0.05488061532378197,
0.053857605904340744,
0.0065824599005281925,
-0.02602916583418846,
-0.029865339398384094,
-0.11695316433906555,
0.07218395918607712,
0.0... | 0.401369 |
This page describes the supported keys and value formats you can use as conditions in the `when` field of an [authorization policy rule](/docs/reference/config/security/authorization-policy/#Rule). For more information, refer to the [authorization concept page](/docs/concepts/security/#authorization). ## Supported Cond... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/security/conditions/index.md | master | istio | [
-0.061363328248262405,
0.08193446695804596,
-0.0991785004734993,
-0.03534276410937309,
-0.02750948816537857,
-0.04391658306121826,
0.08191444724798203,
-0.019628819078207016,
-0.010967301204800606,
-0.030677897855639458,
-0.03722945600748062,
-0.03459515795111656,
0.09404923021793365,
0.06... | 0.030003 |
{{< warning >}} This feature is in the Alpha stage, see [Istio Feature Status](/docs/releases/feature-stages/). Your feedback is welcome in the [Istio User Experience discussion](https://discuss.istio.io/c/UX/23). Currently, this feature is tested only for single, low volume clusters with a single control plane revisio... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/config/config-status/index.md | master | istio | [
0.028214382007718086,
0.009824627079069614,
-0.04493512585759163,
0.1000441461801529,
0.045899346470832825,
-0.016984282061457634,
0.044875115156173706,
0.034177325665950775,
-0.02641376480460167,
0.02928919903934002,
-0.023044995963573456,
-0.10621020197868347,
-0.017464622855186462,
0.01... | 0.597127 |
Within a multicluster mesh, [namespace sameness](https://github.com/kubernetes/community/blob/master/sig-multicluster/namespace-sameness-position-statement.md) applies and all namespaces with a given name are considered to be the same namespace. If multiple clusters contain a `Service` with the same namespaced name, th... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/glossary/namespace-sameness.md | master | istio | [
-0.03490935266017914,
-0.05771681293845177,
0.04361146315932274,
-0.09854939579963684,
-0.03521677851676941,
-0.038487162441015244,
0.0050908890552818775,
-0.063787542283535,
0.10996547341346741,
-0.016664914786815643,
-0.030064476653933525,
-0.04790516197681427,
0.02733210101723671,
0.019... | 0.126694 |
The [Container Network Interface (CNI)](https://www.cni.dev/) is the standard used by Kubernetes for configuring cluster networking. It is implemented using \*plugins\*, of which there are two types: \* \*interface\* plugins, which create a network interface, and are provided by the cluster operator \* \*chained\* plug... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/glossary/cni.md | master | istio | [
-0.01938798651099205,
0.027885766699910164,
0.02422155626118183,
0.02639012038707733,
-0.00596937071532011,
0.00491194985806942,
0.0074816616252064705,
0.00012283609248697758,
0.0021394246723502874,
0.001113999867811799,
-0.020196788012981415,
-0.10411273688077927,
-0.03144833818078041,
-0... | 0.441834 |
Istio maintains an internal service registry containing the set of [services](/docs/reference/glossary/#service), and their corresponding [service endpoints](/docs/reference/glossary/#service-endpoint), running in a service mesh. Istio uses the service registry to generate [Envoy](/docs/reference/glossary/#envoy) confi... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/glossary/service-registry.md | master | istio | [
-0.09079819917678833,
-0.0883067399263382,
-0.01594933122396469,
-0.04971345514059067,
-0.08982185274362564,
-0.03681535646319389,
0.04829982668161392,
0.013713871128857136,
0.04481348395347595,
-0.004232653882354498,
-0.06525234878063202,
-0.06923728436231613,
-0.037433650344610214,
0.054... | 0.570781 |
Identity is a fundamental security infrastructure concept. The Istio identity model is based on a first-class workload identity. At the beginning of service-to-service communication, the two parties exchange credentials with their identity information for mutual authentication purposes. Clients check the server’s ident... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/glossary/identity.md | master | istio | [
-0.09367474168539047,
0.03360311686992645,
-0.01872927136719227,
-0.038332629948854446,
0.010716679506003857,
-0.01960633136332035,
0.1437542587518692,
0.011084169149398804,
0.11270059645175934,
-0.0033444722648710012,
-0.03809317946434021,
-0.08089741319417953,
0.029251400381326675,
0.035... | 0.570572 |
A single instantiation of a [workload's](/docs/reference/glossary/#workload) binary. A workload instance can expose zero or more [service endpoints](/docs/reference/glossary/#service-endpoint), and can consume zero or more [services](/docs/reference/glossary/#service). Workload instances have a number of properties: - ... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/glossary/workload-instance.md | master | istio | [
-0.07972052693367004,
-0.00686861015856266,
-0.017285415902733803,
-0.0206917691975832,
-0.10130680352449417,
-0.037486203014850616,
0.10642388463020325,
-0.026771992444992065,
0.012180950492620468,
0.006115572527050972,
0.005066041834652424,
-0.0711502656340599,
0.017424046993255615,
0.02... | 0.362495 |
Attributes control the runtime behavior of services running in the mesh. Attributes are named and typed pieces of metadata describing ingress and egress traffic and the environment this traffic occurs in. An Istio attribute carries a specific piece of information such as the error code of an API request, the latency of... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/glossary/attribute.md | master | istio | [
-0.035233743488788605,
0.07312524318695068,
0.006832239218056202,
0.06490770727396011,
0.01773371361196041,
-0.06574123352766037,
0.0840953141450882,
0.02720499411225319,
0.054476428776979446,
0.01108046155422926,
-0.025968847796320915,
-0.08077573031187057,
-0.011242400854825974,
0.033353... | 0.630061 |
A \*service mesh\* or simply \*mesh\* is an infrastructure layer that enables managed, observable and secure communication between [workload instances](/docs/reference/glossary/#workload-instance). Service names combined with a namespace are unique within a mesh. In a [multicluster](/docs/reference/glossary/#multiclust... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/glossary/service-mesh.md | master | istio | [
-0.13069725036621094,
-0.018687352538108826,
0.005982592701911926,
-0.043809011578559875,
-0.05418819561600685,
-0.031952984631061554,
0.07374607771635056,
-0.07397940754890442,
0.08463423699140549,
-0.014528218656778336,
-0.0222476776689291,
-0.06878075003623962,
0.06449873000383377,
0.04... | 0.142427 |
A binary deployed by [operators](/docs/reference/glossary/#operator) to deliver some function of a service mesh application. Workloads have names, namespaces, and unique ids. These properties are available in policy and telemetry configuration using the following [attributes](/docs/reference/glossary/#attribute): \* `s... | https://github.com/istio/istio.io/blob/master//content/en/docs/reference/glossary/workload.md | master | istio | [
-0.054662711918354034,
0.0033675970043987036,
0.04927336052060127,
-0.04092993587255478,
-0.0914885625243187,
-0.06881792098283768,
0.06374648213386536,
-0.04715748503804207,
0.08704353123903275,
0.044598113745450974,
-0.012105683796107769,
-0.03614841774106026,
0.003515370888635516,
0.003... | 0.179657 |
.. \_installation-instructions: ======================= Installing scikit-learn ======================= There are different ways to install scikit-learn: \* :ref:`Install the latest official release `. This is the best approach for most users. It will provide a stable version and pre-built packages are available for mo... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/install.rst | main | scikit-learn | [
-0.004450819920748472,
-0.03628301993012428,
0.04004160687327385,
0.0024919549468904734,
0.09759894758462906,
-0.08500873297452927,
-0.06312701106071472,
0.0038230568170547485,
-0.0841282457113266,
0.01981443166732788,
0.03421479091048241,
-0.03247934952378273,
-0.10044385492801666,
-0.021... | 0.06094 |
in order to avoid potential conflicts with other packages. .. prompt:: bash python3 -m venv sklearn-env source sklearn-env/bin/activate # activate pip3 install -U scikit-learn In order to check your installation, you can use: .. prompt:: bash python3 -m pip show scikit-learn # show scikit-learn version and location pyt... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/install.rst | main | scikit-learn | [
0.04797704145312309,
-0.12202075123786926,
-0.03579750657081604,
-0.08044087141752243,
0.12946400046348572,
-0.05076808109879494,
-0.002505863318219781,
-0.02656516246497631,
-0.013604407198727131,
-0.006186380982398987,
0.006159414071589708,
-0.0055640391074121,
-0.06280148029327393,
0.02... | -0.00394 |
Mac OSX -------------------- The MacPorts package is named ``py-scikit-learn``, where ``XY`` denotes the Python version. It can be installed by typing the following command: .. prompt:: bash sudo port install py312-scikit-learn Anaconda and Enthought Deployment Manager for all supported platforms ----------------------... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/install.rst | main | scikit-learn | [
-0.003413752419874072,
-0.07037581503391266,
-0.02805028297007084,
-0.036282893270254135,
0.06708464026451111,
-0.057157885283231735,
-0.006898898631334305,
-0.014574266038835049,
-0.08487394452095032,
0.0196091141551733,
0.06666933745145798,
-0.05489025264978409,
-0.019155031070113182,
0.... | 0.169117 |
Getting Started =============== ``Scikit-learn`` is an open source machine learning library that supports supervised and unsupervised learning. It also provides various tools for model fitting, data preprocessing, model selection, model evaluation, and many other utilities. The purpose of this guide is to illustrate so... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/getting_started.rst | main | scikit-learn | [
-0.08124909549951553,
-0.09206970781087875,
-0.001274753361940384,
0.05981488153338432,
0.1363014429807663,
-0.06889517605304718,
-0.06086309254169464,
-0.023649396374821663,
-0.09335336089134216,
-0.0057891360484063625,
0.007526031695306301,
-0.06240488216280937,
-0.019995277747511864,
-0... | 0.184162 |
we :ref:`load the Iris dataset `, split it into train and test sets, and compute the accuracy score of a pipeline on the test data:: >>> from sklearn.preprocessing import StandardScaler >>> from sklearn.linear\_model import LogisticRegression >>> from sklearn.pipeline import make\_pipeline >>> from sklearn.datasets imp... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/getting_started.rst | main | scikit-learn | [
-0.028502527624368668,
-0.0686698779463768,
-0.028675591573119164,
0.03161947429180145,
-0.028957851231098175,
-0.10748940706253052,
-0.012637786567211151,
0.06230989098548889,
-0.11739201843738556,
-0.011355645023286343,
-0.0006148403626866639,
-0.09665868431329727,
-0.027132904157042503,
... | 0.053944 |
like a normal random forest estimator >>> # with max\_depth=9 and n\_estimators=4 >>> search.score(X\_test, y\_test) 0.84... .. note:: In practice, you almost always want to :ref:`search over a pipeline `, instead of a single estimator. One of the main reasons is that if you apply a pre-processing step to the whole dat... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/getting_started.rst | main | scikit-learn | [
-0.03175465762615204,
-0.08033724129199982,
0.03765436261892319,
0.048821669071912766,
0.08957361429929733,
-0.024098314344882965,
-0.057943183928728104,
0.0341954305768013,
-0.057865507900714874,
-0.03870035707950592,
-0.10397598147392273,
-0.0838465765118599,
-0.03766537457704544,
-0.072... | -0.011266 |
.. |ss| raw:: html .. |se| raw:: html .. \_roadmap: Roadmap ======= Purpose of this document ------------------------ This document lists general directions that core contributors are interested to see developed in scikit-learn. The fact that an item is listed here is in no way a promise that it will happen, as resourc... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/roadmap.rst | main | scikit-learn | [
-0.09299852699041367,
-0.01393512636423111,
-0.004404118284583092,
0.02877749502658844,
0.10588689893484116,
-0.08955138921737671,
-0.07483313232660294,
-0.004461902193725109,
-0.09224811941385269,
-0.010509776882827282,
-0.02693112939596176,
0.0026542472187429667,
-0.04544748365879059,
-0... | 0.171289 |
should also not need to be provided to estimator constructors, ideally, but should be available as metadata alongside X. :issue:`8480` #. Passing around information that is not (X, y): Target information \* We have problems getting the full set of classes to all components when the data is split/sampled. :issue:`6231` ... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/roadmap.rst | main | scikit-learn | [
-0.006787879392504692,
-0.0553448311984539,
0.02499144896864891,
-0.0026952943298965693,
0.11234261840581894,
-0.07152662426233292,
-0.0176224522292614,
0.01968218944966793,
-0.10514594614505768,
-0.0168314129114151,
-0.03494737297296524,
-0.08795887976884842,
-0.05496663972735405,
-0.0251... | 0.060161 |
to our API contract. We are still in the process of making decisions on some of these related issues. \* `Pipeline ` and `FeatureUnion` modify their input parameters in fit. Fixing this requires making sure we have a good grasp of their use cases to make sure all current functionality is maintained. :issue:`8157` :issu... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/roadmap.rst | main | scikit-learn | [
-0.11430200189352036,
-0.04042445123195648,
0.02210438996553421,
0.0301545187830925,
0.03829333186149597,
-0.09798908233642578,
-0.1250237226486206,
0.03237026929855347,
-0.12766548991203308,
-0.0534541979432106,
-0.03319502994418144,
-0.0235299002379179,
-0.01765573024749756,
-0.005485422... | 0.083576 |
:html\_theme.sidebar\_secondary.remove: .. \_ml\_map: Choosing the right estimator ============================ Often the hardest part of solving a machine learning problem can be finding the right estimator for the job. Different estimators are better suited for different types of data and different problems. The flow... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/machine_learning_map.rst | main | scikit-learn | [
-0.019667141139507294,
-0.021678734570741653,
0.0630563274025917,
0.018360676243901253,
0.09982932358980179,
0.0019614561460912228,
-0.029263371601700783,
-0.08841179311275482,
0.009181112982332706,
-0.00936861988157034,
-0.01650037243962288,
0.01284731924533844,
-0.007816742174327374,
-0.... | -0.014588 |
.. \_inspection: Inspection ---------- Predictive performance is often the main goal of developing machine learning models. Yet summarizing performance with an evaluation metric is often insufficient: it assumes that the evaluation metric and test dataset perfectly reflect the target domain, which is rarely true. In ce... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/inspection.rst | main | scikit-learn | [
-0.07470154017210007,
-0.0468795970082283,
-0.04694116860628128,
-0.005994841456413269,
0.11137920618057251,
-0.048900797963142395,
0.022891324013471603,
-0.013578825630247593,
-0.08420884609222412,
-0.008096390403807163,
-0.015540874563157558,
-0.0018943678587675095,
0.0027743540704250336,
... | 0.146703 |
======= Support ======= There are several channels to connect with scikit-learn developers for assistance, feedback, or contributions. \*\*Note\*\*: Communications on all channels should respect our `Code of Conduct `\_. .. \_announcements\_and\_notification: Mailing Lists ============= - \*\*Main Mailing List\*\*: Joi... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/support.rst | main | scikit-learn | [
-0.055436234921216965,
-0.06771151721477509,
0.009353474713861942,
0.025536393746733665,
0.10436301678419113,
-0.10899548977613449,
0.0744689553976059,
-0.009601171128451824,
-0.04572732374072075,
-0.008065210655331612,
-0.04613863676786423,
-0.07458867877721786,
-0.058129578828811646,
-0.... | 0.187872 |
.. \_model\_persistence: ================= Model persistence ================= .. list-table:: Summary of model persistence methods :widths: 25 50 50 :header-rows: 1 \* - Persistence method - Pros - Risks / Cons \* - :ref:`ONNX ` - \* Serve models without a Python environment \* Serving and training environments indepe... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/model_persistence.rst | main | scikit-learn | [
-0.07725288718938828,
-0.04291326552629471,
-0.0996401235461235,
0.07551393657922745,
0.07326869666576385,
-0.030218692496418953,
-0.040374793112277985,
0.004145532846450806,
-0.03820377215743065,
-0.013366805389523506,
-0.02115763910114765,
-0.025713618844747543,
0.020232519134879112,
0.0... | 0.126527 |
Did you try :mod:`pickle` or :mod:`joblib` and found that the model cannot be persisted? It can happen for instance when you have user defined functions in your model. If yes, then you can use `cloudpickle`\_ which can serialize certain objects which cannot be serialized by :mod:`pickle` or :mod:`joblib`. Workflow Over... | https://github.com/scikit-learn/scikit-learn/blob/main//doc/model_persistence.rst | main | scikit-learn | [
-0.11142435669898987,
-0.09005103260278702,
-0.051063016057014465,
0.025238731876015663,
0.07092524319887161,
-0.01883385330438614,
-0.041560281068086624,
-0.02906729280948639,
-0.021929942071437836,
-0.028857111930847168,
-0.02805541642010212,
-0.032488152384757996,
0.012552506290376186,
... | 0.08756 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.