cluster-registry-sync-manager-0.1.0

Cluster Registry is a Rest API representing the source of record for all Kubernetes clusters in the infrastructure fleet. All clusters are automatically registered, and the information is accurately reflected in the Cluster Registry using a client-server architecture.

cluster-registry-client-0.3.0

Cluster Registry is a Rest API representing the source of record for all Kubernetes clusters in the infrastructure fleet. All clusters are automatically registered, and the information is accurately reflected in the Cluster Registry using a client-server architecture.

v1.5.8

1.5.8

cluster-registry-api

• Chargeback - Swagger docs (#175)

cluster-registry-client

• Chargeback - Swagger docs (#175)

helm-chart-v0.2.7

Cluster Registry is a Rest API representing the source of record for all Kubernetes clusters in the infrastructure fleet. All clusters are automatically registered, and the information is accurately reflected in the Cluster Registry using a client-server architecture.

v1.5.7

1.5.7

cluster-registry-api

• Make chargeback fields as optional (#167)
• fix(deps): update module github.com/go-jose/go-jose/v3 to v4 (#162)
• fix(deps): update module github.com/onsi/ginkgo to v2 (#161)
• fix(deps): update module github.com/go-jose/go-jose/v3 to v4 (#157)
• fix(deps): update module github.com/onsi/ginkgo to v2 (#158)
• fix(deps): update k8s.io/utils digest to fe8a2dd (#151)
• fix(deps): update module github.com/go-logr/logr to v1.4.2 (#152)
• Add renovate.json (#134)
• dependabot(deps): bump github.com/labstack/echo/v4 from 4.11.4 to 4.12.0 (#141)
• dependabot(deps): bump github.com/onsi/gomega from 1.32.0 to 1.33.1 (#145)
• dependabot(deps): bump github.com/prometheus/client_golang (#146)
• dependabot(deps): bump github.com/testcontainers/testcontainers-go (#147)
• dependabot(deps): bump github.com/aws/aws-sdk-go from 1.51.16 to 1.53.10 (#150)

cluster-registry-client

• Make chargeback fields as optional (#167)
• fix(deps): update module github.com/go-jose/go-jose/v3 to v4 (#162)
• fix(deps): update module github.com/onsi/ginkgo to v2 (#161)
• fix(deps): update module github.com/go-jose/go-jose/v3 to v4 (#157)
• fix(deps): update module github.com/onsi/ginkgo to v2 (#158)
• fix(deps): update k8s.io/utils digest to fe8a2dd (#151)
• fix(deps): update module github.com/go-logr/logr to v1.4.2 (#152)
• Add renovate.json (#134)
• dependabot(deps): bump github.com/labstack/echo/v4 from 4.11.4 to 4.12.0 (#141)
• dependabot(deps): bump github.com/onsi/gomega from 1.32.0 to 1.33.1 (#145)
• dependabot(deps): bump github.com/prometheus/client_golang (#146)
• dependabot(deps): bump github.com/testcontainers/testcontainers-go (#147)
• dependabot(deps): bump github.com/aws/aws-sdk-go from 1.51.16 to 1.53.10 (#150)

helm-chart-v0.2.6

Cluster Registry is a Rest API representing the source of record for all Kubernetes clusters in the infrastructure fleet. All clusters are automatically registered, and the information is accurately reflected in the Cluster Registry using a client-server architecture.

v1.5.6

1.5.6

cluster-registry-api

• dependabot(deps): bump golang.org/x/net from 0.22.0 to 0.24.0 (#131)
• dependabot(deps): bump github.com/aws/aws-sdk-go from 1.51.11 to 1.51.16 (#132)

cluster-registry-client

• Fix extra metrics handler (#135)
• dependabot(deps): bump golang.org/x/net from 0.22.0 to 0.24.0 (#131)
• dependabot(deps): bump github.com/aws/aws-sdk-go from 1.51.11 to 1.51.16 (#132)

helm-chart-v0.2.5

Cluster Registry is a Rest API representing the source of record for all Kubernetes clusters in the infrastructure fleet. All clusters are automatically registered, and the information is accurately reflected in the Cluster Registry using a client-server architecture.

v1.5.5

1.5.5

cluster-registry-api

• Add NamespaceProfileInfraType field (#130)

cluster-registry-client

• Add NamespaceProfileInfraType field (#130)

helm-chart-v0.2.4

Cluster Registry is a Rest API representing the source of record for all Kubernetes clusters in the infrastructure fleet. All clusters are automatically registered, and the information is accurately reflected in the Cluster Registry using a client-server architecture.