adobe/cluster-registry

A lightweight API for maintaining a list of Kubernetes clusters and associated metadata.

cluster-registry's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update module github.com/aws/aws-sdk-go to v1.53.11
• fix(deps): update kubernetes packages to v0.30.1 (k8s.io/api, k8s.io/apimachinery, k8s.io/client-go, k8s.io/component-base)
• fix(deps): update module sigs.k8s.io/controller-runtime to v0.18.3
• fix(deps): update module github.com/go-jose/go-jose/v3 to v4
• fix(deps): update module github.com/onsi/ginkgo to v2
• fix(deps): update module gopkg.in/go-playground/validator.v9 to v10
• fix(deps): update module gopkg.in/yaml.v2 to v3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

dockerfile

cmd/apiserver/Dockerfile

cmd/client/Dockerfile

github-actions

.github/workflows/chart-releaser.yaml

• actions/checkout v4
• helm/chart-releaser-action v1.6.0

.github/workflows/release.yml

• actions/checkout v4
• actions/setup-go v5
• docker/login-action v3

.github/workflows/tests.yml

• actions/checkout v4
• actions/setup-go v5

gomod

go.mod

• go 1.21
• github.com/Azure/go-autorest/autorest/azure/auth v0.5.12
• github.com/aws/aws-sdk-go v1.53.10
• github.com/coreos/go-oidc/v3 v3.10.0
• github.com/evanphx/json-patch/v5 v5.9.0
• github.com/go-jose/go-jose/v3 v3.0.3
• github.com/go-jose/go-jose/v4 v4.0.2
• github.com/go-logr/logr v1.4.2
• github.com/google/uuid v1.6.0
• github.com/gusaul/go-dynamock v0.0.0-20210107061312-3e989056e1e6@3e989056e1e6
• github.com/jinzhu/gorm v1.9.16
• github.com/labstack/echo/v4 v4.12.0
• github.com/labstack/gommon v0.4.2
• github.com/onsi/ginkgo v1.16.5
• github.com/onsi/ginkgo/v2 v2.19.0
• github.com/onsi/gomega v1.33.1
• github.com/prometheus/client_golang v1.19.1
• github.com/stretchr/testify v1.9.0
• github.com/swaggo/echo-swagger v1.4.1
• github.com/swaggo/swag v1.16.3
• github.com/testcontainers/testcontainers-go v0.31.0
• golang.org/x/net v0.25.0
• gopkg.in/go-playground/validator.v9 v9.31.0
• gopkg.in/yaml.v2 v2.4.0
• k8s.io/api v0.29.2
• k8s.io/apimachinery v0.29.2
• k8s.io/client-go v0.29.2
• k8s.io/component-base v0.29.2
• k8s.io/utils v0.0.0-20240502163921-fe8a2dddb1d0@fe8a2dddb1d0
• sigs.k8s.io/controller-runtime v0.17.1
• sigs.k8s.io/yaml v1.4.0

---

• Check this box to trigger a request for Renovate to run again on this repository

Add chargebackBusinessUnit Field to ClusterRegistry

Expected Behaviour / Actual Behaviour

The Ethos Chargeback team would like to add an additional field to ClusterRegistry that defines the appropriate business unit for each cluster. While there is currently a businessUnit field for clusters, there are times when clusters need to have a separate business unit value to separate the cluster's Unit Cost from other clusters that fall under the same business unit umbrella. Chargeback needs to be able to separate the business unit for which part of the business the cluster belongs to from the business unit for how costs are allocated to the cluster.

For example, from an infrastructure point of view, ethos08-prod-va7 is a DX cluster, but from a Chargeback point of view the cluster is a CJA cluster. The Chargeback team would like to have more control over setting this field to align with the Cloud bill and tenant / finance requirements.

Are there any considerations from the Cluster Registry team to have this field added?