Kops - Migrate kops DO jobs to community-owned prow clusters

[rifelpet]

The issue says DigitalOcean jobs should be migrated to the trusted cluster. This migrates one of kops' 6 DigitalOcean jobs to the new cluster.

/cc @ameukam
Can you confirm these secrets are present in the new cluster?

test-infra/config/jobs/kubernetes-sigs/cluster-api-provider-digitalocean/cluster-api-provider-digitalocean-presets.yaml

Lines 8 to 10 in e69c6b0

	secretKeyRef:
	name: cluster-api-provider-digitalocean-token
	key: DIGITALOCEAN_ACCESS_TOKEN

test-infra/config/jobs/kubernetes/kops/kops-presets-do.yaml

Lines 8 to 10 in e69c6b0

	secretKeyRef:
	name: spaces-digitalocean-s3
	key: access-key

test-infra/config/jobs/kubernetes/kops/kops-presets-do.yaml

Lines 25 to 27 in e69c6b0

	secret:
	defaultMode: 0400
	secretName: kops-e2e-do-ssh-key

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rifelpet

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:

• config/jobs/kubernetes/kops/OWNERS [rifelpet]

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

[rifelpet]

If the secrets do exist then I'll move the job to this repo path:

test-infra/config/tests/jobs/jobs_test.go

Lines 325 to 328 in e69c6b0

	func TestK8sInfraTrusted(t *testing.T) {
	jobsToFix := 0
	const trusted = "k8s-infra-prow-build-trusted"
	trustedPath := path.Join(*jobConfigPath, "kubernetes", "sig-k8s-infra", "trusted") + "/"

[ameukam]

Secrets are currently not present. Still working with CNCF to get them migrated.

[k8s-triage-robot]

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

This bot triages 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 PR is closed

You can:

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

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

/lifecycle stale

[rifelpet]

/remove-lifecycle stale

[ameukam]

@rifelpet Now kubernetes/k8s.io#6967 is merged, we can proceed with this.

[ameukam]

/lgtm

[k8s-ci-robot]

@rifelpet: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key kops-periodics-misc.yaml using file config/jobs/kubernetes/kops/kops-periodics-misc.yaml
• key kops-presubmits.yaml using file config/jobs/kubernetes/kops/kops-presubmits.yaml

In response to this:

The issue says DigitalOcean jobs should be migrated to the trusted cluster. This migrates one of kops' 6 DigitalOcean jobs to the new cluster.

/cc @ameukam
Can you confirm these secrets are present in the new cluster?

test-infra/config/jobs/kubernetes-sigs/cluster-api-provider-digitalocean/cluster-api-provider-digitalocean-presets.yaml

Lines 8 to 10 in e69c6b0

	secretKeyRef:
	name: cluster-api-provider-digitalocean-token
	key: DIGITALOCEAN_ACCESS_TOKEN

test-infra/config/jobs/kubernetes/kops/kops-presets-do.yaml

Lines 8 to 10 in e69c6b0

	secretKeyRef:
	name: spaces-digitalocean-s3
	key: access-key

test-infra/config/jobs/kubernetes/kops/kops-presets-do.yaml

Lines 25 to 27 in e69c6b0

	secret:
	defaultMode: 0400
	secretName: kops-e2e-do-ssh-key

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-sigs/prow repository.

[rifelpet]

@upodroid @ameukam I confirmed these jobs are working in the new cluster: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/e2e-kops-do-calico-gossip/1813195507388911616