Merge branch 'devel' into ovn-ic

.github/workflows/build.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out the repository
-        uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608
+        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11
         with:
           fetch-depth: 0
 

.github/workflows/linting.yml

@@ -38,7 +38,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out the repository
-        uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608
+        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11
 
       - name: Run markdown-link-check
         uses: gaurav-nelson/github-action-markdown-link-check@d53a906aa6b22b8979d33bc86170567e619495ec
@@ -53,7 +53,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out the repository
-        uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608
+        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11
       - name: Run markdownlint
         uses: nosborn/github-action-markdown-cli@9b5e871c11cc0649c5ac2526af22e23525fa344d
         with:
@@ -66,7 +66,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out the repository
-        uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608
+        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11
       - name: Run yamllint
         uses: ibiqlik/action-yamllint@2576378a8e339169678f9939646ee3ee325e845c
         with:

.github/workflows/periodic.yml

@@ -16,7 +16,7 @@ jobs:
       issues: write
     steps:
       - name: Check out the repository
-        uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608
+        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11
 
       - name: Run markdown-link-check
         uses: gaurav-nelson/github-action-markdown-link-check@d53a906aa6b22b8979d33bc86170567e619495ec

.github/workflows/publish.yml

@@ -16,7 +16,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out the repository
-        uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608
+        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11
         with:
           fetch-depth: 0
 

src/content/community/releases/_index.en.md

@@ -5,6 +5,48 @@ weight = 40
 +++
 <!-- markdownlint-disable no-duplicate-header -->
 
+## v0.16.1/v0.16.2 (November 7, 2023)
+
+* The Globalnet controller now employs Kubernetes leader election to ensure proper continuity during fail-over and avoid potential race
+  conditions.
+* The Gateway leader election was enhanced to not restart the pod when leadership is lost to avoid possible data path disruption.
+* Fixed an issue in Service Discovery where stale endpoint IPs, corresponding to services that no longer exist, were returned from DNS
+  queries.
+* Sockets from the host are mounted through their parent directory, which ensures that the sockets themselves aren't replaced by directories
+  (which prevents OVN components from starting). Additionally, stray directories are cleaned up at startup. This fixes the known issue with
+  upgrades involving OVN, as documented in the known issues section for v0.16.0.
+
+## v0.15.3 (November 3, 2023)
+
+* The `subctl diagnose` command has been enhanced to check for potential firewall issues that may be blocking ESP traffic
+  and will provide an appropriate error message.
+* Submariner now explicitly enables forwarding on the interfaces that it creates to support forwarding even when
+  global forwarding on the node is turned off.
+* Enhanced Calico CNI detection now includes searching for calico-node CNI pods when the calico-config map is
+  not detected.
+* Submariner now explicitly configures dpddelay when initiating IPsec connections to prevent excessively frequent
+  liveness probes.
+* Service Discovery will now publish DNS records for pods that are not ready based on the setting of the `publishNotReadyAddresses`
+  flag on the service.
+* The CNI detection method in Submariner Operator is now improved to detect the Flannel CNI, even when the Flannel configMap
+  is missing from the cluster.
+* Submariner now ensures that the IPsec control socket is created before initiating connection requests, and also
+  automatically retries connections in response to errors reported by the 'whack' command.
+* The pod CIDR detection logic now ensures that the node's `podCIDR` is exclusively used for single-node deployments.
+* The Submariner gateway now retries reading local node information on startup to reduce pod restarts if the Kubernetes API server is
+  temporarily unavailable.
+* Reduced data path downtime with Libreswan cable driver when gateway pod restarts.
+
+## v0.14.7 (October 17, 2023)
+
+* Submariner now explicitly enables forwarding on the interfaces that it creates to support forwarding even
+  when global forwarding on the node is turned off.
+* Submariner now ensures that the IPsec control socket is created before initiating connection requests, and also
+  automatically retries connections in response to errors reported by the 'whack' command.
+* The Submariner gateway now retries reading local node information on startup to reduce pod restarts if the Kubernetes API server is
+  temporarily unavailable.
+* Reduced data path downtime with Libreswan cable driver when gateway pod restarts.
+
 ## v0.16.0 (October 2, 2023)
 
 ### New features

src/content/getting-started/quickstart/_index.en.md

@@ -5,7 +5,6 @@ weight = 20
 +++
 
 * [Sandbox Environment (kind)](kind)
-* [K3s](k3s)
 * [Managed Kubernetes](managed-kubernetes)
   * [Google (GKE)](managed-kubernetes/gke)
   * [Rancher](managed-kubernetes/rancher)

src/content/getting-started/quickstart/external/_index.md

@@ -48,9 +48,6 @@ In addition to providing connectivity, the source IP of traffic is also preserve
     | cluster-b |10.42.0.0/24  |10.43.0.0/16  |
 
     Note that we will use Globalnet in this guide, therefore overlapping CIDRs are supported.
-    One of the easiest way to create this environment will be to deploy two K3s clusters by the steps described
-    [here](https://submariner.io/getting-started/quickstart/k3s/) until "Deploy cluster-b on node-b",
-    with modifying deploy commands to just `curl -sfL https://get.k3s.io | sh -` to use default CIDR.
 
 {{% notice note %}}
 In this configuration, global IPs are used to access between the gateway node and non-cluster hosts,
@@ -79,7 +76,7 @@ subctl deploy-broker --kubeconfig kubeconfig.cluster-a --globalnet
 
 When Submariner joins a cluster to the broker via the `subctl join` command, it chooses a node on which to install the
 gateway by labeling it appropriately. By default, Submariner uses a worker node for the gateway; if there are no worker
-nodes, then no gateway is installed unless a node is manually labeled as a gateway. Since we are deploying k3s all-in-one
+nodes, then no gateway is installed unless a node is manually labeled as a gateway. Since we are deploying all-in-one
 nodes, there are no worker nodes, so it is necessary to label the single node as a gateway. By default, the node name is
 the hostname. In this example, the hostnames are "cluster-a" and "cluster-b", respectively.
 

src/content/operations/deployment/subctl/_index.en.md

@@ -76,7 +76,7 @@ contains the following details:
 | Flag                                  | Description
 |:--------------------------------------|:---------------------------------------------------------------------------------------------------|
 | `--repository` `<string>`             | The repository from where the various Submariner images will be sourced (default `quay.io/submariner`)
-| `--version` `<string>`                | Image version (default image tag "devel")
+| `--version` `<string>`                | Image version (defaults to the subctl version)
 | `--components <strings>`              | Comma-separated list of components to be installed - any of `service-discovery`,`connectivity`. The default is: `service-discovery`,`connectivity`
 | `--globalnet`                         | Enable support for overlapping Cluster/Service CIDRs in connecting clusters (default disabled)
 | `--globalnet-cidr-range` `<string>`   | Global CIDR supernet range for allocating GlobalCIDRs to each cluster (default "242.0.0.0/8")
@@ -161,7 +161,7 @@ deployment.
 | Flag                                    | Description
 |:----------------------------------------|:----------------------------------------------------------------------------|
 | `--repository` `<string>`               | The repository from where the various Submariner images will be sourced (default `quay.io/submariner`)
-| `--version` `<string>`                  | Image version (default image tag "devel")
+| `--version` `<string>`                  | Image version (defaults to the subctl version)
 | `--image-override` `<string>=<string>`  | Component image override. This flag can be used more than once (example: `--image-override=submariner-gateway=quay.io/myUser/submariner-gateway:latest`)
 <!-- markdownlint-enable line-length -->