k8s-infra-prow-build: Deploy KubeCost and integrate it with the existing KubeCost installation on EKS

[xmudrii]

We deployed KubeCost on the EKS Prow build cluster recently (#5164). This issue tracks:

• deploying KubeCost on the GKE community Prow build cluster (k8s-infra-prow-build)
• integrating it with the existing KubeCost installation so that we have all information in the single dashboard and API

/assign @koksay /priority important-soon /milestone v1.30 /sig k8s-infra /area infra /area infra/gcp

[k8s-ci-robot]

@xmudrii: GitHub didn't allow me to assign the following users: koksay.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide

In response to this:

We deployed KubeCost on the EKS Prow build cluster recently (#5164). This issue tracks:

• deploying KubeCost on the GKE community Prow build cluster (k8s-infra-prow-build)
• integrating it with the existing KubeCost installation so that we have all information in the single dashboard and API

/assign @koksay /priority important-soon /milestone v1.30 /sig k8s-infra /area infra /area infra/gcp

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.

[koksay]

Commenting, so that it can be assigned to me.

[xmudrii]

/assign @koksay

[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]

/remove-lifecycle stale

[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 I think we decided not to proceed with this one or is it still relevant?

[koksay]

Yes, this is not relevant anymore. I was even thinking about removing Kubecost from the EKS cluster as we have already got the info we needed.

[xmudrii]

@koksay Okay, I'll create a new issue to track that. /close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

@koksay Okay, I'll create a new issue to track that. /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.

[xmudrii]

@koksay I created https://github.com/kubernetes/k8s.io/issues/7226 to track removing KubeCost from eks-prow-build-cluster