Remove trailing whitespace from all files

Signed-off-by: kahirokunn <[email protected]>

Author: kahirokunn

.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -11,7 +11,7 @@ body:
         Describe the bug in as much detail as possible.
     validations:
       required: true
-  
+
   - type: dropdown
     id: area
     attributes:
@@ -37,7 +37,7 @@ body:
         How can we reproduce it (as minimally and precisely as possible)?
     validations:
       required: true
-  
+
   - type: input
     id: k0smotron-version
     attributes:

.github/workflows/publish-docs.yml

@@ -96,7 +96,7 @@ jobs:
           make release IMG=quay.io/k0sproject/k0smotron:${STABLE}
           cp install.yaml /tmp/install.yaml
           git checkout gh-pages
-          cp /tmp/install.yaml ${STABLE}/install.yaml 
+          cp /tmp/install.yaml ${STABLE}/install.yaml
           git add ${STABLE}/install.yaml && git update-index --refresh
           git diff-index --quiet HEAD -- || git commit -m "Update install.yaml to ${STABLE}"
           git push origin gh-pages

.github/workflows/release.yml

@@ -129,7 +129,7 @@ jobs:
           asset_path: ./templates/cluster-template.yaml
           asset_name: cluster-template.yaml
           asset_content_type: application/octet-stream
-      
+
       - name: Upload Release Assets - cluster-template-hcp.yaml
         id: upload-release-asset-cluster-template-hcp
         uses: shogo82148/[email protected]

docs/README.md

@@ -16,7 +16,7 @@ Using k0smotron the clusters controlplane and workerplane are truly separated. T
 
 ### Bring your own workers
 
-With k0smotron you can connect worker nodes from ANY infrastructure to your cluster control plane. 
+With k0smotron you can connect worker nodes from ANY infrastructure to your cluster control plane.
 
 ## How does it work
 
@@ -34,7 +34,7 @@ Often when running integration and end-to-end testing for your software running
 
 ### Edge
 
-Running Kubernetes on the network edge usually means running in low resource infrastructure. What this often means is that setting up the controlplane is either a challenge or a mission impossible. Running the controlplane on a existing cluster, on a separate dedicated infrastructure, removes that challenge and let's you focus on the real edge. 
+Running Kubernetes on the network edge usually means running in low resource infrastructure. What this often means is that setting up the controlplane is either a challenge or a mission impossible. Running the controlplane on a existing cluster, on a separate dedicated infrastructure, removes that challenge and let's you focus on the real edge.
 
 Running on the edge often also means large number of clusters to manage. Do you really want to dedicate nodes for each cluster controlplane and manage all the infrastructure for those?
 

docs/capi-aws.md

@@ -1,6 +1,6 @@
 # Cluster API - AWS (Hosted Control Plane)
 
-This example demonstrates how k0smotron can be used with CAPA (Cluster API Provider Amazon Web Services) to deploy 
+This example demonstrates how k0smotron can be used with CAPA (Cluster API Provider Amazon Web Services) to deploy
 a cluster with hosted control plane and workers in AWS.
 
 ## Prerequisites
@@ -115,7 +115,7 @@ spec:
     spec:
       ami:
         # Replace with your AMI ID
-        id: ami-0989fb15ce71ba39e # Ubuntu 22.04 in eu-central-1 
+        id: ami-0989fb15ce71ba39e # Ubuntu 22.04 in eu-central-1
       instanceType: t3.large
       iamInstanceProfile: nodes.cluster-api-provider-aws.sigs.k8s.io # Instance Profile created by `clusterawsadm bootstrap iam create-cloudformation-stack`
       cloudInit:
@@ -146,20 +146,20 @@ Once complete, your command line should display output similar to this:
 ```shell
 % kubectl get cluster,machine
 NAME                                    PHASE         AGE   VERSION
-cluster.cluster.x-k8s.io/k0s-aws-test   Provisioned   16m   
+cluster.cluster.x-k8s.io/k0s-aws-test   Provisioned   16m
 
 NAME                                         CLUSTER        NODENAME   PROVIDERID                                 PHASE         AGE   VERSION
-machine.cluster.x-k8s.io/k0s-aws-test-md-0   k0s-aws-test              aws:///eu-central-1a/i-05f2de7da41dc542a   Provisioned   16m   
+machine.cluster.x-k8s.io/k0s-aws-test-md-0   k0s-aws-test              aws:///eu-central-1a/i-05f2de7da41dc542a   Provisioned   16m
 ```
 
 You can also check the status of the cluster deployment with `clusterctl`:
 ```shell
-% clusterctl describe cluster  
-NAME                                                   READY  SEVERITY  REASON                    SINCE  MESSAGE          
-Cluster/k0s-aws-test                                   True                                       25m                      
-├─ClusterInfrastructure - AWSCluster/k0s-aws-test                                                                             
-├─ControlPlane - K0smotronControlPlane/k0s-aws-test-cp                                                                           
-└─Workers                                                                                                                  
+% clusterctl describe cluster
+NAME                                                   READY  SEVERITY  REASON                    SINCE  MESSAGE
+Cluster/k0s-aws-test                                   True                                       25m
+├─ClusterInfrastructure - AWSCluster/k0s-aws-test
+├─ControlPlane - K0smotronControlPlane/k0s-aws-test-cp
+└─Workers
   └─Other
 ```
 
