-
Notifications
You must be signed in to change notification settings - Fork 806
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
k8s-infra-prow-build: Deploy KubeCost and integrate it with the existing KubeCost installation on EKS #6413
Comments
@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. 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. |
Commenting, so that it can be assigned to me. |
/assign @koksay |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
@koksay I think we decided not to proceed with this one or is it still relevant? |
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. |
@koksay Okay, I'll create a new issue to track that. |
@xmudrii: Closing this issue. 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-sigs/prow repository. |
We deployed KubeCost on the EKS Prow build cluster recently (#5164). This issue tracks:
/assign @koksay
/priority important-soon
/milestone v1.30
/sig k8s-infra
/area infra
/area infra/gcp
The text was updated successfully, but these errors were encountered: