Versioned static manifests

[afirth]

Generate static manifests compatible with supported K8s versions, rather than just 1.20

What this PR does / why we need it:

Currently the helm templates have handling for different kubernetes versions, but the script to generate static manifests uses the helm default version (currently 1.20).
With this change the existing deploy/static manifests remain at 1.20 so we don't break docs, but additional folders are underneath with an explicit version.

For more background see #8000 and #7810. #8099 is related.

Changes

The only real changes here are in hack/generate-deploy-scripts.sh

1. generate for other supported K8s versions
2. don't delete the 1.20 folder (a hack I put in to make Static manifest generation uses kustomize instead of python #8099 small enough to review)

everything else is the result of running the script.

Types of changes

• New feature (non-breaking change which adds functionality)

Which issue/s this PR fixes

/fixes #7810

How Has This Been Tested?

1. Ran ./generate-deploy-scripts.sh
2. Verified existing manifests updated
3. spot-checked diffs to confirm expected changes present e.g.

$ diff deploy/static/provider/aws/1.19/deploy.yaml deploy/static/provider/aws/deploy.yaml

0a1
> #GENERATED FOR K8S 1.20
367a369,371
>   ipFamilies:
>   - IPv4
>   ipFamilyPolicy: SingleStack
369c373,374
<   - name: http
---
>   - appProtocol: http
>     name: http
373c378,379
<   - name: https
---
>   - appProtocol: https
>     name: https
398c404,405
<   - name: https-webhook
---
>   - appProtocol: https
>     name: https-webhook

1.19 does not have appProtocol or ipFamilies 👍

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
  (docs updates were completed in Static manifest generation uses kustomize instead of python #8099)
• I've read the CONTRIBUTION guide
• [n/a] I have added tests to cover my changes.
• All new and existing tests passed.

[afirth]

/assign @rikatz
9d12bd3 is the script change
6a2a2ce is the manifest generation

boilerplate test broke because I force pushed in the middle but
/test pull-ingress-nginx-boilerplate
anyway

[afirth]

/kind feature

[iamNoah1]

/triage accepted
/priority important-soon

[afirth]

I updated the description too but understand this could be daunting to a reviewer.
The only real changes here are in hack/generate-deploy-scripts.sh

• generate for other supported K8s versions
• don't delete the 1.20 folder (a hack I put in to make Static manifest generation uses kustomize instead of python #8099 small enough to review)
  everything else is the result of running the script.

a reviewer could (untested)

git checkout main
git checkout 6a2a2ce -- ./hack/generate-deploy-scripts.sh
./hack/generate-deploy-scripts.sh

helm, and kustomize must be available (installable with asdf). RELEASE.md was also updated in #8099 with these instructions

[rikatz]

/lgtm
/approve
Thanks

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afirth, rikatz

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 [rikatz]

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

[longwuyuan]

@afirth

https://kubernetes.slack.com/archives/C021E147ZA4/p1646123996592759?thread_ts=1645961964.408979&cid=C021E147ZA4

[afirth]

@longwuyuan docs were merged in #8099 https://github.com/kubernetes/ingress-nginx/blob/main/RELEASE.md#e-edit-the-static-manifests to update the python and ruyaml deps to helm+kustomize

[longwuyuan]

Just hoping to at least convert that word "kustomize" into a link to the customise software website.

[afirth]

👍 go for it