Merge pull request #5807 from emissary-ingress/flynn/update

Update Envoy, go-control-plane, Go, and dependencies

.github/workflows/check-branch-version.yml

@@ -22,7 +22,7 @@ name: Check branch version
 
 jobs:
   check-branch-version:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     steps:
       - uses: actions/checkout@v3
         with:

.github/workflows/execute-tests-and-promote.yml

@@ -10,7 +10,7 @@ name: job-promote-to-passed
 
 jobs:
   lint: ########################################################################
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       # See docker/base-python.docker.gen
       BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}
@@ -30,7 +30,7 @@ jobs:
         if: always()
 
   generate: ####################################################################
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       # See docker/base-python.docker.gen
       BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}
@@ -78,7 +78,7 @@ jobs:
         if: always()
 
   check-envoy-protos: ####################################################################
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       # See docker/base-python.docker.gen
       BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}
@@ -110,7 +110,7 @@ jobs:
         if: always()
 
   check-envoy-version: #########################################################
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       # See docker/base-python.docker.gen
       BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}
@@ -139,7 +139,7 @@ jobs:
 
   # Tests ######################################################################
   apiext-e2e:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       # See docker/base-python.docker.gen
       BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}
@@ -170,7 +170,7 @@ jobs:
         run: |
           go test -p 1 -parallel 1 -v -tags=apiext ./test/apiext/... -timeout 15m
   check-gotest:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       # See docker/base-python.docker.gen
       BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}
@@ -193,7 +193,7 @@ jobs:
       - uses: ./.github/actions/after-job
         if: always()
   check-pytest:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       # See docker/base-python.docker.gen
       BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}
@@ -249,7 +249,7 @@ jobs:
         with:
           jobname: check-pytest-${{ matrix.test }}
   check-pytest-unit:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       # See docker/base-python.docker.gen
       BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}
@@ -277,7 +277,7 @@ jobs:
       - uses: ./.github/actions/after-job
         if: always()
   check-chart:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       DEV_REGISTRY: ${{ secrets.DEV_REGISTRY }}
       # See docker/base-python.docker.gen
@@ -308,7 +308,7 @@ jobs:
         if: always()
 
   build: #######################################################################
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       DEV_REGISTRY: ${{ secrets.DEV_REGISTRY }}
       # See docker/base-python.docker.gen
@@ -347,7 +347,7 @@ jobs:
   ######################################################################
   ######################### CVE Scanning ###############################
   trivy-container-scan:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     needs: [build]
     steps:
       # upload of results to github uses git so checkout of code is needed
@@ -388,7 +388,7 @@ jobs:
       - check-pytest-unit
       - check-chart
       - trivy-container-scan
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     steps:
       - name: No-Op
         if: ${{ false }}

.github/workflows/generate-base-python.yml

@@ -6,7 +6,7 @@ on:
     - cron: '0 12 * * SUN'
 jobs:
   generate: ####################################################################
-      runs-on: ubuntu-latest
+      runs-on: ubuntu-24.04
       env:
         # See docker/base-python.docker.gen
         BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}

.github/workflows/k8s-e2e.yml

@@ -8,7 +8,7 @@ name: k8s-e2e
 
 jobs:
   acceptance_tests:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     env:
       # See docker/base-python.docker.gen
       BASE_PYTHON_REPO: ${{ secrets.BASE_PYTHON_REPO }}

.github/workflows/promote-ga.yml

@@ -5,7 +5,7 @@ name: promote-to-ga
       - 'v[0-9]+.[0-9]+.[0-9]+'
 jobs:
   promote-to-ga:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     name: promote-to-ga
     env:
       AWS_S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }}
@@ -52,7 +52,7 @@ jobs:
       - uses: ./.github/actions/after-job
         if: always()
   create-gh-release:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     needs: [promote-to-ga]
     name: "Create GitHub release"
     env:

.github/workflows/promote-rc.yml

@@ -6,7 +6,7 @@ name: promote-to-rc
       - 'v[0-9]+.[0-9]+.[0-9]+-dev'
 jobs:
   promote-to-rc:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     name: promote-to-rc
     env:
       AWS_S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }}

.github/workflows/publish-chart.yml

@@ -5,7 +5,7 @@ name: chart-publish
       - 'chart/v*'
 jobs:
   chart-publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     name: chart-publish
     env:
       AWS_S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }}
@@ -45,7 +45,7 @@ jobs:
         if: always()
   chart-create-gh-release:
     if: ${{ ! contains(github.ref, '-') }}
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     needs: [chart-publish]
     name: "Create GitHub release"
     steps:

CHANGELOG.md

@@ -401,7 +401,7 @@ it will be removed; but as it won't be user-visible this isn't considered a brea
   releases, or a `Host` with or without a `TLSContext` as in prior 2.y releases.
 
 - Bugfix: Prior releases of Emissary-ingress had the arbitrary limitation that a `TCPMapping` cannot
-  be used on the same port that HTTP is served on, even if TLS+SNI would make this possible. 
+  be used on the same port that HTTP is served on, even if TLS+SNI would make this possible.
   Emissary-ingress now allows `TCPMappings` to be used on the same `Listener` port as HTTP `Hosts`,
   as long as that `Listener` terminates TLS.
 
@@ -567,7 +567,7 @@ it will be removed; but as it won't be user-visible this isn't considered a brea
   releases, or a `Host` with or without a `TLSContext` as in prior 2.y releases.
 
 - Bugfix: Prior releases of Emissary-ingress had the arbitrary limitation that a `TCPMapping` cannot
-  be used on the same port that HTTP is served on, even if TLS+SNI would make this possible. 
+  be used on the same port that HTTP is served on, even if TLS+SNI would make this possible.
   Emissary-ingress now allows `TCPMappings` to be used on the same `Listener` port as HTTP `Hosts`,
   as long as that `Listener` terminates TLS.