added files for ginkgo version and testrunner-image-sha

[SaumyaBhushan]

What this PR does / why we need it:

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

added files for ginkgo version and testrunner-image-sha

How Has This Been Tested?

Checklist:

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

Does my pull request need a release note?

Any user-visible or operator-visible change qualifies for a release note. This could be a:

• CLI change
• API change
• UI change
• configuration schema change
• behavioral change
• change in non-functional attributes such as efficiency or availability, availability of a new platform
• a warning about a deprecation
• fix of a previous Known Issue
• fix of a vulnerability (CVE)

No release notes are required for changes to the following:

• Tests
• Build infrastructure
• Fixes for unreleased bugs

For more tips on writing good release notes, check out the Release Notes Handbook

PLACE RELEASE NOTES HERE

[k8s-ci-robot]

@SaumyaBhushan: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-ci-robot]

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

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: SaumyaBhushan
Once this PR has been reviewed and has the lgtm label, please assign rikatz for approval by writing /assign @rikatz in a comment. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-triage-robot]

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla
/easycla

[SaumyaBhushan]

/check-cla
/easycla

[rikatz]

Suggestion (@longwuyuan @strongjz @SaumyaBhushan )

As we are getting more and more of this situation of required software/versions, we should have all of this probably on a yaml file or json file.

With that, during the build we can use tools like jq/yq to fetch version, URL, checksum, etc as required

@strongjz was working on something like that, probably we can align how this will look like (on Slack) and have a single place with all the required softwares instead of creating individual files for each stuff.

[SaumyaBhushan]

Oh ! I got your point @longwuyuan . This makes sense. let me work on that.

[longwuyuan]

Oops, @rikatz @strongjz @SaumyaBhushan @tao12345666333, Saw Ricardo's comments just now. Sorry.

I agree that we should have one file as per Ricardo's comment. Waiting to see messages on ingress-nginx-dev channel in slack

[strongjz]

Something like this file https://github.com/kubernetes/ingress-nginx/pull/9291/files#diff-674c4bc0d26e5898f3326ba71ff5800922119a10f73eebbc0cafb743e29b66ee