@@ -169,7 +169,7 @@ k0smotron, running in a management cluster in AWS, supports flexible networking
 If you prefer using an NLB instead of ELB, you must specify annotations for the Service in the `k0smotronControlPlane`. These annotations guide the AWS Cloud Controller Manager (CCM) or the AWS Load Balancer Controller to create the respective services.
 
 ```yaml
- [...] 
+ [...]
   service:
     type: LoadBalancer
     apiPort: 6443
@@ -184,7 +184,7 @@ For scenarios involving Classic ELBs or NLBs without special options, the AWS CC
 If you aim to use the NLB and set the schema to `internal`, the target group attribute `preserve_client_ip.enabled=false` is required due to "hairpinning" or "NAT loopback". In such cases, the AWS CCM cannot be used because it doesn't support setting Target Group Attributes. Therefore, the AWS Load Balancer Controller, which has the ability to set Target Group Attributes, becomes necessary. Follow [this guide](https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html) to install the AWS Load Balancer Controller.
 
 ```yaml
- [...] 
+ [...]
   service:
     type: LoadBalancer
     apiPort: 6443

docs/capi-bootstrap.md

@@ -112,6 +112,6 @@ spec:
     # More details about the aws machine template can be set here
 ```
 
-This example creates a `MachineDeployment` with 2 replicas, using k0smotron as the bootstrap provider. The `infrastructureRef` is used to specify the infrastructure requirements for the machines, in this case, AWS. 
+This example creates a `MachineDeployment` with 2 replicas, using k0smotron as the bootstrap provider. The `infrastructureRef` is used to specify the infrastructure requirements for the machines, in this case, AWS.
 
 Check the [examples](capi-examples.md) pages for more detailed examples how k0smotron can be used with various Cluster API infrastructure providers.

docs/capi-clusterclass.md

@@ -1,6 +1,6 @@
 # ClusterClass
 
-K0smotron supports ClusterClass, a simple way to create many clusters of a similar shape. 
+K0smotron supports ClusterClass, a simple way to create many clusters of a similar shape.
 
 For instance, we will create a ClusterClass that will create a cluster running control plane and worker nodes on DockerMachines:
 
@@ -136,7 +136,7 @@ spec:
           spec:
             api:
               extraArgs:
-                anonymous-auth: "true" # anonymous-auth=true is needed for k0s to allow unauthorized health-checks on /healthz 
+                anonymous-auth: "true" # anonymous-auth=true is needed for k0s to allow unauthorized health-checks on /healthz
 ---
 apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
 kind: DockerMachineTemplate

docs/capi-controlplane-bootstrap.md

@@ -42,7 +42,7 @@ spec:
       spec:
         api:
           extraArgs:
-            anonymous-auth: "true" # anonymous-auth=true is needed for k0s to allow unauthorized health-checks on /healthz 
+            anonymous-auth: "true" # anonymous-auth=true is needed for k0s to allow unauthorized health-checks on /healthz
   machineTemplate:
     infrastructureRef:
       apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
@@ -69,7 +69,7 @@ For a full reference on `K0sControlPlane` configurability see the [reference doc
 **WARNING: Downscaling is a potentially dangerous operation.**
 
 Kubernetes using etcd as its backing store. It's crucial to have a quorum of etcd nodes available at all times. Always run etcd as a cluster of **odd** members.
-    
+
 When downscaling the control plane, you need firstly to deregister the node from the etcd cluster. k0smotron will do it automatically for you.
 
 **NOTE:** k0smotron gives node names sequentially and on downscaling it will remove the "latest" nodes. For instance, if you have `k0smotron-test` cluster of 5 nodes and you downscale to 3 nodes, the nodes `k0smotron-test-3` and `k0smotron-test-4` will be removed.

docs/capi-hetzner.md

@@ -59,7 +59,7 @@ spec:
     apiPort: 6443
     konnectivityPort: 8132
     annotations:
-      load-balancer.hetzner.cloud/location: fsn1 
+      load-balancer.hetzner.cloud/location: fsn1
 ---
 apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
 kind: HetznerCluster
@@ -134,7 +134,7 @@ spec:
 apiVersion: v1
 kind: Secret
 data:
-  hcloud: <base64 encoded token> 
+  hcloud: <base64 encoded token>
 metadata:
   name: hetzner
 ```
@@ -146,7 +146,7 @@ After applying the manifests to the management cluster and confirming the infras
 ```
 % kubectl get cluster,machine
 NAME                                   PHASE         AGE     VERSION
-cluster.cluster.x-k8s.io/hetzer-test   Provisioned   3m51s   
+cluster.cluster.x-k8s.io/hetzer-test   Provisioned   3m51s
 
 NAME                                         CLUSTER        NODENAME   PROVIDERID          PHASE         AGE     VERSION
 machine.cluster.x-k8s.io/hetzner-test-md-0   hetzner-test              hcloud://12345678   Provisioned   3m50s

docs/capi-kubevirt.md

@@ -4,7 +4,7 @@ This example demonstrates how k0smotron can be used with CAPK (Cluster API Provi
 
 ## Preparations
 
-Before starting this example, ensure that you have met the [general prerequisites](capi-examples.md#prerequisites). 
+Before starting this example, ensure that you have met the [general prerequisites](capi-examples.md#prerequisites).
 
 To install the latest stable version of Kubevirt you can run:
 
@@ -155,7 +155,7 @@ After applying the manifests to the management cluster and confirming the infras
 ```bash
 % kubectl get cluster,machine
 NAME                                   PHASE         AGE     VERSION
-cluster.cluster.x-k8s.io/kubevirt-test Provisioned   22h   
+cluster.cluster.x-k8s.io/kubevirt-test Provisioned   22h
 
 NAME                                               CLUSTER         NODENAME                  PROVIDERID                           PHASE     AGE     VERSION
 machine.cluster.x-k8s.io/kubevirt-md-mdvns-l2rxb   kubevirt-test   kubevirt-md-mdvns-l2rxb   kubevirt://kubevirt-md-mdvns-l2rxb   Running   22h     v1.27.4