feat: add annotation to allow to add custom response headers

[cgroschupp]

What this PR does / why we need it:

Because of the CVE-2021-25742, we need a better way to define response headers, when snippets are disabled.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

fixes #7811

How Has This Been Tested?

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.
• Added Release Notes.

Does my pull request need a release note?

Any user-visible or operator-visible change qualifies for a release note. This could be a:

• CLI change
• API change
• UI change
• configuration schema change
• behavioral change
• change in non-functional attributes such as efficiency or availability, availability of a new platform
• a warning about a deprecation
• fix of a previous Known Issue
• fix of a vulnerability (CVE)

No release notes are required for changes to the following:

• Tests
• Build infrastructure
• Fixes for unreleased bugs

For more tips on writing good release notes, check out the Release Notes Handbook

Allow to set custom response headers by annotation

[k8s-ci-robot]

Hi @cgroschupp. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[strongjz]

@cgroschupp This PR looks good so far, can you add an e2e test as well

Here is the annotations e2e https://github.com/kubernetes/ingress-nginx/tree/main/test/e2e/annotations

[strongjz]

/triage accepted
/priority backlog
/kind feature

[cgroschupp]

@strongjz i added the e2e tests.

[cgroschupp]

@pierluigilenoci I rebased the code agian and it is now green.

[pierluigilenoci]

@tao12345666333 The LGTM label is missing.

[pierluigilenoci]

@Gacko @cpanato, could you please take a look?

[tao12345666333]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgroschupp, pierluigilenoci, tao12345666333

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tao12345666333]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Gacko]

/hold

[Gacko]

I thought we committed on not adding any new annotations?

/cc @strongjz @cpanato

[tao12345666333]

This PR has been discussed in our community meeting and slack.

It is only because of the delay in our review that it has been merged now. So sorry 😞

[pierluigilenoci]

Thank you @cgroschupp!!!
And thank you @tao12345666333.