Add a janitor periodic job to cleanup stale ec2 instances from the node-e2e-tests service account

[dims]

No description provided.

[dims]

/assign @tzneal @upodroid

[tzneal]

Do the actual cluster nodes run in this account, or just the test launched nodes?

[dims]

@tzneal test launched nodes

[dims]

/hold

cross checking my query

[tzneal]

/lgtm

[upodroid]

I recommend you use the boskos janitor, have a look at maintenance-ci-aws-janitor job

- interval: 1h
  name: maintenance-ci-aws-janitor
  labels:
    preset-service-account: "true"
    preset-aws-ssh: "true"
    preset-aws-credential: "true"
  decorate: true
  spec:
    containers:
    - command:
      - /app
      args:
      - --ttl=2h30m
      - --path=s3://k8s-kops-prow/objs.json
      image: gcr.io/k8s-staging-boskos/aws-janitor:v20230524-a7ef97e
  annotations:
    testgrid-dashboards: sig-testing-maintenance
    testgrid-tab-name: ci-aws-janitor
    description: Deletes old AWS resources

That janitor can target resources by tags after the defined ttl.

https://github.com/kubernetes-sigs/boskos/blob/master/cmd/aws-janitor/main.go

[dims]

@upodroid happy to iterate, i want to start with something simple.

[upodroid]

I'll add it to the todo list

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, tzneal, upodroid

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/OWNERS [dims]

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

[dims]

/hold cancel

[k8s-ci-robot]

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

• key ec2-e2e.yaml using file config/jobs/kubernetes/sig-testing/ec2-e2e.yaml

In response to this:

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.