feat(baremetal): Add kustomization.yaml

[haslersn]

With this change, one can use kustomize to deploy ingress-nginx on bare-metal clusters. Example:

# kustomization.yml

namespace: ingress-nginx

bases:
  - github.com/kubernetes/ingress-nginx/deploy/static/provider/baremetal?ref=master

Usage: In the same folder run: $ kubectl apply -k .

How Has This Been Tested?

# kustomization.yml

namespace: ingress-nginx

bases:
  - github.com/haslersn/ingress-nginx/deploy/static/provider/baremetal?ref=baremetal/kustomize

Checklist:

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

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @haslersn!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-nginx has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @haslersn. 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.

[aledbf]

@haslersn we removed kustomize support due to the slowness of the process.
Please check #4156

[haslersn]

@haslersn we remove kustomize support due to the slowness of the process.
Please check #4156

The fixing PR #4159 removed the recommendation to use kustomize, but one could still voluntarily use it. This possibility was removed much later in #5086. I see no reason not to have the possibility.

[aledbf]

This possibility was removed much later in #5086. I see no reason not to have the possibility.

ok, that makes sense.

That said, to accept the PR, please add the kustomization.yaml file to each directory in static/provider adding a comment that the file is provided only with the purpose to support kustomize bases. Something like

# NOTE: kustomize is not supported. This file exists only to be able to reference it from bases
# https://kubectl.docs.kubernetes.io/pages/reference/kustomize.html#bases
# namespace: ingress-nginx
# bases:
#  - github.com/kubernetes/ingress-nginx/deploy/static/provider/baremetal?ref=master

resources:
  - deploy.yaml

[cmluciano]

/ok-to-test

Tests should kick in after you push, I'll try to test this manually now while we await the additional changes

[haslersn]

I force-pushed my changes. However, AWS' deploy-tls-termination.yaml is not supported by the respective kustomization.yaml.

[aledbf]

/lgtm
/approve

[aledbf]

@haslersn thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, haslersn

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

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

[yene]

Could the non kustomize version still be kept around? The change broke my documentation.

[haslersn]

This change did not remove anything. What do you mean by "non kustomize version"?

[yene]

nvm sorry, I open a new ticket