`expanded${EVENT_KEY}`,\n  }\n\n  const Selector = {\n    CONTROL_SIDEBAR: '.control-sidebar',\n    CONTROL_SIDEBAR_CONTENT: '.control-sidebar-content',\n    DATA_TOGGLE: '[data-widget=\"control-sidebar\"]',\n    CONTENT: '.content-wrapper',\n    HEADER: '.main-header',\n    FOOTER: '.main-footer',\n  }\n\n  const ClassName = {\n    CONTROL_SIDEBAR_ANIMATE: 'control-sidebar-animate',\n    CONTROL_SIDEBAR_OPEN: 'control-sidebar-open',\n    CONTROL_SIDEBAR_SLIDE: 'control-sidebar-slide-open',\n    LAYOUT_FIXED:...

.main-footer,\nbody.sidebar-collapse:not(.sidebar-mini-md):not(.sidebar-mini) .main-footer::before,\nbody.sidebar-collapse:not(.sidebar-mini-md):not(.sidebar-mini) .main-header,\nbody.sidebar-collapse:not(.sidebar-mini-md):not(.sidebar-mini) .main-header::before {\n  margin-left: 0;\n}\n\n@media (min-width: 768px) {\n  body:not(.sidebar-mini-md) .content-wrapper,\n  body:not(.sidebar-mini-md) .main-footer,\n  body:not(.sidebar-mini-md) .main-header {\n    transition: margin-left 0.3s ease-in-out;\n  ...

test these changes without affecting `master`/`release` pipeline. Here are the instructions.

- Click the left sidebar "VCS Roots" here and create a VCS root [here](https://builds.gradle.org/admin/editProject.html?projectId=Gradle&cameFromUrl=%2Fproject.html%3FprojectId%3DGradle%26tab%3DprojectOverview%26branch_Gradle_Master_Check%3Dmaster)

Next, for an individual proxy we will check if it could possibly be impacted by the change. For example, we know a sidecar never is impacted by a `Gateway` update, and we can also look at scoping (from `Sidecar.egress.hosts`) to further restrict update scopes.

        - has a istio-proxy container, with first 2 args "proxy" and "sidecar" - or less then 2 args, or first arg not proxy.
        - "sidecar.istio.io/inject" is not false
        - "sidecar.istio.io/status" exists

### Redirect API

The annotation based control is currently only supported in 'sidecar' mode. See plugin/redirect.go for details.

      annotations:
        prometheus.io/path: /stats/prometheus
        prometheus.io/port: "15020"
        prometheus.io/scrape: "true"
        proxy.istio.io/config: '{ "holdApplicationUntilProxyStarts": true }'
        sidecar.istio.io/status: '{"initContainers":["istio-init"],"containers":["istio-proxy"],"volumes":null,"imagePullSecrets":null,"revision":"default"}'
      creationTimestamp: null
      labels:
        app: hello
        tier: backend

- The CSI driver-registrar external sidecar container v1.0.0-rc2 is known to take up to 1 minute to start in some cases. We expect this issue to be resolved in a future release of the sidecar container. For verification, please see the release notes of future releases of the external sidecar container. ([#76](https://github.com/kubernetes-csi/driver-registrar/issues/76))

The image used by the chart, `auto`, may be unintuitive.
This exists because the pod spec will be automatically populated at runtime, using the same mechanism as [Sidecar Injection](istio.io/latest/docs/setup/additional-setup/sidecar-injection).
This allows the same configurations and lifecycle to apply to gateways as sidecars.

Note: this does mean that the namespace the gateway is deployed in must not have the `istio-injection=disabled` label.

* GCE: Fixes loadbalancer creation and deletion issues appearing in 1.10.5. ([#66400](https://github.com/kubernetes/kubernetes/pull/66400), [@nicksardo](https://github.com/nicksardo))
* kubeadm: Pull sidecar and dnsmasq-nanny images when using kube-dns ([#66499](https://github.com/kubernetes/kubernetes/pull/66499), [@rosti](https://github.com/rosti))

Motivations to implement ztunnel generally came from two areas.

First, and most importantly, it serves as a means to implement the real goal: waypoints.
For various reasons outside the scope of this document, there is a desire to move from a sidecar based architecture to a "remote proxy" architecture.
However, this has one glaring issue: how do we get the traffic to the remote proxies, while maintaining the zero-trust properties that Istio is built upon?