eks-prow-build-cluster: Remove the KubeCost deployment

[xmudrii]

We didn't manage to utilize KubeCost to gather data about ProwJobs because ProwJobs are non-managed Pods (e.g. not part of a ReplicaSet/Deployment) and this is not supported well by KubeCost. For that reason, gathering data required a lot of effort and we got similar data to what we have in our dashboards.

@koksay proposed that we remove the KubeCost deployment from the EKS Prow build cluster, so I'm created a ticket to track that.

/priority important-longterm /area infra/aws /area infra /sig k8s-infra

[koksay]

I created PR #7234

[xmudrii]

We need to figure out if/when we want to remove the S3 bucket used by KubeCost: https://github.com/kubernetes/k8s.io/pull/7234#discussion_r1738204849

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[xmudrii]

@koksay Is this done?

[koksay]

Yes, except for the S3 buckets (prod and canary), they're still not removed. Should I remove them and close this issue?

[xmudrii]

@koksay Yes, let's clean up fully, we don't use it any longer and I don't expect that we'll need that data.

[koksay]

@xmudrii ok, I removed the S3 buckets and policies on both prod and canary environments.

[xmudrii]

@koksay Thanks a lot! /close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

@koksay Thanks a lot! /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-sigs/prow repository.