OSSM-2150 rebase our changes on top of vanilla upstream 1.24 (maistra#222)

* Maistra 2.4 changes

* touchups + server side cipher suite deprecations

Signed-off-by: Otto van der Schaaf <[email protected]>

---------

Signed-off-by: Otto van der Schaaf <[email protected]>
Co-authored-by: Otto <[email protected]>

Author: oschaaf

.azure-pipelines/pipelines.yml

@@ -215,6 +215,8 @@ stages:
     pool:
       vmImage: "ubuntu-20.04"
     steps:
+    - bash: .azure-pipelines/cleanup.sh
+      displayName: "Removing tools from agent"
     - template: bazel.yml
       parameters:
         ciTarget: bazel.release
@@ -376,6 +378,8 @@ stages:
     pool:
       vmImage: "ubuntu-20.04"
     steps:
+    - bash: .azure-pipelines/cleanup.sh
+      displayName: "Removing tools from agent"
     - bash: |
         echo "disk space at beginning of build:"
         df -h

.bazelignore

@@ -2,5 +2,6 @@
 api
 examples/grpc-bridge/script
 tools/clang_tools
+test/extensions/quic_listeners/quiche
 tools/dev/src
 .project

.bazelrc

@@ -59,8 +59,6 @@ build:sanitizer --test_tag_filters=-no_san
 
 # Common flags for Clang
 build:clang --action_env=BAZEL_COMPILER=clang
-build:clang --action_env=CC=clang --action_env=CXX=clang++
-build:clang --linkopt=-fuse-ld=lld
 
 # Flags for Clang + PCH
 build:clang-pch --spawn_strategy=local
@@ -417,3 +415,5 @@ build:windows --dynamic_mode=off
 try-import %workspace%/clang.bazelrc
 try-import %workspace%/user.bazelrc
 try-import %workspace%/local_tsan.bazelrc
+
+import %workspace%/maistra/bazelrc

.clang-format

@@ -5,7 +5,6 @@ ColumnLimit: 100
 DerivePointerAlignment: false
 PointerAlignment: Left
 SortIncludes: false
-TypenameMacros: ['STACK_OF']
 ...
 
 ---

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,6 @@
 blank_issues_enabled: false
+
 contact_links:
-- name: "Crash bug"
-  url: https://github.com/envoyproxy/envoy/security/policy
-  about: "Please file any crash bug with [email protected]."
+- name: "Issues"
+  url: https://issues.redhat.com/browse/OSSM
+  about: "Issues for this repository are tracked in Red Hat Jira."

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,17 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: enhancement,triage
-assignees: ''
-
----
-
-*Title*: *One line description*
-
-*Description*:
->Describe the desired behavior, what scenario it enables and how it
-would be used.
-
-[optional *Relevant Links*:]
->Any extra documentation required to understand the issue.

.github/ISSUE_TEMPLATE/non--crash-security--bug.md

@@ -1,49 +0,0 @@
----
-name: Non-{crash,security} bug
-about: Bugs which are not crashes, DoS or other security issue
-title: ''
-labels: bug,triage
-assignees: ''
-
----
-
-**If you are reporting *any* crash or *any* potential security issue, *do not*
-open an issue in this repo. Please report the issue via emailing
-[email protected] where the issue will be triaged appropriately.**
-
-*Title*: *One line description*
-
-*Description*:
->What issue is being seen? Describe what should be happening instead of
-the bug, for example: Envoy should not crash, the expected value isn't
-returned, etc.
-
-*Repro steps*:
-> Include sample requests, environment, etc. All data and inputs
-required to reproduce the bug.
-
->**Note**: The [Envoy_collect tool](https://github.com/envoyproxy/envoy/blob/main/tools/envoy_collect/README.md)
-gathers a tarball with debug logs, config and the following admin
-endpoints: /stats, /clusters and /server_info. Please note if there are
-privacy concerns, sanitize the data prior to sharing the tarball/pasting.
-
-*Admin and Stats Output*:
->Include the admin output for the following endpoints: /stats,
-/clusters, /routes, /server_info. For more information, refer to the
-[admin endpoint documentation.](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
-
->**Note**: If there are privacy concerns, sanitize the data prior to
-sharing.
-
-*Config*:
->Include the config used to configure Envoy.
-
-*Logs*:
->Include the access logs and the Envoy logs.
-
->**Note**: If there are privacy concerns, sanitize the data prior to
-sharing.
-
-*Call Stack*:
-> If the Envoy binary is crashing, a call stack is **required**.
-Please refer to the [Bazel Stack trace documentation](https://github.com/envoyproxy/envoy/tree/main/bazel#stack-trace-symbol-resolution).

.github/ISSUE_TEMPLATE/other.md

@@ -1,20 +0,0 @@
----
-name: Other
-about: Questions, design proposals, tech debt, etc.
-title: ''
-labels: triage
-assignees: ''
-
----
-
-**If you are reporting *any* crash or *any* potential security issue, *do not*
-open an issue in this repo. Please report the issue via emailing
-[email protected] where the issue will be triaged appropriately.**
-
-*Title*: *One line description*
-
-*Description*:
->Describe the issue.
-
-[optional *Relevant Links*:]
->Any extra documentation required to understand the issue.