Remove not needed anymore Prow jobs

[Sawthis]

Description

A lot of jobs are generated for each repository defined in the templates/config.yaml

• validate-dockerfiles(hadolint) - Should be migrated to Github actions.
• checkconfig(Validate inrepo prow configs) - Do we need it? I think noone is using InRepo Prow configs.
• pjconfigtest(Run ginkgo suite tests for prowjobs definitions) - Do we need it for other repositories than test-infra?
• pjtester(Schedule prowjobs tests using pjtester) - Won't be needed after migration outside of Prow.
• vpathguard(Run pjtester vpathguard) - Won't be needed after migration outside of Prow.

• presubmit-scanner(Run Gitleaks presubmit scanner to detect commited sensitive data) - Should we migrate it to GH actions and each team should use it?

  80 Prow jobs owned by us:

  Can be deleted after last Kyma release planned for end of February.

• [ ] pre-release-pr-image-guard
• [ ] pre-main-kyma-validate-image-definitions
• [ ] pre-main-kyma-validate-image-existence
• [ ] pre-main-kyma-validate-dockerfiles
• [ ] pull-kyma-checkconfig
• [ ] pull-kyma-pjconfigtest
• [ ] pull-kyma-pjtester
• [ ] pull-kyma-vpathguard
• [ ] post-kyma-release-cluster
• [ ] kyma-whitesource-scan
• [x] hydroform-whitesource-scan
• [ ] reconciler-whitesource-scan
• [x] kyma-2.20-whitesource-scan

• [x] kyma-2.19-whitesource-scan

  Won't be needed after migration outside of Prow.

• [ ] pull-k8s-prow-integration
• [ ] ci-prow-autobump
• [ ] ci-prow-autobump-jobs
• [ ] post-test-infra-deploy-prow
• [ ] pull-test-infra-checkconfig
• [ ] pull-test-infra-pjconfigtest
• [ ] pull-test-infra-pjtester
• [ ] pull-test-infra-vpathguard
• [ ] pre-main-test-infra-validate-generated-files
• [ ] pull-k8s-prow-unit-test
• [ ] ci-k8s-prow-sync-upstream
• [ ] ci-k8s-prow-publish-tag
• [ ] ci-k8s-prow-autobump-testimages
• [ ] post-k8s-prow-build-release
• [ ] post-gencred-refresh-kubeconfigs
  • Refresh kubeconfigs for workload clusters after config change, to be removed with prow
• [ ] ci-gencred-refresh-kubeconfigs
  • Refresh kubeconfigs for workload clusters after config change, to be removed with prow
• [ ] pull-slack-bot-checkconfig
  • validation of prowjobs in slack-bot repository, to be removed with prow
• [ ] gcloud-ssh-keys-cleaner
  • cleans os-login ssh keys on gcp project, not needed after prow and workloads project deletion
  • [ ] orphaned-disks-cleaner
    • cleans orphaned disks on gcp project, not needed after prow and workloads project deletion
• [ ] orphaned-ips-cleaner
  • cleans orphaned ips on gcp project, not needed after prow and workloads project deletion
• [ ] orphaned-clusters-cleaner
  • cleans orphaned clusters on gcp project, not needed after prow and workloads project deletion
• [ ] orphaned-vms-cleaner
  • cleans orphaned vms on gcp project, not needed after prow and workloads project deletion
• [ ] orphaned-loadbalancer-cleaner
  • cleans orphaned lbs on gcp project, not needed after prow and workloads project deletion
• [ ] orphaned-dns-cleaner
  • cleans orphaned dns on gcp project, probably not needed after prow and workloads project deletion

Reasons

Acceptance Criteria

• [ ] All Prow jobs mentioned in this issue are migrated to Github actions.
• [ ] All Prow jobs mentioned in this issue are removed.

Attachments

https://github.com/kyma-project/test-infra/issues/9470

[github-actions[bot]]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed due to the lack of recent activity. /lifecycle rotten