feat(testing): use kustomize to patch deployments before deploy

[CarterFendley]

Description of your changes:

This PR is a followup to #11284 which removes the kubectl patch commands by introducing a kustomization. This is in attempt to solve #11293, although does not yet address the Tekton side of things.

Feedback wanted:

• Should this new kustomization.yaml be moved to manifests/kustomize/env?

Checklist:

• You have signed off your commits
• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[google-oss-prow]

Hi @CarterFendley. Thanks for your PR.

I'm waiting for a kubeflow 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.

[hbelmiro]

/ok-to-test

Thank you for working on this @CarterFendley.
Looks good. I just left a small suggestion to rename a variable.

Feedback wanted:

Should this new kustomization.yaml be moved to manifests/kustomize/env?

I don't have a strong opinion. In case we decide to move, we should move it to a new test directory and include this directory in the paths that trigger tests. If we leave them where they are, we don't need to change anything else?

@HumairAK @DharmitD thoughts?

[DharmitD]

I don't have a strong opinion. In case we decide to move, we should move it to a new test directory and include this directory in the paths that trigger tests. If we leave them where they are, we don't need to change anything else?

+1, no need to move as such, but if we decide to move it, make sure to create a new test directory and also move the overlays directory too.

[CarterFendley]

The recent additions to the PR move the contents of scripts/deploy/github to .github/resources/ manifests have been seperated in to two different directories. This structure was suggested in slack here.

• .github/resources/manifests/argo
• .github/resources/manifests/tekton

There is some similarity between the Argo testing kustomization and the Tekton ones, but as per discussion in that slack thread, tekton will be tracked by #11292 and not handled in this PR.

[rimolive]

/rerun-all

[hbelmiro]

@CarterFendley can you please rebase?

[hbelmiro]

/lgtm

@rimolive @DharmitD can you take another look?

[rimolive]

/lgtm

The tests passed in the new paths

[DharmitD]

/Approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DharmitD

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:

• .github/OWNERS [DharmitD]
• scripts/OWNERS [DharmitD]

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