cli icon indicating copy to clipboard operation
cli copied to clipboard

[CLI-3394] Configurable Max-eCKU

Open cqin-confluent opened this issue 3 months ago • 9 comments
trafficstars

Release Notes

Breaking Changes

  • PLACEHOLDER

New Features

  • Add a new field of max-ecku to the Kafka Cluster resource, where with each cluster type (Basic, Standard, Enterprise, Freight) users can optionally override the default Confluent-set max eCKU limit with a custom value

Bug Fixes

  • PLACEHOLDER

Checklist

  • [x] I have successfully built and used a custom CLI binary, without linter issues from this PR.
  • [x] I have clearly specified in the What section below whether this PR applies to Confluent Cloud, Confluent Platform, or both.
  • [x] I have verified this PR in Confluent Cloud pre-prod or production environment, if applicable.
  • [x] I have verified this PR in Confluent Platform on-premises environment, if applicable.
  • [x] I have attached manual CLI verification results or screenshots in the Test & Review section below.
  • [x] I have added appropriate CLI integration or unit tests for any new or updated commands and functionality.
  • [x] I confirm that this PR introduces no breaking changes or backward compatibility issues.
  • [x] I have indicated the potential customer impact if something goes wrong in the Blast Radius section below.
  • [x] I have put checkmarks below confirming that the feature associated with this PR is enabled in:
    • [ ] Confluent Cloud prod
    • [x] Confluent Cloud stag
    • [ ] Confluent Platform
    • [ ] Check this box if the feature is enabled for certain organizations only

What

This feature allows users to set a custom max-ecku value for their v2 clusters (Basic, Standard, Enterprise, and Freight). By doing so, Confluent customers gain more control over cluster scaling.

Context: Currently, the number of eCKUs that the customer is billed for dynamically changes. Our existing customers are limited by their cluster scaling up to a max eCKU (default limit) value set by Confluent. This feature offers customers autonomy to explicitly define their scale for clusters of types Basic, Standard, Enterprise, and Freight, similar to what’s already supported for Dedicated clusters.

Blast Radius

Confluent Cloud customers who are using confluent kafka cluster subcommands will be impacted.

References

JIRA CLI-3394 Feature Request 1-pager

Test & Review

CLI Testing and Verification

cqin-confluent avatar Aug 14 '25 04:08 cqin-confluent

:tada: All Contributor License Agreements have been signed. Ready to merge.
Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.

Failed

  • 67.10% Coverage on New Code (is less than 80.00%)

Analysis Details

3 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 3 Code Smells

Coverage and Duplications

  • Coverage 67.10% Coverage (78.10% Estimated after merge)
  • Duplications No duplication information (0.00% Estimated after merge)

Project ID: cli

View in SonarQube

Failed

  • 0.00% Coverage on New Code (is less than 80.00%)

Analysis Details

3 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 3 Code Smells

Coverage and Duplications

  • Coverage 0.00% Coverage (0.00% Estimated after merge)
  • Duplications No duplication information (0.00% Estimated after merge)

Project ID: cli

View in SonarQube

Failed

  • 79.50% Coverage on New Code (is less than 80.00%)

Analysis Details

3 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 3 Code Smells

Coverage and Duplications

  • Coverage 79.50% Coverage (78.10% Estimated after merge)
  • Duplications No duplication information (0.00% Estimated after merge)

Project ID: cli

View in SonarQube

Failed

  • 79.50% Coverage on New Code (is less than 80.00%)

Analysis Details

3 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 3 Code Smells

Coverage and Duplications

  • Coverage 79.50% Coverage (78.20% Estimated after merge)
  • Duplications No duplication information (0.00% Estimated after merge)

Project ID: cli

View in SonarQube

Failed

  • 79.50% Coverage on New Code (is less than 80.00%)

Analysis Details

3 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 3 Code Smells

Coverage and Duplications

  • Coverage 79.50% Coverage (78.20% Estimated after merge)
  • Duplications No duplication information (0.00% Estimated after merge)

Project ID: cli

View in SonarQube

Failed

  • 62.40% Coverage on New Code (is less than 80.00%)

Analysis Details

6 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 6 Code Smells

Coverage and Duplications

  • Coverage 62.40% Coverage (78.10% Estimated after merge)
  • Duplications No duplication information (0.00% Estimated after merge)

Project ID: cli

View in SonarQube

Failed

  • 72.60% Coverage on New Code (is less than 80.00%)

Analysis Details

5 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 5 Code Smells

Coverage and Duplications

  • Coverage 72.60% Coverage (78.10% Estimated after merge)
  • Duplications No duplication information (0.00% Estimated after merge)

Project ID: cli

View in SonarQube

Failed

  • 71.00% Coverage on New Code (is less than 80.00%)

Analysis Details

5 Issues

  • Bug 0 Bugs
  • Vulnerability 0 Vulnerabilities
  • Code Smell 5 Code Smells

Coverage and Duplications

  • Coverage 71.00% Coverage (78.20% Estimated after merge)
  • Duplications No duplication information (0.00% Estimated after merge)

Project ID: cli

View in SonarQube