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 |
|---|---|---|---|---|---|
# Monitoring The Argo CD Notification controller serves Prometheus metrics on port 9001. > [!NOTE] > The metrics port can be changed using the `--metrics-port` flag in `argocd-notifications-controller` deployment. ## Metrics The following metrics are available: ### `argocd\_notifications\_deliveries\_total` Number of d... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/monitoring.md | master | argo-cd | [
-0.041671037673950195,
0.00023268169024959207,
-0.132416769862175,
-0.0021982586476951838,
-0.024550899863243103,
-0.06929150968790054,
0.05328388884663582,
-0.011830349452793598,
-0.008485859259963036,
0.06893062591552734,
0.009343636222183704,
-0.08722706139087677,
0.01019690465182066,
0... | 0.137309 |
The subscription to Argo CD application events can be defined using `notifications.argoproj.io/subscribe..: ` annotation. For example, the following annotation subscribes two Slack channels to notifications about every successful synchronization of the Argo CD application: ```yaml apiVersion: argoproj.io/v1alpha1 kind:... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/subscriptions.md | master | argo-cd | [
-0.01623781956732273,
-0.07671436667442322,
-0.03496844694018364,
-0.011634871363639832,
-0.005398387089371681,
-0.015827761963009834,
0.10704355686903,
0.001450982759706676,
0.015092487446963787,
0.08175399154424667,
-0.032693129032850266,
-0.044537387788295746,
0.010166971012949944,
0.01... | 0.169086 |
# Email ## Parameters The Email notification service sends email notifications using SMTP protocol and requires specifying the following settings: \* `host` - the SMTP server host name \* `port` - the SMTP server port \* `username` - username \* `password` - password \* `from` - from email address \* `html` - optional ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/email.md | master | argo-cd | [
-0.0705619603395462,
-0.06827214360237122,
0.06983786821365356,
-0.05030330643057823,
0.006611155346035957,
-0.03533569350838661,
0.05032023787498474,
-0.03293779119849205,
0.018761126324534416,
0.05818624049425125,
0.006218740250915289,
-0.07075528800487518,
0.08073801547288895,
0.0258613... | -0.020955 |
# Webex Teams ## Parameters The Webex Teams notification service configuration includes following settings: \* `token` - the app token ## Configuration 1. Create a Webex [Bot](https://developer.webex.com/docs/bots) 1. Copy the bot access [token](https://developer.webex.com/my-apps) and store it in the `argocd-notificat... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/webex.md | master | argo-cd | [
-0.051081351935863495,
-0.06689048558473587,
-0.0422540083527565,
0.029790334403514862,
0.05168645456433296,
-0.0405162051320076,
0.10460303723812103,
-0.05240713804960251,
0.02789999172091484,
0.004533344879746437,
-0.005096889100968838,
-0.10830891132354736,
0.037229202687740326,
0.03008... | 0.196098 |
The notification services represent integration with services such as slack, email or custom webhook. Services are configured in `argocd-notifications-cm` ConfigMap using `service..()` keys and might reference sensitive data from `argocd-notifications-secret` Secret. Following example demonstrates slack service configu... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/overview.md | master | argo-cd | [
-0.06980178505182266,
-0.04644371196627617,
-0.07380881905555725,
0.006649813614785671,
0.01748991198837757,
-0.05276953801512718,
0.11681374907493591,
-0.009910598397254944,
0.055872514843940735,
0.05992232263088226,
0.025037964805960655,
-0.027047473937273026,
0.06253658980131149,
0.0159... | 0.180867 |
# Slack If you want to send message using incoming webhook, you can use [webhook](./webhook.md#send-slack). ## Parameters The Slack notification service configuration includes following settings: | \*\*Option\*\* | \*\*Required\*\* | \*\*Type\*\* | \*\*Description\*\* | \*\*Example\*\* | | -------------------- | ------... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/slack.md | master | argo-cd | [
-0.022934479638934135,
-0.01615622267127037,
-0.025771066546440125,
0.00879876408725977,
-0.014938555657863617,
-0.06523676961660385,
0.01821686141192913,
0.006505222991108894,
0.011361904442310333,
0.031196998432278633,
-0.0345412939786911,
-0.11385461688041687,
0.05498696491122246,
0.037... | 0.098896 |
username for each message, you can specify values for `username` and `icon` in the `slack` field. For icon you can specify emoji and image URL, just like in the service definition. If you set `username` and `icon` in template, the values set in template will be used even if values are specified in the service definitio... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/slack.md | master | argo-cd | [
-0.00396682508289814,
0.042801495641469955,
0.021492861211299896,
0.019685151055455208,
-0.00011628807988017797,
-0.03175022080540657,
0.05844573304057121,
0.014844904653728008,
0.016925226897001266,
0.009305763989686966,
0.003918053582310677,
-0.03079158067703247,
0.004673853516578674,
0.... | 0.049539 |
# Rocket.Chat ## Parameters The Rocket.Chat notification service configuration includes following settings: \* `email` - the Rocker.Chat user's SAMAccountName \* `password` - the Rocker.Chat user's password \* `alias` - optional alias that should be used to post message \* `icon` - optional message icon \* `avatar` - o... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/rocketchat.md | master | argo-cd | [
-0.011831255629658699,
-0.04327387362718582,
0.06570671498775482,
-0.030489591881632805,
-0.01899917796254158,
-0.0042751021683216095,
0.11478319019079208,
-0.012184304185211658,
0.027178511023521423,
0.04336552321910858,
0.010338598862290382,
-0.043400634080171585,
0.03630499541759491,
0.... | -0.0239 |
# GitHub ## Parameters The GitHub notification service changes commit status using [GitHub Apps](https://docs.github.com/en/developers/apps) and requires specifying the following settings: - `appID` - the app id - `installationID` - the app installation id - `privateKey` - the app private key - `enterpriseBaseURL` - op... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/github.md | master | argo-cd | [
0.0004922609659843147,
-0.07321139425039291,
-0.08239243924617767,
0.0009933959227055311,
0.013503922149538994,
-0.07672546058893204,
0.002824901370331645,
-0.010876072570681572,
0.0387999564409256,
0.08547268807888031,
0.029620667919516563,
-0.001474633696489036,
0.027731984853744507,
-0.... | 0.165241 |
# PagerDuty ## Parameters The PagerDuty notification service is used to create PagerDuty incidents and requires specifying the following settings: \* `pagerdutyToken` - the PagerDuty auth token \* `from` - email address of a valid user associated with the account making the request. \* `serviceID` - The ID of the resou... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/pagerduty.md | master | argo-cd | [
-0.05885841324925423,
-0.02156815305352211,
-0.031158994883298874,
-0.04808319732546806,
0.01289297640323639,
-0.006484036333858967,
0.0449121855199337,
-0.0739436224102974,
0.011205789633095264,
0.02536025457084179,
0.007347503677010536,
0.0053229606710374355,
0.057045549154281616,
0.0376... | 0.078621 |
# Webhook The webhook notification service allows sending a generic HTTP request using the templatized request body and URL. Using Webhook you might trigger a Jenkins job, update GitHub commit status. ## Parameters The Webhook notification service configuration includes following settings: - `url` - the url to send the... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/webhook.md | master | argo-cd | [
-0.07139100134372711,
0.02571147121489048,
-0.04823431372642517,
0.007585341110825539,
-0.0011432114988565445,
-0.1299552023410797,
-0.05094591900706291,
-0.06433147937059402,
0.02184407226741314,
0.030962156131863594,
-0.038833264261484146,
-0.07615537196397781,
0.028623661026358604,
-0.0... | 0.127675 |
kind: ConfigMap metadata: name: argocd-notifications-cm data: service.webhook.jenkins: | url: http:///job//build?token= basicAuth: username: password: type: Opaque ``` ### Send form-data ```yaml apiVersion: v1 kind: ConfigMap metadata: name: argocd-notifications-cm data: service.webhook.form: | url: https://form.exampl... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/webhook.md | master | argo-cd | [
-0.08302662521600723,
0.026596443727612495,
-0.063170425593853,
0.02817508392035961,
0.015448144637048244,
-0.0686567947268486,
0.009794497862458229,
-0.027656763792037964,
-0.023408671841025352,
0.045234717428684235,
-0.003444325178861618,
-0.09392843395471573,
-0.0022491966374218464,
-0.... | 0.14687 |
# Opsgenie To be able to send notifications with argocd-notifications you have to create an [API Integration](https://docs.opsgenie.com/docs/integrations-overview) inside your [Opsgenie Team](https://docs.opsgenie.com/docs/teams). 1. Login to Opsgenie at https://app.opsgenie.com or https://app.eu.opsgenie.com (if you h... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/opsgenie.md | master | argo-cd | [
-0.07171943038702011,
-0.0312191229313612,
-0.07986892014741898,
0.02602269873023033,
0.03744032233953476,
-0.08476358652114868,
0.0401880256831646,
0.0029638458508998156,
0.029247673228383064,
0.013553918339312077,
-0.09383178502321243,
-0.03902428597211838,
-0.016256889328360558,
0.02040... | 0.145557 |
| ```yaml apiVersion: v1 kind: ConfigMap metadata: name: argocd-notifications-cm data: service.opsgenie: | apiUrl: apiKeys: : template.opsgenie: | message: | [Argo CD] Application {{.app.metadata.name}} has a problem. opsgenie: description: | Application: {{.app.metadata.name}} Health Status: {{.app.status.health.statu... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/opsgenie.md | master | argo-cd | [
-0.04260733351111412,
0.0531851127743721,
0.024637237191200256,
0.024717014282941818,
0.004963087383657694,
-0.06670825928449631,
0.03719901293516159,
-0.015327434055507183,
-0.009999933652579784,
0.0752221941947937,
0.015113514848053455,
-0.03432764485478401,
-0.051642682403326035,
0.0215... | 0.105685 |
# PagerDuty V2 ## Parameters The PagerDuty notification service is used to trigger PagerDuty events and requires specifying the following settings: \* `serviceKeys` - a dictionary with the following structure: \* `service-name: $pagerduty-key-service-name` where `service-name` is the name you want to use for the servic... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/pagerduty_v2.md | master | argo-cd | [
-0.04778914526104927,
-0.0629645437002182,
-0.062399476766586304,
-0.038204606622457504,
-0.024153325706720352,
-0.017983948811888695,
0.09403851628303528,
-0.0694609135389328,
0.0056716823019087315,
-0.00826639961451292,
-0.007936511188745499,
-0.024045439437031746,
0.06742274761199951,
0... | 0.073774 |
# AWS SQS ## Parameters This notification service is capable of sending simple messages to AWS SQS queue. \* `queue` - name of the queue you are intending to send messages to. Can be overridden with target destination annotation. \* `region` - region of the sqs queue can be provided via env variable AWS\_DEFAULT\_REGIO... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/awssqs.md | master | argo-cd | [
-0.037820786237716675,
0.012025520205497742,
-0.06677158921957016,
0.024069320410490036,
-0.02143404260277748,
-0.016132472082972527,
0.1117350310087204,
-0.05657405033707619,
0.08835653960704803,
0.0758763924241066,
-0.010714679956436157,
-0.07235187292098999,
0.07558993995189667,
0.02210... | 0.097153 |
# NewRelic ## Parameters \* `apiURL` - the api server url, e.g. https://api.newrelic.com \* `apiKey` - a [NewRelic ApiKey](https://docs.newrelic.com/docs/apis/rest-api-v2/get-started/introduction-new-relic-rest-api-v2/#api\_key) \* `maxIdleConns` - optional, maximum number of idle (keep-alive) connections across all ho... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/newrelic.md | master | argo-cd | [
-0.055471792817115784,
-0.04524393007159233,
-0.04099366441369057,
0.014305894263088703,
-0.06969358026981354,
-0.07800254970788956,
-0.09182955324649811,
-0.0237344428896904,
0.03569938987493515,
0.04617436230182648,
0.020567404106259346,
0.020378049463033676,
0.03455933928489685,
0.02026... | 0.105416 |
# Teams Workflows ## Overview The Teams Workflows notification service sends message notifications using Microsoft Teams Workflows (Power Automate). This is the recommended replacement for the legacy Office 365 Connectors service, which will be retired on March 31, 2026. ## Parameters The Teams Workflows notification s... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/teams-workflows.md | master | argo-cd | [
-0.09235459566116333,
0.060658812522888184,
-0.034034471958875656,
0.00304136099293828,
0.04030265286564827,
-0.05870576575398445,
-0.026021605357527733,
-0.07879074662923813,
0.09110675007104874,
0.00311592617072165,
-0.07843456417322159,
-0.05790029838681221,
0.03616752102971077,
0.05661... | 0.10014 |
"color": "Good" }, { "type": "TextBlock", "text": "Application {{.app.metadata.name}} has been successfully synced at {{.app.status.operationState.finishedAt}}.", "wrap": true }, { "type": "FactSet", "facts": [ { "title": "Sync Status", "value": "{{.app.status.sync.status}}" }, { "title": "Repository", "value": "{{.app... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/teams-workflows.md | master | argo-cd | [
-0.07404901087284088,
0.06354699283838272,
-0.04032084345817566,
0.0784379243850708,
0.00864020548760891,
-0.025998646393418312,
0.04649737477302551,
-0.048708271235227585,
-0.031182795763015747,
0.0179729200899601,
-0.0027942105662077665,
-0.042393408715724945,
-0.03594355285167694,
0.012... | 0.098423 |
the old Office 365 Connector configuration \*\*Note:\*\* Your existing templates will work without modification. The service automatically converts your template fields to Adaptive Card format, so you get the benefits of modern cards without changing your templates. ## Differences from Office 365 Connectors | Feature |... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/teams-workflows.md | master | argo-cd | [
-0.0793435275554657,
0.051594581454992294,
-0.03404390811920166,
-0.0045403060503304005,
0.032989583909511566,
0.056013282388448715,
-0.110073983669281,
-0.05532991513609886,
0.02576177753508091,
-0.05631941929459572,
-0.032324790954589844,
0.02229321375489235,
-0.043146274983882904,
0.025... | 0.093788 |
# Grafana To be able to create Grafana annotation with argocd-notifications you have to create an [API Key](https://grafana.com/docs/grafana/latest/http\_api/auth/#create-api-key) inside your [Grafana](https://grafana.com). . 2. Store token in `` Secret and configure telegram integration in `argocd-notifications-cm` ConfigMap: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: argocd-notifications-cm data: service.telegram: | token: $telegram-token ``` 3. Create ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/telegram.md | master | argo-cd | [
-0.024030525237321854,
-0.08771660923957825,
-0.02016422711312771,
0.0045250775292515755,
-0.01931724138557911,
-0.044440511614084244,
0.04266844317317009,
0.040736328810453415,
-0.00911053828895092,
0.12278551608324051,
-0.016995204612612724,
-0.07239927351474762,
0.018639419227838516,
0.... | 0.123254 |
# Alertmanager ## Parameters The notification service is used to push events to [Alertmanager](https://github.com/prometheus/alertmanager), and the following settings need to be specified: \* `targets` - the alertmanager service address, array type \* `scheme` - optional, default is "http", e.g. http or https \* `apiPa... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/alertmanager.md | master | argo-cd | [
-0.020980099216103554,
0.025150805711746216,
-0.06795960664749146,
0.04628622159361839,
0.060575682669878006,
-0.15403835475444794,
0.043840304017066956,
-0.04528399929404259,
0.08507585525512695,
0.017519338056445122,
0.02242804691195488,
-0.06775470823049545,
0.09367606788873672,
0.05994... | 0.176932 |
# Teams (Office 365 Connectors) ## ⚠️ Deprecation Notice \*\*Office 365 Connectors are being retired by Microsoft.\*\* Microsoft is retiring the Office 365 Connectors service in Teams. The service will be fully retired by \*\*March 31, 2026\*\* (extended from the original timeline of December 2025). ### What this means... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/teams.md | master | argo-cd | [
-0.1109812930226326,
0.062165241688489914,
-0.0226783137768507,
-0.01888175494968891,
0.07196506857872009,
-0.022678308188915253,
-0.08845396339893341,
-0.08670884370803833,
0.02175242453813553,
-0.01075464766472578,
-0.032656725496053696,
-0.0102856969460845,
-0.006116968579590321,
0.0072... | 0.114166 |
"name": "Sync Status", "value": "{{.app.status.sync.status}}" }, { "name": "Repository", "value": "{{.app.spec.source.repoURL}}" }] ``` ### theme color field You can set theme color as hex string for the message.  `... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/teams.md | master | argo-cd | [
0.03233271837234497,
0.07891536504030228,
0.040637195110321045,
0.027148397639393806,
0.08244498074054718,
0.01734357886016369,
0.0615592822432518,
-0.061935558915138245,
0.10396106541156769,
-0.010954764671623707,
-0.041065916419029236,
-0.035101164132356644,
0.010706670582294464,
0.02296... | 0.059996 |
# Google Chat ## Parameters The Google Chat notification service send message notifications to a google chat webhook. This service uses the following settings: \* `webhooks` - a map of the form `webhookName: webhookUrl` ## Configuration 1. Open `Google chat` and go to the space to which you want to send messages 2. Fro... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/googlechat.md | master | argo-cd | [
-0.08743895590305328,
-0.004390026908367872,
-0.014356573112308979,
-0.014018413610756397,
0.03076835349202156,
-0.07710915058851242,
0.046030644327402115,
-0.062290411442518234,
0.015342501923441887,
0.03894003853201866,
0.014370748773217201,
-0.08924353122711182,
0.008240187540650368,
-0... | 0.062049 |
# Mattermost ## Parameters \* `apiURL` - the server url, e.g. https://mattermost.example.com \* `token` - the bot token \* `insecureSkipVerify` - optional bool, true or false \* `maxIdleConns` - optional, maximum number of idle (keep-alive) connections across all hosts. \* `maxIdleConnsPerHost` - optional, maximum numb... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/mattermost.md | master | argo-cd | [
-0.07319727540016174,
-0.042446721345186234,
-0.07576613128185272,
0.04783882945775986,
-0.014198930002748966,
-0.11940871924161911,
0.013518493622541428,
0.01695403642952442,
0.001945788273587823,
0.05222320556640625,
0.014700914733111858,
-0.022214757278561592,
0.08830579370260239,
0.008... | 0.211007 |
# Pushover 1. Create an app at [pushover.net](https://pushover.net/apps/build). 2. Store the API key in `` Secret and define the secret name in `argocd-notifications-cm` ConfigMap: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: argocd-notifications-cm data: service.pushover: | token: $pushover-token ``` ```yaml... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/notifications/services/pushover.md | master | argo-cd | [
-0.03112781047821045,
-0.12366452068090439,
-0.037559542804956436,
0.0032457581255584955,
0.00429193489253521,
-0.0564291775226593,
0.03753639757633209,
0.007918407209217548,
-0.029717762023210526,
0.0909554585814476,
-0.004833380226045847,
-0.01832849346101284,
-0.03819950670003891,
0.000... | 0.063907 |
Oh no! You found a bug? We'd love to hear about it. ## Product bugs Search our [issue database](https://github.com/istio/istio/issues/) to see if we already know about your problem and learn about when we think we can fix it. If you don't find your problem in the database, please open a [new issue](https://github.com/i... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/bugs/index.md | master | istio | [
-0.010827258229255676,
-0.02095053158700466,
0.021880580112338066,
0.070036381483078,
0.008614830672740936,
0.013101320713758469,
0.002619323553517461,
0.013538410887122154,
-0.034040529280900955,
0.039843346923589706,
-0.039301205426454544,
-0.1163395568728447,
-0.02036520093679428,
0.042... | 0.434939 |
This page lists the status, timeline and policy for currently supported releases. Supported releases of Istio include releases that are in the active maintenance window and are patched for security and bug fixes. Subsequent patch releases on a minor release do not contain backward incompatible changes. - [Support polic... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/supported-releases/index.md | master | istio | [
-0.06638605892658234,
-0.011558984406292439,
0.04495348036289215,
-0.017362099140882492,
0.05132004991173744,
-0.002581215463578701,
0.008060258813202381,
0.047890037298202515,
-0.07860160619020462,
0.017613815143704414,
0.03950751572847366,
-0.0530255064368248,
-0.048065800219774246,
0.02... | 0.509646 |
release/v1.36 | | 1.27.x | release/v1.35 | | 1.26.x | release/v1.34 | You can find the precise Envoy commit used by Istio [in the `istio/proxy` repository](https://github.com/istio/proxy/blob/{{< source\_branch\_name >}}/WORKSPACE#L26): look for the `ENVOY\_SHA` variable. | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/supported-releases/index.md | master | istio | [
-0.017392627894878387,
-0.040303125977516174,
0.014191141352057457,
0.05324489250779152,
-0.059239186346530914,
-0.019882462918758392,
0.00889959279447794,
0.00044248768244870007,
0.006945115979760885,
0.041125502437353134,
-0.03960714489221573,
-0.07102105021476746,
-0.06938382238149643,
... | 0.527356 |
To provide clarity to our users, use the standard terms in this section consistently within the documentation. ## Service Avoid using the term \*\*service\*\*. Research shows that different folks understand different things under that term. The following table shows acceptable alternatives that provide greater specific... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/terminology/index.md | master | istio | [
-0.12088091671466827,
-0.04124661535024643,
0.013354983180761337,
-0.037222832441329956,
-0.0738794282078743,
-0.04772322624921799,
0.11294355988502502,
-0.042823515832424164,
0.018471412360668182,
0.028405264019966125,
-0.02631203643977642,
-0.0044236816465854645,
0.07085087895393372,
0.0... | 0.1553 |
To contribute new documentation to Istio, just follow these steps: 1. Identify the audience and intended use for the information. 1. Choose the [type of content](#content-types) you wish to contribute. 1. [Choose a title](#choosing-a-title). 1. Write your contribution following our [documentation contribution guides](/... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/add-content/index.md | master | istio | [
0.0006085226777940989,
-0.0155391376465559,
-0.010990035720169544,
0.03398260474205017,
0.027068931609392166,
0.03254975005984306,
0.006630054209381342,
0.13831381499767303,
-0.01329202950000763,
0.04946036636829376,
-0.05903998762369156,
-0.10475362092256546,
0.003748508868739009,
0.05407... | 0.506754 |
of Istio with other projects, or an end-to-end solution for a use case. Examples must use an existing Istio setup as a starting point. Examples must include an automated test since they are maintained for technical accuracy. | Readers that want to quickly run the example themselves and experiment. Ideally, readers shou... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/add-content/index.md | master | istio | [
-0.049540869891643524,
-0.02668095752596855,
0.019566230475902557,
0.055292848497629166,
0.03174727037549019,
-0.06679284572601318,
0.0353626050055027,
0.07436613738536835,
-0.09512821584939957,
-0.005301155615597963,
-0.03524060174822807,
-0.12528327107429504,
-0.0020410208962857723,
0.07... | 0.614791 |
Welcome to the Istio diagram guide! The guide is available as an [SVG file](./diagram-guidelines.svg) or as a [Google Drawings file](https://docs.google.com/drawings/d/1f3NyutAQIDOA8ojGNyMA5JAJllDShZGQAFfdD01XdSc/edit) to allow you to reuse the shapes and styles with ease. Use these guidelines to create SVG diagrams fo... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/diagrams/index.md | master | istio | [
0.029074355959892273,
-0.024496395140886307,
0.0070475125685334206,
0.03592240810394287,
-0.028010692447423935,
-0.03119744546711445,
-0.04540209472179413,
0.07481339573860168,
-0.03923363238573074,
-0.021307995542883873,
-0.02019522711634636,
-0.030724963173270226,
-0.037293966859579086,
... | 0.475885 |
To remove documentation from Istio, please follow these simple steps: 1. Remove the page. 1. Reconcile the broken links. 1. Submit your contribution to GitHub. ## Remove the page Use `git rm -rf` to remove the directory containing the `index.md` page. ## Reconcile broken links To reconcile broken links, use this flowch... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/remove-content/index.md | master | istio | [
-0.03496344015002251,
0.04618360847234726,
0.042154356837272644,
0.06298157572746277,
0.058929115533828735,
-0.039766233414411545,
-0.0693274587392807,
0.02833956852555275,
-0.0010606901487335563,
0.002203688956797123,
-0.04311511665582657,
-0.006910193711519241,
-0.024897310882806778,
0.0... | 0.423511 |
Hugo shortcodes are special placeholders with a certain syntax that you can add to your content to create dynamic content experiences, such as tabs, images and icons, links to other pages, and special content layouts. This page explains the available shortcodes and how to use them for your content. ## Add images Place ... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/shortcodes/index.md | master | istio | [
0.0023567599710077047,
0.004454765934497118,
0.03356895595788956,
0.026872951537370682,
0.12760254740715027,
0.02004956640303135,
-0.06042031943798065,
0.08477949351072311,
0.0319075733423233,
0.027077332139015198,
0.0048539284616708755,
0.05255156755447388,
0.061175331473350525,
-0.022059... | 0.094804 |
>}} [httpbin]({{}}/samples/httpbin) {{< /text >}} - \*\*{{}}\*\* is how you reference a file in GitHub sources. This shortcode produces a link to `https://github.com/istio/istio/blob\*`, for example: {{< text markdown >}} [RawVM MySQL]({{}}/samples/rawvm/README.md) {{< /text >}} The shortcodes above produce links to th... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/shortcodes/index.md | master | istio | [
-0.004720036871731281,
0.00825181882828474,
-0.05656351521611214,
0.040138520300388336,
0.07686430960893631,
-0.02318803034722805,
-0.03590529412031174,
0.05453191697597504,
0.0003639859496615827,
0.007842217572033405,
-0.016112985089421272,
-0.04071381315588951,
0.02222403511404991,
-0.02... | 0.372057 |
in the `/content/en/boilerplates` directory. ## Use tabs To display content that has multiple options or formats, use tab sets and tabs. For example: - Equivalent commands for different platforms - Equivalent code samples in different languages - Alternative configurations To insert tabbed content, combine the `tabset`... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/shortcodes/index.md | master | istio | [
0.045735713094472885,
0.011596721597015858,
-0.07631370425224304,
0.05762394517660141,
-0.006016779225319624,
0.04917362704873085,
0.014296283014118671,
0.022905664518475533,
-0.008333396166563034,
-0.030215248465538025,
-0.042399778962135315,
-0.04422210901975632,
-0.0007884091464802623,
... | 0.005779 |
format. Instead of a date, this can also be the value `latest_release`, which then uses the latest known Istio release as the start date. This is useful when creating a banner saying "Istio x.y.z has just been released". | | `period_end` | The last date on which to display the item in `YYYY-MM-DD` format. This value is... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/shortcodes/index.md | master | istio | [
-0.03782813623547554,
0.09492059051990509,
-0.021559467539191246,
0.05291253328323364,
0.04741036519408226,
0.015371285378932953,
0.0028667193837463856,
0.050790395587682724,
0.05470407009124756,
-0.016660764813423157,
0.0372297540307045,
-0.022662021219730377,
-0.010829644277691841,
-0.06... | 0.321534 |
The front matter is YAML code in between triple-dashed lines at the top of each file and provides important management options for our content. For example, the front matter allows us to ensure that existing links continue to work for pages that are moved or deleted entirely. This page explains the features currently a... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/front-matter/index.md | master | istio | [
-0.025882810354232788,
0.005076246336102486,
0.0024636415764689445,
0.09355971962213516,
0.05457286909222603,
-0.021316885948181152,
-0.051018424332141876,
0.005729255732148886,
-0.017474493011832237,
0.05194072425365448,
-0.06889290362596512,
0.008222127333283424,
-0.009896606206893921,
-... | 0.403357 |
Description |--------------------|------------ |`skip\_toc` | If true, Hugo doesn't generate a ToC for the page. |`force\_inline\_toc` | If true, Hugo inserts an auto-generated ToC in the text instead of in the sidebar to the right. |`max\_toc\_level` | Sets the heading levels used in the ToC. Values can go from 2 to 6... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/front-matter/index.md | master | istio | [
-0.10697633773088455,
-0.024678949266672134,
0.032155733555555344,
0.05398087203502655,
0.12347418069839478,
0.04048902913928032,
-0.027716876938939095,
0.048808399587869644,
-0.03931855037808418,
0.04506572708487511,
-0.03612612932920456,
-0.019075101241469383,
0.039377905428409576,
-0.06... | 0.18627 |
The Istio documentation follows the standard [GitHub collaboration flow](https://guides.github.com/introduction/flow/) for Pull Requests (PRs). This well-established collaboration model helps open source projects manage the following types of contributions: - [Add](/docs/releases/contribute/add-content) new files to th... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/github/index.md | master | istio | [
-0.0349152609705925,
-0.0539175420999527,
-0.02509060688316822,
0.040902283042669296,
0.016107238829135895,
0.010243810713291168,
-0.020014869049191475,
0.10254266113042831,
0.005679736845195293,
0.04375244304537773,
-0.024517633020877838,
-0.09781897813081741,
-0.03852090239524841,
0.0315... | 0.51044 |
merge issues that prevented the process from working automatically. Note that we only ever cherry pick changes into the current release branch, and never to older branches. Older branches are considered to be archived and generally no longer receive any changes. ## Istio community roles Depending on your contributions ... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/github/index.md | master | istio | [
0.028413156047463417,
-0.07126352190971375,
0.01924261637032032,
0.04647621884942055,
-0.004219099413603544,
-0.06642244011163712,
-0.023119207471609116,
0.04754909500479698,
-0.05932595953345299,
0.02008979767560959,
-0.01311798021197319,
-0.06441150605678558,
-0.0830903947353363,
0.06748... | 0.585517 |
This page shows the formatting standards for the Istio documentation. Istio uses Markdown to markup the content and Hugo to build the website. To ensure consistency across our documentation, we have agreed on these formatting standards. ## Don't use capitalization for emphasis Only use the original capitalization found... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/formatting/index.md | master | istio | [
-0.002331934403628111,
0.017143182456493378,
0.015641113743185997,
0.039561256766319275,
-0.020324483513832092,
-0.022226698696613312,
0.030653638765215874,
0.08255849033594131,
-0.0044813379645347595,
-0.015879780054092407,
-0.04378090426325798,
-0.07537814229726791,
0.0027086795307695866,
... | 0.534933 |
The maintainers and working group leads of the Istio Docs Working Group (WG) approve all changes to the [Istio website](/docs/). A \*\*documentation reviewer\*\* is a trusted contributor that approves content that meets the acceptance criteria described in the [review criteria](#review-criteria). All content reviews fo... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/review/index.md | master | istio | [
-0.0689430832862854,
-0.025163063779473305,
-0.011460046283900738,
0.06864666938781738,
0.037668921053409576,
-0.030198300257325172,
-0.007951721549034119,
0.03836691752076149,
0.045102041214704514,
0.06293696910142899,
-0.007610187400132418,
-0.043172527104616165,
-0.030656104907393456,
0... | 0.534758 |
of the Google developer style guide. - Links and navigation: The content has no broken links and the site builds properly. ### Supplemental acceptance criteria - Content structure: Information structure enhances the readers' experience. - Consistency: Content adheres to all recommendations in the [Istio contribution gu... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/review/index.md | master | istio | [
-0.04783595725893974,
-0.05615946650505066,
0.034194156527519226,
0.024985292926430702,
0.0435560904443264,
0.032316289842128754,
-0.002956805285066366,
0.02872380055487156,
-0.06372442096471786,
0.007575249299407005,
-0.011408226564526558,
0.04725873842835426,
0.001860589487478137,
-0.028... | 0.334019 |
After making your contribution to our website, ensure the changes render as you expect. To ensure you can preview your changes locally, we have tools that let you build and view them easily. We use automated tests to check the quality of all contributions. Before submitting your changes in a Pull Request (PR), you shou... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/build/index.md | master | istio | [
-0.02614411525428295,
0.006583430338650942,
0.013117523863911629,
0.03188195452094078,
0.07272523641586304,
-0.07497435808181763,
-0.11913686245679855,
0.04391859471797943,
-0.05922791361808777,
0.035354383289813995,
-0.029936235398054123,
-0.11713360249996185,
-0.0579986609518528,
-0.0060... | 0.398152 |
All content accepted into the Istio documentation must be \*\*clear\*\* and \*\*understandable\*\*. The standard we use to make that determination is defined by the [highlights](https://developers.google.com/style/highlights) and the [general principles](https://developers.google.com/style/tone) of the Google developer... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/style-guide/index.md | master | istio | [
-0.04827325418591499,
0.003160194493830204,
0.04730118811130524,
0.013537228107452393,
-0.00044686158071272075,
0.009584635496139526,
0.014867664314806461,
0.03873739391565323,
-0.05200101062655449,
0.01717466674745083,
-0.024209819734096527,
-0.08994383364915848,
0.0062810624949634075,
-0... | 0.557173 |
feature in development, add a boilerplate under the front matter that identifies the information accordingly. ### Avoid statements that will soon be out of date Avoid using wording that becomes outdated quickly like "currently" and "new". A feature that is new today is not new for long. |Do | Don't |-------------------... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/style-guide/index.md | master | istio | [
0.03906158730387688,
0.0028055335860699415,
0.07648240774869919,
-0.00774639705196023,
0.08771054446697235,
0.03581123426556587,
-0.020807379856705666,
-0.04517840966582298,
-0.08699198812246323,
0.03443596512079239,
-0.0278482586145401,
-0.027505207806825638,
-0.04430709779262543,
0.05199... | 0.115112 |
Code blocks in the Istio documentation are embedded preformatted block of content. We use Hugo to build our website, and it uses the `text` and `text\_import` shortcodes to add code to a page. Using this markup allows us to provide our readers with a better experience. The rendered code blocks can be easily copied, pri... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/code-blocks/index.md | master | istio | [
-0.07362821698188782,
0.0010671451454982162,
-0.03600691631436348,
0.06915496289730072,
0.02677886188030243,
0.007350542116910219,
-0.0809028223156929,
0.06746316701173782,
0.0016252496279776096,
-0.026773633435368538,
0.014054722152650356,
-0.041580189019441605,
-0.015213879756629467,
-0.... | 0.473545 |
istio-system get pods -l istio-mixer-type=telemetry -o jsonpath='{.items[0].metadata.name}') mixer | grep \"instance\":\"newlog.logentry.istio-system\" {"level":"warn","ts":"2017-09-21T04:33:31.249Z","instance":"newlog.logentry.istio-system","destination":"details","latency":"6.848ms","responseCode":200,"responseSize":... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/code-blocks/index.md | master | istio | [
0.057205550372600555,
-0.03143974393606186,
-0.007771668955683708,
0.004898337181657553,
-0.0055799405090510845,
-0.05437520146369934,
0.05814893916249275,
0.03275825083255768,
0.028474314138293266,
0.019909720867872238,
-0.004767711739987135,
-0.16637162864208221,
-0.054555878043174744,
-... | 0.471369 |
that takes you to the corresponding file: {{< text bash >}} $ kubectl apply -f @samples/bookinfo/networking/virtual-service-reviews-v3.yaml@ {{< /text >}} By default, these links point to the current release branch of the `istio/istio` repository. For the link to point to a different Istio repository instead, you can u... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/contribute/code-blocks/index.md | master | istio | [
0.0009288154542446136,
0.025294361636042595,
-0.0201549232006073,
0.013100536540150642,
0.011377324350178242,
0.015340825542807579,
-0.0019796565175056458,
0.003388098906725645,
0.10753923654556274,
0.017228705808520317,
-0.01653451845049858,
-0.05688173696398735,
-0.020142020657658577,
-0... | 0.328314 |
This page lists the relative maturity and support level of every Istio feature. Please note that the phases are applied to individual features within the project, not to the project as a whole. Here is a high level description of what these labels mean. ## Feature phase definitions | | Experimental | Alpha | Beta | Sta... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/feature-stages/index.md | master | istio | [
0.013393489643931389,
-0.0023273127153515816,
-0.007136003114283085,
0.006212511099874973,
0.009415809996426105,
0.025544358417391777,
-0.08711390197277069,
0.054963137954473495,
-0.04899553954601288,
-0.009438377805054188,
-0.023676712065935135,
-0.11506734043359756,
-0.0527433417737484,
... | 0.383686 |
beta (e.g. v1beta1). | The API version is `vX` where X is an integer (e.g. v1). | | Availability | The feature may or may not be available in the main Istio repository. The feature may or may not appear in an Istio release. If it does appear in an Istio release it will be disabled by default. The feature requires an ex... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/feature-stages/index.md | master | istio | [
-0.0045056939125061035,
-0.035460617393255234,
0.0048714326694607735,
0.06347422301769257,
0.05333873629570007,
0.011725968681275845,
0.02906191162765026,
0.03974679857492447,
-0.0767548605799675,
-0.020695440471172333,
-0.01930428110063076,
-0.039837796241045,
-0.06864234060049057,
0.0287... | 0.518019 |
on the new feature, and may require manual conversion of objects to the new version. When manual conversion is necessary, the project will provide documentation on the process. | Only strictly compatible changes are allowed in subsequent software releases. | | Testing | The presence of the feature must not affect any r... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/feature-stages/index.md | master | istio | [
0.01992289535701275,
0.0037895669229328632,
-0.026194151490926743,
0.03469127416610718,
0.09798719733953476,
-0.02433706261217594,
-0.06748384237289429,
0.0032577046658843756,
-0.1937161237001419,
-0.026772795245051384,
0.055876486003398895,
0.011336252093315125,
-0.00684386445209384,
0.01... | 0.075261 |
We are very grateful to the security researchers and users that report back Istio security vulnerabilities. We investigate every report thoroughly. ## Reporting a vulnerability To make a report, send an email to the private [istio-security-vulnerability-reports@googlegroups.com](mailto:istio-security-vulnerability-repo... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/security-vulnerabilities/index.md | master | istio | [
-0.04346603900194168,
0.046740416437387466,
-0.0029551833868026733,
0.07322603464126587,
0.03461810573935509,
0.013159578666090965,
0.028854850679636,
0.07491642981767654,
-0.020497942343354225,
0.018700556829571724,
-0.01997396908700466,
-0.12332423031330109,
0.01147952489554882,
0.049800... | 0.510959 |
CVEs. When CVEs are detected in our images, new images are automatically built and used for all future builds. Additionally, the security team analyzes the vulnerabilities to see if they are exploitable in Istio directly. In most cases, these vulnerabilities may be present in packages within the base image, but are not... | https://github.com/istio/istio.io/blob/master//content/en/docs/releases/security-vulnerabilities/index.md | master | istio | [
-0.04152124747633934,
0.07142972201108932,
0.033198632299900055,
0.0025613263715058565,
0.09467257559299469,
-0.050541143864393234,
-0.032702233642339706,
0.08773879706859589,
-0.024508988484740257,
0.013908478431403637,
-0.00590481236577034,
-0.0794682502746582,
0.021815886721014977,
0.09... | 0.359838 |
This task shows how to configure the minimum TLS version for Istio workloads. The maximum TLS version for Istio workloads is 1.3. ## Configuration of minimum TLS version for Istio workloads \* Install Istio through `istioctl` with the minimum TLS version configured. The `IstioOperator` custom resource used to configure... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/tls-configuration/workload-min-tls-version/index.md | master | istio | [
-0.02870776504278183,
0.06036171317100525,
0.006123182363808155,
-0.0036653310526162386,
-0.05914762243628502,
-0.06002794951200485,
0.021707937121391296,
0.010334635153412819,
0.060448430478572845,
-0.04122549667954445,
-0.05800929665565491,
-0.10553199052810669,
-0.027685904875397682,
0.... | 0.428687 |
This task shows how administrators can configure the Istio certificate authority (CA) with a root certificate, signing certificate and key. By default the Istio CA generates a self-signed root certificate and key and uses them to sign the workload certificates. To protect the root CA key, you should use a root CA which... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/cert-management/plugin-ca-cert/index.md | master | istio | [
-0.01813490316271782,
0.03138086572289467,
-0.025070862844586372,
0.04406227916479111,
-0.03811604529619217,
-0.08004684746265411,
-0.027528397738933563,
0.08770166337490082,
-0.010230820626020432,
-0.008960827253758907,
-0.0032398493494838476,
-0.1366289258003235,
0.08559459447860718,
0.0... | 0.425957 |
from the secret-mount files. {{< text bash >}} $ istioctl install --set profile=demo {{< /text >}} ## Deploying example services 1. Deploy the `httpbin` and `curl` sample services. {{< text bash >}} $ kubectl create ns foo $ kubectl apply -f <(istioctl kube-inject -f samples/httpbin/httpbin.yaml) -n foo $ kubectl apply... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/cert-management/plugin-ca-cert/index.md | master | istio | [
-0.051207154989242554,
0.03750288859009743,
0.005100594833493233,
-0.02777816168963909,
-0.04958571121096611,
-0.08885857462882996,
-0.022937094792723656,
-0.02726450003683567,
0.09447532147169113,
0.01466766744852066,
0.021668432280421257,
-0.10603363811969757,
0.0703238695859909,
-0.0043... | 0.18469 |
{{< boilerplate experimental >}} This feature requires Kubernetes version >= 1.18. This task shows how to provision workload certificates using a custom certificate authority that integrates with the [Kubernetes CSR API](https://kubernetes.io/docs/reference/access-authn-authz/certificate-signing-requests/). Different w... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/cert-management/custom-ca-k8s/index.md | master | istio | [
-0.0846509039402008,
0.05219405144453049,
0.06301450729370117,
0.022178243845701218,
-0.051623255014419556,
-0.08001763373613358,
-0.012960469350218773,
-0.024331875145435333,
0.0975242331624031,
-0.03792732581496239,
-0.057405296713113785,
-0.10672178119421005,
0.08294677734375,
0.0852168... | 0.131636 |
clusterissuers.cert-manager.io/bar components: pilot: k8s: env: - name: CERT\_SIGNER\_DOMAIN value: clusterissuers.cert-manager.io - name: PILOT\_CERT\_PROVIDER value: k8s.io/clusterissuers.cert-manager.io/istio-system overlays: - kind: ClusterRole name: istiod-clusterrole-istio-system patches: - path: rules[-1] value:... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/cert-management/custom-ca-k8s/index.md | master | istio | [
0.005639712326228619,
0.01592918299138546,
-0.041645996272563934,
0.03342249616980553,
-0.02213655598461628,
-0.023784996941685677,
0.02519480139017105,
0.013254373334348202,
0.008108529262244701,
0.0003714027698151767,
0.006355066783726215,
-0.1928660273551941,
0.02339768037199974,
0.0622... | 0.410166 |
to implement a Kubernetes controller to watch the `CertificateSigningRequest` Resources and act on them. \* Better multi-tenancy - By specifying a different cert-signer for different workloads, certificates for different tenant's workloads can be signed by different CAs. | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/cert-management/custom-ca-k8s/index.md | master | istio | [
0.016342181712388992,
0.005754348821938038,
0.034223608672618866,
-0.05174980312585831,
-0.053458135575056076,
0.0019447396043688059,
0.0027797783259302378,
-0.03236084431409836,
0.11133504658937454,
0.0008516063680872321,
-0.03671276569366455,
-0.06292074173688889,
0.039085470139980316,
0... | 0.130509 |
This task shows you how to set up Istio authorization policy for TCP traffic in an Istio mesh. ## Before you begin Before you begin this task, do the following: \* Read the [Istio authorization concepts](/docs/concepts/security/#authorization). \* Install Istio using the [Istio installation guide](/docs/setup/install/i... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-tcp/index.md | master | istio | [
-0.014829004183411598,
0.047448087483644485,
0.018054183572530746,
-0.05116879194974899,
-0.12120601534843445,
-0.029859201982617378,
0.06980573385953903,
0.008113468065857887,
0.02004058100283146,
0.03679880499839783,
-0.07677046209573746,
-0.12554578483104706,
-0.017596717923879623,
0.04... | 0.471193 |
Verify that requests to port 9001 are allowed using the following command: {{< text bash >}} $ kubectl exec "$(kubectl get pod -l app=curl -n foo -o jsonpath={.items..metadata.name})" \ -c curl -n foo -- sh -c \ 'echo "port 9001" | nc tcp-echo 9001' | grep "hello" && echo 'connection succeeded' || echo 'connection reje... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-tcp/index.md | master | istio | [
0.007559616584330797,
0.0846773311495781,
0.0076432921923696995,
-0.08179060369729996,
-0.060586802661418915,
-0.05756736174225807,
0.0087587283924222,
-0.020738987252116203,
0.03793825954198837,
0.005342456512153149,
-0.025776254013180733,
-0.0862574651837349,
-0.02100350894033909,
0.0208... | 0.06274 |
Add a DENY policy with both TCP and HTTP fields using the following command: {{< text bash >}} $ kubectl apply -f - <}} 1. Verify that requests to port 9000 is denied. This occurs because the request matches the `ports` in the above-mentioned deny policy. {{< text bash >}} $ kubectl exec "$(kubectl get pod -l app=curl ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-tcp/index.md | master | istio | [
0.008543903939425945,
0.13613414764404297,
0.0004394697898533195,
-0.08456775546073914,
-0.04395761713385582,
-0.04601593688130379,
0.004831299185752869,
-0.05562957376241684,
0.062064237892627716,
0.03232915699481964,
0.007761229295283556,
-0.09079542011022568,
0.0076448023319244385,
0.00... | 0.083624 |
This task shows you how to set up an Istio authorization policy using a new value for the [action field](/docs/reference/config/security/authorization-policy/#AuthorizationPolicy-Action), `CUSTOM`, to delegate the access control to an external authorization system. This can be used to integrate with [OPA authorization]... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-custom/index.md | master | istio | [
-0.04842866212129593,
-0.0029510450549423695,
-0.08546870201826096,
0.020542383193969727,
-0.09210161864757538,
-0.0748463124036789,
0.04878247156739235,
0.07261505722999573,
-0.008696640841662884,
0.03360490873456001,
-0.04218018427491188,
-0.03383453190326691,
0.04235747456550598,
0.0563... | 0.389241 |
external authorizer]({{< github\_tree >}}/samples/extauthz) which allows requests with the header `x-ext-authz: allow`. 1. Edit the mesh config with the following command: {{< text bash >}} $ kubectl edit configmap istio -n istio-system {{< /text >}} 1. In the editor, add the extension provider definitions shown below:... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-custom/index.md | master | istio | [
-0.0004163575067650527,
0.03540961816906929,
-0.03800864517688751,
-0.026209978386759758,
0.009684448130428791,
-0.07030195742845535,
0.02276020497083664,
0.020337538793683052,
0.06984341144561768,
0.042663224041461945,
0.005511967930942774,
-0.10567650943994522,
-0.015424290671944618,
0.0... | 0.202055 |
to confirm it was called twice (for the two requests). The first one was allowed and the second one was denied: {{< text bash >}} $ kubectl logs "$(kubectl get pod -l app=ext-authz -n foo -o jsonpath={.items..metadata.name})" -n foo -c ext-authz 2021/01/07 22:55:47 Starting HTTP server at [::]:8000 2021/01/07 22:55:47 ... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-custom/index.md | master | istio | [
0.008590440265834332,
0.08017455786466599,
-0.008081129752099514,
-0.02528916858136654,
-0.014798947609961033,
-0.09470333904027939,
-0.004807471297681332,
-0.05422895774245262,
0.09082262963056564,
0.03712974116206169,
0.014568876475095749,
-0.0514252707362175,
-0.019356433302164078,
0.03... | 0.069173 |
This task shows you how to enforce IP-based access control on an Istio ingress gateway using an authorization policy. {{< boilerplate gateway-api-support >}} ## Before you begin Before you begin this task, do the following: \* Read the [Istio authorization concepts](/docs/concepts/security/#authorization). \* Install I... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-ingress/index.md | master | istio | [
-0.01177935115993023,
0.04616833105683327,
-0.03032097965478897,
0.014855626039206982,
-0.09465470910072327,
0.004675514996051788,
0.06211065128445625,
-0.011275815777480602,
-0.0019298320403322577,
0.045729316771030426,
-0.0230748001486063,
-0.11452310532331467,
-0.012836858630180359,
0.0... | 0.407274 |
a `LoadBalancer` service. What if the Pod that is handling traffic from the `NodePort` or `LoadBalancer` isn't running on the worker node that received the traffic? Kubernetes has its own internal proxy called kube-proxy that receives the packets and forwards them to the correct node. ## Source IP address of the origin... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-ingress/index.md | master | istio | [
-0.08676788955926895,
0.047238606959581375,
0.0847499892115593,
-0.05038284882903099,
-0.02284833788871765,
-0.05540081858634949,
0.07740601897239685,
-0.04083375260233879,
0.08241720497608185,
0.03618054836988449,
-0.10058954358100891,
-0.006497025024145842,
-0.028446970507502556,
-0.0340... | 0.292919 |
an ingress gateway pod to multiple nodes\*\* if you enable `externalTrafficPolicy: Local`. Otherwise, this creates a situation where \*\*only\*\* nodes with an active ingress gateway pod will be able to accept and distribute incoming NLB traffic to the rest of the cluster, creating potential ingress traffic bottlenecks... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-ingress/index.md | master | istio | [
0.0011082018027082086,
-0.0009650971041992307,
0.023600172251462936,
0.0374087430536747,
0.0012860234128311276,
0.00915235374122858,
0.049088794738054276,
0.019484668970108032,
0.034850891679525375,
0.10297702252864838,
-0.04355945065617561,
-0.07039126753807068,
0.021528368815779686,
-0.0... | 0.320911 |
logs "$pod" -n istio-system | grep remoteIP; done | tail -1 | awk -F, '{print $3}' | awk -F: '{print $2}' | sed 's/ //') && echo "$CLIENT\_IP" 192.168.10.15 {{< /text >}} \*\*\*remoteIpBlocks:\*\*\* {{< text bash >}} $ CLIENT\_IP=$(kubectl get pods -n istio-system -o name -l istio=ingressgateway | sed 's|pod/||' | whil... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-ingress/index.md | master | istio | [
0.03401418402791023,
0.08601953834295273,
0.021291635930538177,
-0.030015313997864723,
-0.015257950872182846,
-0.029687637463212013,
0.07052488625049591,
0.007584462407976389,
0.06765930354595184,
0.05543367192149162,
0.026283610612154007,
-0.054710593074560165,
-0.03263523057103157,
-0.05... | 0.288388 |
$ kubectl get pods -n foo -o name -l gateway.networking.k8s.io/gateway-name=httpbin-gateway | sed 's|pod/||' | while read -r pod; do kubectl logs "$pod" -n foo; done {{< /text >}} {{< /tab >}} {{< /tabset >}} ## Clean up \* Remove the authorization policy: {{< tabset category-name="config-api" >}} {{< tab name="Istio A... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-ingress/index.md | master | istio | [
0.060599859803915024,
0.07117052376270294,
-0.0015345003921538591,
-0.01198542583733797,
-0.01884152740240097,
-0.0197428148239851,
0.05921445041894913,
-0.054725658148527145,
0.05877162516117096,
0.045107726007699966,
-0.007643914315849543,
-0.10898972302675247,
-0.02673722617328167,
-0.0... | 0.229439 |
{{< boilerplate alpha >}} This task shows you how to set up an Istio authorization policy using a new [experimental annotation `istio.io/dry-run`](/docs/reference/config/annotations/) to dry-run the policy without actually enforcing it. The dry-run annotation allows you to better understand the effect of an authorizati... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-dry-run/index.md | master | istio | [
-0.03807307779788971,
0.049838293343782425,
-0.008139469660818577,
0.014164306223392487,
-0.0007192370831035078,
-0.09300752729177475,
0.03843096271157265,
0.04160936176776886,
-0.07996244728565216,
0.03985489159822464,
-0.026316862553358078,
-0.08669083565473557,
-0.004107910208404064,
0.... | 0.565081 |
more details of the logging. ## Check dry-run result in metric using Prometheus 1. Open the Prometheus dashboard with the following command: {{< text bash >}} $ istioctl dashboard prometheus {{< /text >}} 1. In the Prometheus dashboard, search for the following metric: {{< text plain >}} envoy\_http\_inbound\_0\_0\_0\_... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-dry-run/index.md | master | istio | [
-0.01893215999007225,
0.05862577259540558,
-0.004060820676386356,
0.03567009046673775,
0.036834679543972015,
-0.14037485420703888,
0.028754934668540955,
-0.053332481533288956,
0.009287108667194843,
0.017534784972667694,
-0.03023514710366726,
-0.08071199059486389,
0.03446841984987259,
0.056... | 0.220554 |
This task shows you how to migrate from one trust domain to another without changing authorization policy. In Istio 1.4, we introduce an alpha feature to support {{< gloss >}}trust domain migration{{}} for authorization policy. This means if an Istio mesh needs to change its {{< gloss >}}trust domain{{}}, the authoriza... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-td-migration/index.md | master | istio | [
-0.05862462520599365,
-0.04483707994222641,
-0.04241561517119408,
-0.013943910598754883,
-0.04471152648329735,
-0.08179605007171631,
0.08506350964307785,
-0.02728559635579586,
0.005345700308680534,
0.0041604358702898026,
-0.005810966715216637,
-0.13649392127990723,
0.045370686799287796,
0.... | 0.422627 |
identity, which is the old identity of the `curl` application in `curl-allow` namespace. When we migrated to a new trust domain above, i.e. `new-td`, the identity of this `curl` application is now `new-td/ns/curl-allow/sa/curl`, which is not the same as `old-td/ns/curl-allow/sa/curl`. Therefore, requests from the `curl... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-td-migration/index.md | master | istio | [
-0.04873466491699219,
-0.005913956556469202,
-0.041468605399131775,
-0.008289494551718235,
-0.016763698309659958,
-0.06475196778774261,
0.030893338844180107,
-0.011042228899896145,
0.010104835964739323,
0.03636978194117546,
0.012252306565642357,
-0.11977679282426834,
0.019417613744735718,
... | 0.48007 |
This task shows you how to set up an Istio authorization policy to enforce access based on a JSON Web Token (JWT). An Istio authorization policy supports both string typed and list-of-string typed JWT claims. ## Before you begin Before you begin this task, do the following: \* Complete the [Istio end user authenticatio... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-jwt/index.md | master | istio | [
-0.08213788270950317,
0.030445342883467674,
-0.021693700924515724,
-0.01740892231464386,
-0.10929897427558899,
-0.046551965177059174,
0.05690598487854004,
0.020207880064845085,
-0.0016481311758980155,
0.02510814182460308,
-0.05608163774013519,
-0.11581830680370331,
-0.00016740492719691247,
... | 0.457992 |
curl "http://httpbin.foo:8000/headers" -sS -o /dev/null -w "%{http\_code}\n" 403 {{< /text >}} 1. The following command updates the `require-jwt` authorization policy to also require the JWT to have a claim named `groups` containing the value `group1`: {{< text syntax="bash" expandlinks="false" >}} $ kubectl apply -f -... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-jwt/index.md | master | istio | [
-0.06693903356790543,
0.07783107459545135,
-0.007265626452863216,
-0.006067682523280382,
0.02153632417321205,
-0.008491706103086472,
0.023948078975081444,
-0.0309453122317791,
0.0765584334731102,
-0.028349896892905235,
-0.04041854292154312,
-0.12118750065565109,
0.06663676351308823,
-0.063... | 0.073359 |
This task shows you how to set up Istio authorization policy of `ALLOW` action for HTTP traffic in an Istio mesh. ## Before you begin Before you begin this task, do the following: \* Read the [Istio authorization concepts](/docs/concepts/security/#authorization). \* Follow the [Istio installation guide](/docs/setup/ins... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-http/index.md | master | istio | [
-0.053267039358615875,
0.014855832792818546,
-0.09125193953514099,
-0.023668838664889336,
-0.054661814123392105,
-0.017691578716039658,
0.01902727596461773,
-0.015552014112472534,
0.017028450965881348,
0.03420381247997284,
-0.010706103406846523,
-0.08471080660820007,
0.027884645387530327,
... | 0.415839 |
the `productpage` workload, which issues requests using the `cluster.local/ns/default/sa/bookinfo-productpage` service account, to access the `reviews` workload through `GET` methods: {{< text bash >}} $ kubectl apply -f - <}} Point your browser at the Bookinfo `productpage` (`http://$GATEWAY\_URL/productpage`). Now, y... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-http/index.md | master | istio | [
-0.004251406062394381,
-0.038041602820158005,
-0.06799660623073578,
0.02362745814025402,
-0.03041224740445614,
0.031991079449653625,
-0.0527532696723938,
-0.0867057740688324,
0.05742520093917847,
0.03748391196131706,
0.019069679081439972,
-0.04707612469792366,
0.005339999683201313,
-0.0409... | 0.042491 |
This task shows you how to set up Istio authorization policy of `DENY` action to explicitly deny traffic in an Istio mesh. This is different from the `ALLOW` action because the `DENY` action has higher priority and will not be bypassed by any `ALLOW` actions. ## Before you begin Before you begin this task, do the follo... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-deny/index.md | master | istio | [
-0.03745805472135544,
0.046613190323114395,
0.0022942889481782913,
-0.01797172613441944,
-0.0942002534866333,
-0.04398820549249649,
0.0484105683863163,
-0.029881751164793968,
0.005879699718207121,
0.06839945167303085,
-0.02771168388426304,
-0.08257298916578293,
-0.01706758886575699,
0.0589... | 0.496123 |
sets the `action` field to `ALLOW`. This type of policy is better known as an allow policy. {{< text bash >}} $ kubectl apply -f - <}} 1. Verify that `GET` requests with the HTTP header `x-token: guest` at path `/ip` are denied by the `deny-method-get` policy. Deny policies takes precedence over the allow policies: {{<... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authorization/authz-deny/index.md | master | istio | [
0.03066021390259266,
0.10597161203622818,
-0.0327330157160759,
-0.061687421053647995,
-0.009259777143597603,
-0.047131605446338654,
-0.004670010879635811,
-0.05303741246461868,
0.06019037216901779,
0.05933450162410736,
0.02940542995929718,
-0.05846671387553215,
-0.019352050498127937,
-0.04... | 0.102532 |
{{< boilerplate alpha >}} This task shows you how to route requests based on JWT claims on an Istio ingress gateway using the request authentication and virtual service. Note: this feature only supports Istio ingress gateway and requires the use of both request authentication and virtual service to properly validate an... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/jwt-route/index.md | master | istio | [
-0.08042563498020172,
0.005456624552607536,
-0.027119319885969162,
-0.027924366295337677,
-0.0712885856628418,
-0.024508336558938026,
0.0684087872505188,
0.047086477279663086,
0.003831873182207346,
0.03726495802402496,
-0.06711382418870926,
-0.12152808904647827,
-0.008476047776639462,
0.01... | 0.527521 |
>}} $ curl -s -I "http://$INGRESS\_HOST:$INGRESS\_PORT/headers" -H "Authorization: Bearer some.invalid.token" HTTP/1.1 401 Unauthorized ... {{< /text >}} The 401 is returned by the request authentication because the JWT failed the validation. 1. Validate the ingress gateway routes the request with a valid JWT token tha... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/jwt-route/index.md | master | istio | [
-0.07791212201118469,
0.06977757066488266,
-0.03686921298503876,
0.024435479193925858,
0.04057544469833374,
-0.042588114738464355,
0.006902133580297232,
-0.021927831694483757,
0.06220719963312149,
0.044672783464193344,
-0.03234636411070824,
-0.09276992082595825,
0.04697642847895622,
-0.012... | 0.200042 |
This task shows how to ensure your workloads only communicate using mutual TLS as they are migrated to Istio. Istio automatically configures workload sidecars to use [mutual TLS](/docs/tasks/security/authentication/authn-policy/#auto-mutual-tls) when calling other workloads. By default, Istio configures the destination... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/mtls-migration/index.md | master | istio | [
-0.1084429994225502,
0.060456953942775726,
-0.02017502672970295,
-0.016275348141789436,
-0.05447988957166672,
-0.1000269204378128,
0.04980466142296791,
-0.029507532715797424,
0.03162812441587448,
-0.02949640154838562,
-0.03810640424489975,
-0.1193472295999527,
-0.004316830541938543,
0.1086... | 0.476196 |
app=curl -n ${from} -o jsonpath={.items..metadata.name})" -c curl -n ${from} -- curl http://httpbin.${to}:8000/ip -s -o /dev/null -w "curl.${from} to httpbin.${to}: %{http\_code}\n"; done; done curl.foo to httpbin.foo: 200 curl.foo to httpbin.bar: 200 curl.bar to httpbin.foo: 200 curl.bar to httpbin.bar: 200 curl.legac... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/mtls-migration/index.md | master | istio | [
0.0038740811869502068,
0.04619358852505684,
-0.05827213078737259,
-0.034071605652570724,
-0.03803642839193344,
-0.0413992740213871,
0.001934459200128913,
-0.006962543819099665,
0.045778751373291016,
0.031245918944478035,
0.017800994217395782,
-0.12138313055038452,
-0.053941238671541214,
-0... | 0.266495 |
This task covers the primary activities you might need to perform when enabling, configuring, and using Istio authentication policies. Find out more about the underlying concepts in the [authentication overview](/docs/concepts/security/#authentication). ## Before you begin \* Understand Istio [authentication policy](/d... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/authn-policy/index.md | master | istio | [
-0.05513375252485275,
0.028132958337664604,
-0.0007298181881196797,
-0.007429439574480057,
-0.0997900515794754,
-0.036840472370386124,
0.049990877509117126,
0.020939644426107407,
0.04503944143652916,
0.0115490248426795,
-0.026887735351920128,
-0.14354804158210754,
0.0237946268171072,
0.052... | 0.438431 |
workloads with proxies uses mutual TLS, without you doing anything. For example, take the response from a request to `httpbin/header`. When using mutual TLS, the proxy injects the `X-Forwarded-Client-Cert` header to the upstream request to the backend. That header's presence is evidence that mutual TLS is used. For exa... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/authn-policy/index.md | master | istio | [
-0.029377209022641182,
0.0899123027920723,
0.012402203865349293,
-0.01593679003417492,
-0.07282926142215729,
-0.05932443216443062,
0.0007344417972490191,
-0.057916317135095596,
0.13111162185668945,
0.017012983560562134,
-0.05448000878095627,
-0.04163980484008789,
0.03361564129590988,
0.004... | 0.069791 |
>}} $ for from in "foo" "bar" "legacy"; do for to in "foo" "bar" "legacy"; do kubectl exec "$(kubectl get pod -l app=curl -n ${from} -o jsonpath={.items..metadata.name})" -c curl -n ${from} -- curl "http://httpbin.${to}:8000/ip" -s -o /dev/null -w "curl.${from} to httpbin.${to}: %{http\_code}\n"; done; done curl.foo to... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/authn-policy/index.md | master | istio | [
0.0390106737613678,
0.009709333069622517,
0.011666852049529552,
-0.054433561861515045,
-0.07564065605401993,
-0.01834769919514656,
-0.053769759833812714,
-0.03496527671813965,
0.06616772711277008,
0.023805130273103714,
0.025733981281518936,
-0.08623646199703217,
-0.039165198802948,
-0.0659... | 0.067032 |
http://httpbin.foo:8000/ip -s -o /dev/null -w "%{http\_code}\n" 200 {{< /text >}} ### Cleanup part 2 Remove policies created in the above steps: {{< text bash >}} $ kubectl delete peerauthentication default overwrite-example -n foo $ kubectl delete peerauthentication httpbin -n bar {{< /text >}} ## End-user authenticat... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/authn-policy/index.md | master | istio | [
-0.06335648894309998,
0.033912427723407745,
-0.0004440392949618399,
-0.0652124285697937,
-0.06335721909999847,
-0.042031604796648026,
0.0005467094597406685,
-0.048858627676963806,
0.035636331886053085,
-0.0006186507525853813,
-0.032560888677835464,
-0.06668349355459213,
0.02415028028190136,
... | 0.204457 |
this means the JWT token will become valid 60 seconds earlier than its configured `nbf` and remain valid 60 seconds after its configured `exp`. For example, the command below creates a token that expires in 5 seconds. As you see, Istio authenticates requests using that token successfully at first but rejects them after... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/authn-policy/index.md | master | istio | [
-0.08939914405345917,
0.02979455143213272,
-0.0079801045358181,
0.03057064302265644,
-0.004860042128711939,
-0.07552649825811386,
0.0192358810454607,
0.026447143405675888,
0.08168085664510727,
-0.0006634839810431004,
-0.02195020765066147,
-0.024387676268815994,
0.006855633109807968,
-0.037... | 0.424209 |
{{< boilerplate experimental >}} This task shows you how to copy valid JWT claims to HTTP headers after JWT authentication is successfully completed via an Istio request authentication policy. {{< warning >}} Only claims of type string, boolean, and integer are supported. Array type claims are not supported at this tim... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/security/authentication/claim-to-header/index.md | master | istio | [
-0.08651873469352722,
0.04353027790784836,
-0.005541938357055187,
-0.018731456249952316,
-0.042717184871435165,
-0.015613257884979248,
0.03455469757318497,
0.025507668033242226,
-0.014118061400949955,
-0.006628282833844423,
-0.016614310443401337,
-0.15813246369361877,
0.015105964615941048,
... | 0.41677 |
Telemetry API has been in Istio as a first-class API for quite sometime now. Previously, users had to configure metrics in the `telemetry` section of the Istio configuration. This task shows you how to customize the metrics that Istio generates with Telemetry API. ## Before you begin [Install Istio](/docs/setup/) in yo... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/telemetry-api/index.md | master | istio | [
-0.012114745564758778,
-0.0134959165006876,
0.005388803780078888,
0.026760714128613472,
-0.04731522873044014,
-0.08404302597045898,
0.014503451064229012,
0.041226260364055634,
-0.015079032629728317,
0.019480034708976746,
-0.02892564982175827,
-0.12741506099700928,
-0.05859806388616562,
0.0... | 0.480482 |
For example, in the output, locate the metric `istio\_requests\_total` and verify it contains your new dimension. {{< tip >}} It might take a short period of time for the proxies to start applying the config. If the metric is not received, you may retry sending requests after a short wait, and look for the metric again... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/telemetry-api/index.md | master | istio | [
-0.009753195568919182,
-0.06481066346168518,
-0.004528926685452461,
0.05556658282876015,
-0.046096038073301315,
-0.09694614261388779,
-0.022574687376618385,
-0.007298865355551243,
-0.013954753056168556,
-0.00047868574620224535,
-0.0039036108646541834,
-0.0710502564907074,
-0.0132122263312339... | 0.163801 |
This task shows you how to customize the metrics that Istio generates. Istio generates telemetry that various dashboards consume to help you visualize your mesh. For example, dashboards that support Istio include: \* [Grafana](/docs/tasks/observability/metrics/using-istio-dashboard/) \* [Kiali](/docs/tasks/observabilit... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/customize-metrics/index.md | master | istio | [
-0.04207663610577583,
-0.00531720370054245,
-0.056942690163850784,
0.023893000558018684,
-0.08974767476320267,
-0.06645815819501877,
0.020777888596057892,
0.08656463027000427,
0.002918910002335906,
0.024263355880975723,
-0.05284157767891884,
-0.17888127267360687,
0.002522410824894905,
0.06... | 0.576371 |
delete the `Bookinfo` sample application and its configuration, see [`Bookinfo` cleanup](/docs/examples/bookinfo/#cleanup). | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/customize-metrics/index.md | master | istio | [
-0.01262771524488926,
-0.01976604200899601,
-0.05856658145785332,
-0.03375411406159401,
-0.012658142484724522,
-0.036987707018852234,
-0.09233812242746353,
-0.03636404126882553,
0.02880575880408287,
0.047637902200222015,
0.015975669026374817,
0.05346953123807907,
-0.010453675873577595,
-0.... | -0.019185 |
This task shows you how to query for Istio Metrics using Prometheus. As part of this task, you will use the web-based interface for querying metric values. The [Bookinfo](/docs/examples/bookinfo/) sample application is used as the example application throughout this task. ## Before you begin \* [Install Istio](/docs/se... | https://github.com/istio/istio.io/blob/master//content/en/docs/tasks/observability/metrics/querying-metrics/index.md | master | istio | [
-0.007113885134458542,
-0.005698755849152803,
-0.04698197916150093,
0.040675655007362366,
-0.08692440390586853,
-0.038519237190485,
0.010078903287649155,
0.03373754769563675,
0.04552842676639557,
0.021833769977092743,
-0.01733677089214325,
-0.15722590684890747,
-0.012396988458931446,
-0.00... | 0.410092 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.