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

Reference: information about AWS clusters without cost attribution enabled. #4885

Closed
7 of 15 tasks
consideRatio opened this issue Sep 25, 2024 · 1 comment
Closed
7 of 15 tasks
Assignees

Comments

@consideRatio
Copy link
Contributor

consideRatio commented Sep 25, 2024

The following clusters were created without 2i2c.org/cluster-name tag applied to node groups, or other less relevant resources like EKS plugins.

  • catalystproject-africa
  • earthscope
  • gridsst
  • jupyter-health
  • jupyter-meets-the-earth
  • kitware
  • nasa-cryo
  • nasa-ghg
  • nasa-veda
  • openscapes
  • opensci
  • projectpythia
  • smithsonian
  • ubc-eoas
  • victor

This issue is referenced by documentation being written in #4873, where we can check off clusters over time, and should be able to close with the completion of #4878.

@GeorgianaElena
Copy link
Member

While doing #4878 @consideRatio and I discovered that clusters running on k8s 1.29 don't have the 2i2c.org/cluster-name applied to nodegroups, so they qualified for recreating their nodegroups in order for the tag to be picked up (per step 3 of https://infrastructure.2i2c.org/howto/cost-attribution/aws/#practical-steps).

However, k8s 1.29 does set other tags that are also being picked up by our cost allocation dashboard, namely alpha.eksctl.io/cluster-name and kubernetes.io/cluster/{CLUSTER_NAME}

"Or": [
{
"Tags": {
"Key": "alpha.eksctl.io/cluster-name",
"Values": [CLUSTER_NAME],
"MatchOptions": ["EQUALS"],
},
},
{
"Tags": {
"Key": f"kubernetes.io/cluster/{CLUSTER_NAME}",
"Values": ["owned"],
"MatchOptions": ["EQUALS"],
},
},
{
"Tags": {
"Key": "2i2c.org/cluster-name",
"Values": [CLUSTER_NAME],
"MatchOptions": ["EQUALS"],
},
},

This means that the nodegroups weren't recreated this time, so they don't have the 2i2c.org/cluster-name tag, which is fine from a cost attribution point of view because of the other two that are present. As far as we know currently we're not assuming this tag is present on the nodegroups, so this issue can be closed.

Note that once we'll upgrade the k8s version and recreate the nodegroups anyway, the 2i2c.org/cluster-name will be automatically added. So no specific action needs to be taken at this moment. Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants