Reword doc + add API_SERVER_PORT to the template

Signed-off-by: Damien DASSIEU <[email protected]>

Author: damsien

.github/workflows/test-e2e.yml

@@ -10,7 +10,7 @@ jobs:
   test-e2e:
     name: Run on Ubuntu
     runs-on: ubuntu-latest
-    timeout-minutes: 20
+    timeout-minutes: 40
     steps:
       - name: Clone the code
         uses: actions/checkout@v4

docs/scalewaycluster.md

@@ -151,11 +151,11 @@ For more information about private DNS, please refer to the [Understanding Scale
 When creating a `ScalewayCluster`, a "main" Load Balancer is always created.
 It is also possible to specify "extra" Load Balancers to achieve regional redundancy.
 
-#### Front API server port
+#### Frontend API server port
 
-The kube-apiserver Load Balancer's front port can be set at the cluster creation in the `Cluster` object.
+The kube-apiserver Load Balancer's frontend port can be set at the cluster creation in the `Cluster` object.
 
-Here is an example of the main Load Balancer port configuration:
+Here is an example of a Load Balancer frontend port configuration:
 
 ```yaml
 apiVersion: cluster.x-k8s.io/v1beta1
@@ -164,10 +164,10 @@ metadata:
   name: my-cluster
   namespace: default
 spec:
-  ...
+  # ...
   clusterNetwork:
     apiServerPort: 443
-  ...
+  # ...
 ```
 
 - The `apiServerPort` field specifies the port of the Load Balancer frontend that exposes the kube-apiserver(s).

templates/cluster-template.yaml

@@ -4,6 +4,7 @@ metadata:
   name: ${CLUSTER_NAME}
 spec:
   clusterNetwork:
+    apiServerPort: ${API_SERVER_PORT:=null}
     pods:
       cidrBlocks:
         - 10.244.0.0/16