docs: fix nested list indentation for sane_lists extension

- Fixed nested indentation to use 4-space in README.md, deprecation.md, version-update-playbook.md, coredns-etcd.md, and aws.md

Author: ROunofF

README.md

@@ -192,11 +192,11 @@ The following tutorials are provided:
 - [Akamai Edge DNS](docs/tutorials/akamai-edgedns.md)
 - [Alibaba Cloud](docs/tutorials/alibabacloud.md)
 - AWS
-  - [AWS Load Balancer Controller](docs/tutorials/aws-load-balancer-controller.md)
-  - [Route53](docs/tutorials/aws.md)
-    - [Same domain for public and private Route53 zones](docs/tutorials/aws-public-private-route53.md)
-  - [Cloud Map](docs/tutorials/aws-sd.md)
-  - [Kube Ingress AWS Controller](docs/tutorials/kube-ingress-aws.md)
+    - [AWS Load Balancer Controller](docs/tutorials/aws-load-balancer-controller.md)
+    - [Route53](docs/tutorials/aws.md)
+        - [Same domain for public and private Route53 zones](docs/tutorials/aws-public-private-route53.md)
+    - [Cloud Map](docs/tutorials/aws-sd.md)
+    - [Kube Ingress AWS Controller](docs/tutorials/kube-ingress-aws.md)
 - [Azure DNS](docs/tutorials/azure.md)
 - [Azure Private DNS](docs/tutorials/azure-private-dns.md)
 - [Civo](docs/tutorials/civo.md)
@@ -207,8 +207,8 @@ The following tutorials are provided:
 - [Exoscale](docs/tutorials/exoscale.md)
 - [ExternalName Services](docs/tutorials/externalname.md)
 - Google Kubernetes Engine
