🏃extend ci-conformance.sh testing capability

[sayantani11]

/kind feature

Extending ci-conformance.sh testing capability to allow other tests to be run on a CAPZ cluster - a temporary solution until kubernetes-sigs/cluster-api#2826 is fixed.

Describe the solution you'd like

[A clear and concise description of what you want to happen.]
ci-entrypoint.sh will be the new entrypoint for all E2E tests. It can accept k/k master branch or release branches, and has the option to run upstream E2E tests or bring your own E2E tests by appending custom commands to ./scripts/ci-entrypoint.sh.

Anything else you would like to add:

Refer to: kubernetes-sigs/cluster-api-provider-azure#617
https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/scripts/ci-entrypoint.sh
As of now try adding the scripts/ci-entrypoint.sh file, and as we move forward we could see for the rest.

[MadhavJivrajani]

@sayantani11 please ensure that the issue contains sufficient context and information about what exactly needs to be done so that a new contributor can pick it up with almost 0 barrier to entry. The guidelines for good-first-issues can be found here.

/remove-good-first-issue
Please feel free to re-apply once sufficient information has been added.

[sayantani11]

/good-first-issue

[k8s-ci-robot]

@sayantani11:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

[Darshnadas]

Can I take this issue?

[MadhavJivrajani]

/assign @Darshnadas

[sayantani11]

@Darshnadas You will see a PR reference we are looking for something similar, but as of now our main focus will be the ci-entrypoint.sh file. I have attached the reference to the file with latest update. This script is present in CAPZ and we are wanting the same for CAPG. For the variables in the script, you might try having a look at https://github.com/kubernetes-sigs/cluster-api-provider-gcp/blob/main/docs/book/src/topics/prerequisites.md#setup-environment-variables. For the ensure scripts try looking at the hack folder. And for any problems, we can start a thread in Slack if you want.

[PranshuSrivastava]

Can i also work on this issue?

[PranshuSrivastava]

/assign

[Darshnadas]

@sayantani11 Sure, a thread starting in a slack sounds good

[sayantani11]

@PranshuSrivastava as you can see @Darshnadas has claimed the issue, so I think one person will be okay for the PR. You can still browse through the project and see if there are other changes that you could introduce for enhancement of the project. Hope you understand🙂
/unassign @PranshuSrivastava

[PranshuSrivastava]

@sayantani11 Sure, no problem!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Darshnadas]

/remove-lifecycle stale

[mehabhalodiya]

@sayantani11 I would like to work on this if nobody else is doing so.

[mehabhalodiya]

/assign

[sayantani11]

@mehabhalodiya There's a PR but guess that needs improvement, you can still work on it

[mehabhalodiya]

@Darshnadas I see you are working on this. Let me know if you wouldn't, I can continue 🙂

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sayantani11]

/close

[k8s-ci-robot]

@sayantani11: Closing this issue.

In response to this:

/close

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.