✨ Add e2e tests scaffolded in default layout

[Lauquik]

Description

adding testing scaffold for the default layout of our project

Test perfoms the follwoing tasks

• Building the Operator Image:
• Loading the Operator Image to Kind:
• Deploying the Controller-Manager:
• Validating Controller-Manager Pod:

Fixes

#3605

[k8s-ci-robot]

Hi @Lauquik. Thanks for your PR.

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

[camilamacedo86]

Great work, but I think we still require some adjusts

• Rebase with master
• Do not change the current e2e tests to try run the sample tests. The e2e tests executed run the e2e tests scaffolds for kubebuilder itself. We need a new GitHub action that will run the sample tests and be configured with kind
• Ensure that the final scaffold has only what is required for end users.

[camilamacedo86]

/ok-to-test

[Lauquik]

@camilamacedo86 i have created a whole new workflow for sample project-v4 and removed the sample-e2e.sh script, is it okay? or require any changes, i'm open to receiving any suggestion and guidance

[camilamacedo86]

Hi @Lauquik,

@camilamacedo86 i have created a whole new workflow for sample project-v4 and removed the sample-e2e.sh script, is it okay? or require any changes, i'm open to receiving any suggestion and guidance

• The samples should continue to be generated as they currently are.
• The existing checks should remain operational in their current form.

That said, to ensure the integrity of our new e2e tests, we need a dedicated GitHub Action. While it's not necessary to test every single sample (and if doing so simplifies the process, that's acceptable), a streamlined approach might be:

1. Set up a new GitHub Action.
2. Have this action install kind.
3. Run the e2e tests that have been scaffolded for example for project-v4.

[camilamacedo86]

Hi @Lauquik

Very terrific great work 🥇
I think we have just a couple of nits to sort out, and then it is good to fly.

[Lauquik]

@camilamacedo86 i think you are right removing the test dir is not the best approach, i will think of some other solution

[Lauquik]

@camilamacedo86 I have modified the scaffolded Makefile to exclude the e2e test when running 'make test,' so there's no need to remove the test directories explicitly

[camilamacedo86]

Great work 🥇
It is great for me so I am approving this one

/approved

Let's give some time to see if others also want to do some review.
If nobody came with a second review or objections we can lgtm this one.

[Kavinjsir]

Great job @Lauquik 👍🏼 The PR Looks good to me!

[camilamacedo86]

/lgtm

It seems good to fly
we can always push improvements and etc in a follow up

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, Kavinjsir, Lauquik

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

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