Implement Upgrade Suggestions for Kafka Cluster Creation in the Confluent CLI

[danielayaz]

trafficstars

Release Notes

Breaking Changes

• PLACEHOLDER

New Features

• PLACEHOLDER

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.
• [ ] 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.
• [ ] 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.
• [ ] 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

Added a feature-flagged upgrade suggestion that appears after creating a Basic Kafka cluster, encouraging users to upgrade to Standard. The suggestion is shown to 85% of organizations and includes specific limitations of Basic clusters with a direct upgrade command.

Blast Radius

If the feature flag service is unavailable or the upgrade suggestion fails, users will simply not see the suggestion message. No core functionality is affected - users can still create and use their clusters normally.

References

https://confluentinc.atlassian.net/browse/CLI-3502 https://app.launchdarkly.com/projects/cli/flags/cli.basic-to-standard-cluster-upgrade-suggestion/targeting?env=production&env=test&selected-env=production

Test & Review

Feature flag ON:

Feature flag OFF:

[confluent-cla-assistant[bot]]

: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.}

[danielayaz]

Curious as to how acceptance testing works for this kind of scenario where you're doing an A/B test (some percent of orgs will see a certain output in the CLI vs. others)