Update lint checker configuration. (istio#12602)

* Update lint checker configuration.

* Uses mdl.rb in the root

* Fix trailing lines

* Reset mdl.rb

* Fix for adding an empty line

Author: Eric Van Norman

archetypes/blog.md

@@ -5,4 +5,4 @@ description: My one-line description for the page.
 publishdate: 2017-05-24
 attribution: My Name (My Company Name)
 keywords: [keyword1,keyword2]
----
+---

archetypes/news.md

@@ -4,4 +4,4 @@ subtitle: My optional on-line subtitle
 description: My one-line description for the page.
 publishdate: 2017-05-24
 keywords: [keyword1,keyword2]
----
+---

content/en/about/case-studies/airbnb/index.md

@@ -22,4 +22,4 @@ In a [presentation at IstioCon 2021](https://events.istio.io/istiocon-2021/sessi
 
 <iframe width="696" height="392" src="https://www.youtube-nocookie.com/embed/6kDiDQW5YXQ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
-[Download the slides](https://events.istio.io/istiocon-2021/slides/f1s-AirbnbIstioJourney.pdf)
+[Download the slides](https://events.istio.io/istiocon-2021/slides/f1s-AirbnbIstioJourney.pdf)

content/en/about/case-studies/atlassian/index.md

@@ -22,4 +22,4 @@ Atlassian has been deploying Envoy to the compute nodes of its internal PaaS ove
 
 <iframe width="696" height="392" src="https://www.youtube-nocookie.com/embed/iAyVhjuA1HE" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
-[Download the slides](https://events.istio.io/istiocon-2021/slides/c1s-GoingDynamicEnvoy-NicolasMeessen.pdf)
+[Download the slides](https://events.istio.io/istiocon-2021/slides/c1s-GoingDynamicEnvoy-NicolasMeessen.pdf)

content/en/about/case-studies/cash-app/index.md

@@ -22,4 +22,4 @@ As service mesh gains wider adoption, more and more companies are looking to bri
 
 <iframe width="696" height="392" src="https://www.youtube-nocookie.com/embed/TL97Id9j7F0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
-[Download the slides](https://events.istio.io/istiocon-2021/slides/f5a-IstioAdoption-CashApp.pdf)
+[Download the slides](https://events.istio.io/istiocon-2021/slides/f5a-IstioAdoption-CashApp.pdf)

content/en/about/case-studies/ebay/index.md

@@ -22,4 +22,4 @@ Managing a service mesh that spans hundreds of thousands of containers across th
 
 <iframe width="696" height="392" src="https://www.youtube-nocookie.com/embed/Yo6x5Knv7Kc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
-[Download the slides](https://events.istio.io/istiocon-2021/slides/g2s-IstioAtScale-eBay-Sudhi.pdf)
+[Download the slides](https://events.istio.io/istiocon-2021/slides/g2s-IstioAtScale-eBay-Sudhi.pdf)

content/en/about/case-studies/splunk/index.md

@@ -24,4 +24,4 @@ In [this talk from IstioCon 2022](https://events.istio.io/istiocon-2022/sessions
 
 <iframe width="696" height="392" src="https://www.youtube.com/embed/O2IamfjFk7E" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
-[Download the slides](https://events.istio.io/istiocon-2022/slides/a7-IstioSplunk.pdf)
+[Download the slides](https://events.istio.io/istiocon-2022/slides/a7-IstioSplunk.pdf)

content/en/about/case-studies/t-mobile/index.md

@@ -24,4 +24,4 @@ In [this talk from IstioCon 2021](https://events.istio.io/istiocon-2021/sessions
 
 <iframe width="696" height="392" src="https://www.youtube-nocookie.com/embed/gzrWEP87mKg" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
-[Download the slides](https://events.istio.io/istiocon-2021/slides/c2s-GoodBadMesh-JoeSearcy.pdf)
+[Download the slides](https://events.istio.io/istiocon-2021/slides/c2s-GoodBadMesh-JoeSearcy.pdf)

content/en/about/case-studies/wp-engine/index.md

@@ -26,4 +26,4 @@ In [this talk from IstioCon 2022](https://events.istio.io/istiocon-2022/sessions
 
 <iframe width="696" height="392" src="https://www.youtube.com/embed/aI-o1KYwBhs" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
-[Download the slides](https://events.istio.io/istiocon-2022/slides/d5a-WPEngine.pdf)
+[Download the slides](https://events.istio.io/istiocon-2022/slides/d5a-WPEngine.pdf)

content/en/about/case-studies/zozo/index.md

@@ -24,4 +24,4 @@ In [this talk from IstioCon 2022](https://events.istio.io/istiocon-2022/sessions
 
 <iframe width="696" height="392" src="https://www.youtube.com/embed/CKDuv9hwQPs" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
-[Download the slides](https://events.istio.io/istiocon-2022/slides/f1c-AcceleratingZozotown.pdf)
+[Download the slides](https://events.istio.io/istiocon-2022/slides/f1c-AcceleratingZozotown.pdf)

content/en/about/faq/security/verify-mtls-encryption.md

@@ -3,4 +3,4 @@ title: How can I verify that traffic is using mutual TLS encryption?
 weight: 25
 ---
 
-If you installed Istio with `values.global.proxy.privileged=true`, you can use `tcpdump` to determine encryption status. Also in Kubernetes 1.23 and later, as an alternative to installing Istio as privileged, you can use `kubectl debug` to run `tcpdump` in an [ephemeral container](https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/#ephemeral-container). See [Istio mutual TLS migration](/docs/tasks/security/authentication/mtls-migration) for instructions.
+If you installed Istio with `values.global.proxy.privileged=true`, you can use `tcpdump` to determine encryption status. Also in Kubernetes 1.23 and later, as an alternative to installing Istio as privileged, you can use `kubectl debug` to run `tcpdump` in an [ephemeral container](https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/#ephemeral-container). See [Istio mutual TLS migration](/docs/tasks/security/authentication/mtls-migration) for instructions.

content/en/blog/2018/egress-monitoring-access-control/index.md

@@ -614,4 +614,4 @@ demonstrated a simple policy that allowed certain URL paths only. We also showed
     serviceaccount "politics" deleted
     service "politics" deleted
     deployment "politics" deleted
-    {{< /text >}}
+    {{< /text >}}

content/en/blog/2018/export-logs-through-stackdriver/index.md

@@ -255,4 +255,4 @@ exported. In detail as follows:
 ## Availability of logs in export sinks
 
 Export to BigQuery is within minutes (we see it to be almost instant), GCS can
-have a delay of 2 to 12 hours and Pub/Sub is almost immediately.
+have a delay of 2 to 12 hours and Pub/Sub is almost immediately.

content/en/blog/2019/egress-performance/index.md

@@ -119,4 +119,3 @@ In terms of CPU consumption per transaction, Istio has used significantly more C
 ## Conclusion
 
 In this investigation, we tried different options to access an external TLS-enabled MongoDB to compare their performance. The introduction of the Egress Gateway did not have a significant impact on the performance nor meaningful additional CPU consumption. Only when enabling mutual TLS between sidecars and egress gateway or using an additional SNI proxy for wildcarded domains we could observe some degradation.
-

content/en/blog/2019/egress-traffic-control-in-istio-part-2/index.md

@@ -126,4 +126,4 @@ Hopefully, I managed to convince you that Istio is an effective tool to prevent
 traffic. In [the next part of this series](/blog/2019/egress-traffic-control-in-istio-part-3/), I compare secure control of egress traffic in Istio with alternative
 solutions such as
 [Kubernetes Network Policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/) and legacy
-egress proxies/firewalls.
+egress proxies/firewalls.

content/en/blog/2019/egress-traffic-control-in-istio-part-3/index.md

@@ -149,4 +149,4 @@ microservices inside the cluster.
 
 So, if you haven't had the chance to work with Istio yet, [install Istio](/docs/setup/install/) on your cluster
 and check our [egress traffic control tasks](/docs/tasks/traffic-management/egress/) and the tasks for the other
-[Istio features](/docs/tasks/). We also want to hear from you, please join us at [discuss.istio.io](https://discuss.istio.io).
+[Istio features](/docs/tasks/). We also want to hear from you, please join us at [discuss.istio.io](https://discuss.istio.io).

content/en/blog/2019/monitoring-external-service-traffic/index.md

@@ -369,4 +369,4 @@ labels emitted based on the listener type invoked in Envoy.
   connection that is ever established.
 
 Monitoring these metrics can help operators easily understand all the external
-services consumed by the applications in their cluster.
+services consumed by the applications in their cluster.

content/en/blog/2019/multicluster-version-routing/index.md

@@ -458,4 +458,4 @@ across clusters in a multicluster service mesh with a replicated control plane m
 In this example, we manually configured the `.global` service entry and destination rules needed to provide
 connectivity to one remote service, `reviews`. In general, however, if we wanted to enable any service
 to run either locally or remotely, we would need to create `.global` resources for every service.
-Fortunately, this process could be automated and likely will be in a future Istio release.
+Fortunately, this process could be automated and likely will be in a future Istio release.

content/en/blog/2019/root-transition/index.md

@@ -19,4 +19,4 @@ information on how to gauge the age of your certificates and how to perform rota
 {{< tip >}}
 We strongly recommend you rotate root keys and root certificates annually as a security best practice.
 We will send out instructions for root key/cert rotation soon.
-{{< /tip >}}
+{{< /tip >}}

content/en/blog/2019/v1beta1-authorization-policy/index.md

@@ -489,5 +489,3 @@ support the full `v1alpha1` semantics as of the date of this blog post.
 
 The command to support the full `v1alpha1` semantics is expected in a patch
 release following Istio 1.4.
-
-

content/en/blog/2020/istio-sds-gloo/index.md

@@ -19,4 +19,3 @@ There are two different approaches to doing this. The supported way for Gloo OSS
 See a quick demo of integrating open-source Gloo with Istio 1.5:
 
 <iframe width="560" height="315" src="https://www.youtube.com/embed/zhUR3HgeFSg" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
-

content/en/blog/2020/multi-cluster-mesh-automation/index.md

@@ -166,4 +166,4 @@ spec:
 
 Admiral provides a new Global Traffic Routing and unique service naming functionality to address some challenges posed by the Istio model described in [multi-cluster deployment with replicated control planes](https://istio.io/v1.6/docs/setup/install/multicluster/gateways/#deploy-the-istio-control-plane-in-each-cluster). It removes the need for manual configuration synchronization between clusters and generates contextual configuration for each cluster. This makes it possible to operate a Service Mesh composed of many Kubernetes clusters.
 
-We think Istio/Service Mesh community would benefit from this approach, so we [open sourced Admiral](https://github.com/istio-ecosystem/admiral) and would love your feedback and support!
+We think Istio/Service Mesh community would benefit from this approach, so we [open sourced Admiral](https://github.com/istio-ecosystem/admiral) and would love your feedback and support!

content/en/blog/2020/wasm-announce/index.md

@@ -210,4 +210,4 @@ community home for the tooling and the WebAssembly Hub
 
 -   [Tutorials](https://docs.solo.io/web-assembly-hub/latest/tutorial_code/)
 
--   Videos on the [Solo.io YouTube Channel](https://www.youtube.com/channel/UCuketWAG3WqYjjxtQ9Q8ApQ)
+-   Videos on the [Solo.io YouTube Channel](https://www.youtube.com/channel/UCuketWAG3WqYjjxtQ9Q8ApQ)

content/en/blog/2021/external-locality-failover/index.md

@@ -212,4 +212,4 @@ spec:
 
 ## Wrapping Up
 
-Istio’s `VirtualService` and `DestinationRule` API’s provide traffic routing, failure recovery and fault injection features so that you can create resilient applications. The ServiceEntry API extends many of these features to external services that are not part of your service mesh.
+Istio’s `VirtualService` and `DestinationRule` API’s provide traffic routing, failure recovery and fault injection features so that you can create resilient applications. The ServiceEntry API extends many of these features to external services that are not part of your service mesh.

content/en/blog/2021/simple-vms/index.md

@@ -85,4 +85,4 @@ In part 2, I will explain how to configure Istio as well as a virtual machine to
 
 ### Special Thanks
 
-A special thanks to Dave Ortiz for this virtual machine idea and congrats to Constant Contact [a new registered Istio user!](https://github.com/istio/istio.io/pull/10571)
+A special thanks to Dave Ortiz for this virtual machine idea and congrats to Constant Contact [a new registered Istio user!](https://github.com/istio/istio.io/pull/10571)

content/en/blog/2022/ambient-security/index.md

@@ -54,4 +54,4 @@ In ambient mesh, we do not share L7 processing in a proxy across multiple identi
 
 ## Sidecars are still a first-class supported deployment
 
-We understand that some folks are comfortable with the sidecar model and their known security boundaries and wish to stay on that model. With Istio, sidecars are a first-class citizen to the mesh and platform owners have the choice to continue using them. If a platform owner wants to support both sidecar and ambient, they can. A workload with the ambient data plane can natively communicate with workloads that have a sidecar deployed. As folks better understand the security posture of ambient mesh, we are confident that ambient will be the preferred mode of Istio service mesh with sidecars used for specific optimizations.
+We understand that some folks are comfortable with the sidecar model and their known security boundaries and wish to stay on that model. With Istio, sidecars are a first-class citizen to the mesh and platform owners have the choice to continue using them. If a platform owner wants to support both sidecar and ambient, they can. A workload with the ambient data plane can natively communicate with workloads that have a sidecar deployed. As folks better understand the security posture of ambient mesh, we are confident that ambient will be the preferred mode of Istio service mesh with sidecars used for specific optimizations.

content/en/blog/2023/istioday-kubecon-eu/index.md

@@ -45,4 +45,3 @@ Do you want to put your product or service in front of the most discerning Cloud
 For those of you who can't make it, keep your eyes peeled for announcements of IstioCon 2023 and Istio Day North America later this year.
 
 Stay tuned to hear more about the event, and we hope you can join us at Istio Day Europe!
-

content/en/blog/2023/steering-contribution-seat-results/index.md

@@ -29,4 +29,3 @@ Based on this, here is the complete list of Istio Steering Committee members, in
 - [Zhonghu Xu](https://github.com/hzxuzhonghu) (Huawei)
 
 Our sincerest thanks to Louis Ryan, Srihari Angaluri, Kebe Liu and Jason McGee, all long-time contributors to the Istio project, whose terms have come to an end.
-

content/en/boilerplates/helm-jwt-warning.md

@@ -11,4 +11,4 @@ If third party tokens are not enabled, you should add the option
 If the `jwtPolicy` is not set correctly, pods associated with `istiod`,
 gateways or workloads with injected Envoy proxies will not get deployed due
 to the missing `istio-token` volume.
-{{< /warning >}}
+{{< /warning >}}

content/en/boilerplates/helm-prereqs.md

@@ -13,4 +13,4 @@
 {{< text bash >}}
 $ helm repo add istio https://istio-release.storage.googleapis.com/charts
 $ helm repo update
-{{< /text >}}
+{{< /text >}}

content/en/boilerplates/revision-tags-default-outro.md

@@ -2,4 +2,4 @@
 ---
 When using the `default` tag alongside an existing non-revisioned Istio installation it is recommended to remove the old
 `MutatingWebhookConfiguration` (typically called `istio-sidecar-injector`) to avoid having both the older and newer control
-planes attempt injection.
+planes attempt injection.

content/en/boilerplates/revision-tags-preamble.md

@@ -2,4 +2,4 @@
 ---
 Manually relabeling namespaces when moving them to a new revision can be tedious and error-prone.
 [Revision tags](/docs/reference/commands/istioctl/#istioctl-tag) solve this problem.
-[Revision tags](/docs/reference/commands/istioctl/#istioctl-tag) are stable identifiers that point to revisions and can be used to avoid relabeling namespaces. Rather than relabeling the namespace, a mesh operator can simply change the tag to point to a new revision. All namespaces labeled with that tag will be updated at the same time.
+[Revision tags](/docs/reference/commands/istioctl/#istioctl-tag) are stable identifiers that point to revisions and can be used to avoid relabeling namespaces. Rather than relabeling the namespace, a mesh operator can simply change the tag to point to a new revision. All namespaces labeled with that tag will be updated at the same time.

content/en/boilerplates/revision-tags-prologue.md

@@ -8,4 +8,4 @@ caption="Namespace labels unchanged but now all namespaces pointed to 1-10-0"
 >}}
 
 Restarting injected workloads in the namespaces marked `prod-stable` will now result in those workloads using the `1-10-0`
-control plane. Notice that no namespace relabeling was required to migrate workloads to the new revision.
+control plane. Notice that no namespace relabeling was required to migrate workloads to the new revision.

content/en/boilerplates/revision-tags-usage.md

@@ -2,4 +2,4 @@
 ---
 Consider a cluster with two revisions installed, `1-9-5` and `1-10-0`. The cluster operator creates a revision tag `prod-stable`,
 pointed at the older, stable `1-9-5` version, and a revision tag `prod-canary` pointed at the newer `1-10-0` revision. That
-state could be reached via the following commands:
+state could be reached via the following commands:

content/en/boilerplates/telemetry-tracing-tips.md

@@ -2,4 +2,4 @@
 ---
 {{< tip >}}
 Users are encouraged to transition to the [Telemetry API](/docs/tasks/observability/telemetry/) for tracing configuration.
-{{</ tip >}}
+{{</ tip >}}

content/en/docs/ops/best-practices/image-signing-validation/index.md

@@ -65,4 +65,3 @@ The following checks were performed on each of these signatures:
 
 [{"critical":{"identity":{"docker-reference":"gcr.io/istio-release/pilot"},"image":{"docker-manifest-digest":"sha256:c37fd83f6435ca0966d653dc6ac42c9fe5ac11d0d5d719dfe97de84acbf7a32d"},"type":"cosign container image signature"},"optional":null}]
 {{< /text >}}
-

content/en/docs/ops/best-practices/traffic-management/index.md

@@ -319,5 +319,3 @@ To make sure services will have zero down-time when configuring routes with subs
     1. Wait a few seconds for the `VirtualService` configuration to propagate to the Envoy sidecars.
 
     1. Update the `DestinationRule` to remove the unused subsets.
-
-

content/en/docs/ops/configuration/extensibility/wasm-pull-policy/index.md

@@ -35,4 +35,4 @@ In Kubernetes, `ImagePullPolicy: Always` means that an image is pulled directly
 Every time a new pod is started, Kubernetes pulls the image anew.
 
 For a `WasmPlugin`, `ImagePullPolicy: Always` means that Istio will pull an image directly from its source each time the corresponding `WasmPlugin` Kubernetes resource is created or changed.
-Please note that a change not only in `spec` but also `metadata` triggers the pulling of a Wasm module when the `Always` policy is used. This can mean that an image is pulled from source several times over the lifetime of a pod, and over the lifetime of an individual proxy.
+Please note that a change not only in `spec` but also `metadata` triggers the pulling of a Wasm module when the `Always` policy is used. This can mean that an image is pulled from source several times over the lifetime of a pod, and over the lifetime of an individual proxy.

content/en/docs/ops/configuration/traffic-management/network-topologies/index.md

@@ -234,4 +234,3 @@ spec:
 The client IP is retrieved from the PROXY protocol by the gateway and set (or appended) in the `X-Forwarded-For` and `X-Envoy-External-Address` header. Note that the PROXY protocol is mutually exclusive with L7 headers like `X-Forwarded-For` and `X-Envoy-External-Address`. When PROXY protocol is used in conjunction with the `gatewayTopology` configuration, the `numTrustedProxies` and the received `X-Forwarded-For` header takes precedence in determining the trusted client addresses, and PROXY protocol client information will be ignored.
 
 Note that the above example only configures the Gateway to accept incoming PROXY protocol TCP traffic - See the [Envoy documentation](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/other_features/ip_transparency#proxy-protocol) for examples of how to configure Envoy itself to communicate with upstream services using PROXY protocol.
-

content/en/docs/ops/deployment/_index.md

@@ -10,4 +10,4 @@ keywords:
 - installation
 - configuration
 test: n/a
----
+---