-  - [Using Google's Default Ingress Controller](docs/tutorials/gke.md)
-  - [Using the Nginx Ingress Controller](docs/tutorials/gke-nginx.md)
+    - [Using Google's Default Ingress Controller](docs/tutorials/gke.md)
+    - [Using the Nginx Ingress Controller](docs/tutorials/gke-nginx.md)
 - [Headless Services](docs/tutorials/hostport.md)
 - [IONOS Cloud](docs/tutorials/ionoscloud.md)
 - [Istio Gateway Source](docs/sources/istio.md)

docs/deprecation.md

@@ -69,7 +69,7 @@ Votes may be conducted asynchronously, with a reasonable deadline for responses
 Upon approval, the proposing maintainer is responsible for implementing the changes required to mark the feature as deprecated. This includes:
 
 * Updating the codebase with deprecation warnings where applicable.
-  * log.Warn("The XXX is on the path of ***DEPRECATION***. We recommend that you use YYY (link to docs)")
+    * log.Warn("The XXX is on the path of ***DEPRECATION***. We recommend that you use YYY (link to docs)")
 * Documenting the deprecation in release notes and relevant documentation.
 * Updating APIs, metrics, or behaviors per the Kubernetes Deprecation Policy if in scope.
 * If the feature is entirely deprecated, archival of any associated repositories (external provider as example).
@@ -80,7 +80,7 @@ Deprecation must be introduced in the next release. The release must follow sema
 
 * If the project is in the 0.x stage, a `minor` version `bump` is required.
 * For projects 1.x and beyond, a major version bump is required. For the features completely removed.
-  * If it's a flag change/flip, the `minor` version `bump` is acceptable
+    * If it's a flag change/flip, the `minor` version `bump` is acceptable
 
 ### Full Deprecation and Removal
 

docs/tutorials/aws.md

@@ -1013,14 +1013,14 @@ For any given DNS name, only **one** of the following routing policies can be us
 - Latency-based routing: `external-dns.alpha.kubernetes.io/aws-region`
 - Failover:`external-dns.alpha.kubernetes.io/aws-failover`
 - Geolocation-based routing:
-  - `external-dns.alpha.kubernetes.io/aws-geolocation-continent-code`
-  - `external-dns.alpha.kubernetes.io/aws-geolocation-country-code`
-  - `external-dns.alpha.kubernetes.io/aws-geolocation-subdivision-code`
+    - `external-dns.alpha.kubernetes.io/aws-geolocation-continent-code`
+    - `external-dns.alpha.kubernetes.io/aws-geolocation-country-code`
+    - `external-dns.alpha.kubernetes.io/aws-geolocation-subdivision-code`
 - Geoproximity routing:
-  - `external-dns.alpha.kubernetes.io/aws-geoproximity-region`
-  - `external-dns.alpha.kubernetes.io/aws-geoproximity-local-zone-group`
-  - `external-dns.alpha.kubernetes.io/aws-geoproximity-coordinates`
-  - `external-dns.alpha.kubernetes.io/aws-geoproximity-bias`
+    - `external-dns.alpha.kubernetes.io/aws-geoproximity-region`
+    - `external-dns.alpha.kubernetes.io/aws-geoproximity-local-zone-group`
+    - `external-dns.alpha.kubernetes.io/aws-geoproximity-coordinates`
+    - `external-dns.alpha.kubernetes.io/aws-geoproximity-bias`
 - Multi-value answer:`external-dns.alpha.kubernetes.io/aws-multi-value-answer`
 
 ### Associating DNS records with healthchecks
@@ -1059,7 +1059,7 @@ args:
 ```
 
 - The first two changes are needed if you use Route53 in Govcloud, which only supports private zones. There are also no cross account IAM whatsoever between Govcloud and commercial AWS accounts.
-  - If services and ingresses need to make Route 53 entries to an public zone in a commercial account, you will have set env variables of `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` with a key and secret to the commercial account that has the sufficient rights.
+    - If services and ingresses need to make Route 53 entries to an public zone in a commercial account, you will have set env variables of `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` with a key and secret to the commercial account that has the sufficient rights.
 
 ```yaml
 env:
@@ -1137,33 +1137,33 @@ Route53 has a [5 API requests per second per account hard quota](https://docs.aw
 Running several fast polling ExternalDNS instances in a given account can easily hit that limit. Some ways to reduce the request rate include:
 
 - Reduce the polling loop's synchronization interval at the possible cost of slower change propagation (but see `--events` below to reduce the impact).
-  - `--interval=5m` (default `1m`)
+    - `--interval=5m` (default `1m`)
 - Enable a Cache to store the zone records list. It comes with a cost: slower propagation when the zone gets modified from other sources such as the AWS console, terraform, cloudformation or anything similar.
-  - `--provider-cache-time=15m` (default `0m`)
+    - `--provider-cache-time=15m` (default `0m`)
 - Trigger the polling loop on changes to K8s objects, rather than only at `interval` and ensure a minimum of time between events, to have responsive updates with long poll intervals
-  - `--events`
-  - `--min-event-sync-interval=5m` (default `5s`)
+    - `--events`
+    - `--min-event-sync-interval=5m` (default `5s`)
 - Limit the [sources watched](https://github.com/kubernetes-sigs/external-dns/blob/master/pkg/apis/externaldns/types.go#L364) when the `--events` flag is specified to specific types, namespaces, labels, or annotations
-  - `--source=ingress --source=service` - specify multiple times for multiple sources
-  - `--namespace=my-app`
-  - `--label-filter=app in (my-app)`
-  - `--ingress-class=nginx-external`
+    - `--source=ingress --source=service` - specify multiple times for multiple sources
+    - `--namespace=my-app`
+    - `--label-filter=app in (my-app)`
+    - `--ingress-class=nginx-external`
 - Limit services watched by type (not applicable to ingress or other types)
-  - `--service-type-filter=LoadBalancer` default `all`
+    - `--service-type-filter=LoadBalancer` default `all`
 - Limit the hosted zones considered
-  - `--zone-id-filter=ABCDEF12345678` - specify multiple times if needed
-  - `--domain-filter=example.com` by domain suffix - specify multiple times if needed
-  - `--regex-domain-filter=example*` by domain suffix but as a regex - overrides domain-filter
-  - `--exclude-domains=ignore.this.example.com` to exclude a domain or subdomain
-  - `--regex-domain-exclusion=ignore*` subtracts it's matches from `regex-domain-filter`'s matches
-  - `--aws-zone-type=public` only sync zones of this type `[public|private]`
-  - `--aws-zone-tags=owner=k8s` only sync zones with this tag
+    - `--zone-id-filter=ABCDEF12345678` - specify multiple times if needed
+    - `--domain-filter=example.com` by domain suffix - specify multiple times if needed
+    - `--regex-domain-filter=example*` by domain suffix but as a regex - overrides domain-filter
+    - `--exclude-domains=ignore.this.example.com` to exclude a domain or subdomain
+    - `--regex-domain-exclusion=ignore*` subtracts it's matches from `regex-domain-filter`'s matches
+    - `--aws-zone-type=public` only sync zones of this type `[public|private]`
+    - `--aws-zone-tags=owner=k8s` only sync zones with this tag
 - If the list of zones managed by ExternalDNS doesn't change frequently, cache it by setting a TTL.
-  - `--aws-zones-cache-duration=3h` (default `0` - disabled)
+    - `--aws-zones-cache-duration=3h` (default `0` - disabled)
 - Increase the number of changes applied to Route53 in each batch
-  - `--aws-batch-change-size=4000` (default `1000`)
+    - `--aws-batch-change-size=4000` (default `1000`)
 - Increase the interval between changes
-  - `--aws-batch-change-interval=10s` (default `1s`)
+    - `--aws-batch-change-interval=10s` (default `1s`)
 - Introducing some jitter to the pod initialization, so that when multiple instances of ExternalDNS are updated at the same time they do not make their requests on the same second.
 
 A simple way to implement randomised startup is with an init container:
@@ -1203,11 +1203,11 @@ If the change can't fit into any batch - *it will be skipped.*
 There are 3 options to control batch size for AWS provider:
 
 - Maximum amount of changes added to one batch
-  - `--aws-batch-change-size` (default `1000`)
+    - `--aws-batch-change-size` (default `1000`)
 - Maximum size of changes in bytes added to one batch
-  - `--aws-batch-change-size-bytes` (default `32000`)
+    - `--aws-batch-change-size-bytes` (default `32000`)
 - Maximum value count of changes added to one batch
-  - `aws-batch-change-size-values` (default `1000`)
+    - `aws-batch-change-size-values` (default `1000`)
 
 `aws-batch-change-size` can be very useful for throttling purposes and can be set to any value.
 

docs/tutorials/coredns-etcd.md

@@ -21,13 +21,13 @@ After completing this lab, you will have a Kubernetes environment running as con
 Before you start, ensure you have:
 
 - A running kubernetes cluster.
-  - In this tutorial we are going to use [kind](https://kind.sigs.k8s.io/)
+    - In this tutorial we are going to use [kind](https://kind.sigs.k8s.io/)
 - [`kubectl`](https://kubernetes.io/docs/tasks/tools/) and [`helm`](https://helm.sh/)
 - `external-dns` source code or [helm chart](https://github.com/kubernetes-sigs/external-dns/tree/master/charts/external-dns)
 - `CoreDNS` [helm chart](https://github.com/coredns/helm)
 - Optional
-  - `dnstools` container for testing
-  - `etcdctl` to interat with [etcd](https://etcd.io/docs/v3.4/dev-guide/interacting_v3/)
+    - `dnstools` container for testing
+    - `etcdctl` to interat with [etcd](https://etcd.io/docs/v3.4/dev-guide/interacting_v3/)
 
 ## Bootstrap Environment
 

docs/version-update-playbook.md

@@ -16,10 +16,10 @@ Upgrading External-DNS involves validating configuration compatibility, testing
 - Visit the official [External-DNS Releases](https://github.com/kubernetes-sigs/external-dns/releases).
 - Review all versions between your current and target release.
 - Pay attention to:
-  - **Breaking changes** (flags, CRD fields, provider behaviors). Not all changes could be captured as breaking changes.
-  - **Deprecations**
-  - **Provider-specific updates**
-  - **Bug fixes**
+    - **Breaking changes** (flags, CRD fields, provider behaviors). Not all changes could be captured as breaking changes.
+    - **Deprecations**
+    - **Provider-specific updates**
+    - **Bug fixes**
 
 > ⚠️ Breaking CLI flag or annotation changes are common in `0.x` releases.
 
@@ -31,9 +31,9 @@ If using Helm:
 
 - Compare your Helm chart version to the version supporting the new app release.
 - Check for:
-  - `values.yaml` structural changes
-  - Default arguments under `extraArgs`
-  - Updates to RBAC, ServiceAccounts, or Deployment templates
+    - `values.yaml` structural changes
+    - Default arguments under `extraArgs`
+    - Updates to RBAC, ServiceAccounts, or Deployment templates
 
 ---