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.

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

Multi Cluster cost monitoring using Kubecost, AMP and AMG #49

Open
elamaran11 opened this issue Jul 11, 2023 · 5 comments
Open

Multi Cluster cost monitoring using Kubecost, AMP and AMG #49

elamaran11 opened this issue Jul 11, 2023 · 5 comments
Assignees
Labels

Comments

@elamaran11
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Multi Cluster cost monitoring using Kubecost, AMP and AMG

Describe the solution you'd like
https://aws.amazon.com/blogs/containers/multi-cluster-cost-monitoring-using-kubecost-with-amazon-eks-and-amazon-managed-service-for-prometheus/

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@github-actions
Copy link

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

Copy link

github-actions bot commented Jan 9, 2024

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Jan 9, 2024
@elamaran11 elamaran11 removed the stale label Jan 9, 2024
@elamaran11 elamaran11 assigned iamprakkie and unassigned rameshv29 Feb 13, 2024
Copy link

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

Copy link

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

Copy link

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants