Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Open
xmudrii opened this issue Feb 12, 2024 · 5 comments
Open

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

xmudrii opened this issue Feb 12, 2024 · 5 comments
Assignees
@koksay
Labels
area/infra/gcp Issues or PRs related to Kubernetes GCP infrastructure area/infra Infrastructure management, infrastructure design, code in infra/ priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Milestone
v1.30

Comments

@xmudrii
Copy link
Member

xmudrii commented Feb 12, 2024

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
Copy link
Contributor

@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.

@k8s-ci-robot k8s-ci-robot added this to the v1.30 milestone Feb 12, 2024
@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. area/infra Infrastructure management, infrastructure design, code in infra/ area/infra/gcp Issues or PRs related to Kubernetes GCP infrastructure labels Feb 12, 2024
@koksay
Copy link
Contributor

koksay commented Feb 12, 2024

Commenting, so that it can be assigned to me.

@xmudrii
Copy link
Member Author

xmudrii commented Feb 12, 2024

/assign @koksay

@xmudrii xmudrii mentioned this issue Feb 26, 2024
Merged
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2024
@xmudrii
Copy link
Member Author

xmudrii commented May 20, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@koksay koksay

Labels
area/infra/gcp Issues or PRs related to Kubernetes GCP infrastructure area/infra Infrastructure management, infrastructure design, code in infra/ priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Projects
None yet
Milestone
v1.30
Development

No branches or pull requests
4 participants
@koksay @xmudrii @k8s-ci-robot @k8s-triage-robot