feat: merge hybrid clusters into cluster cmd#86
Merged
Davidonium merged 15 commits intomainfrom Mar 31, 2026
Merged
Conversation
listing cloud providers and regions
the flags that were missing to the update command
hybrid cloud clusters
generic for this code
This was referenced Mar 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merge hybrid cluster commands into the
clustercommandThis PR unifies the
hybrid clustersubcommand tree with the mainclustercommand, eliminating a parallel command hierarchy and giving all clusters (cloud-hosted and hybrid) a single, consistent interface.What changed
Command structure
hybrid clustersubcommand entirely (internal/cmd/hybrid/cluster*.godeleted)packagesubcommands to the root (qcloud package listinstead ofqcloud cluster package list)cluster create,cluster update,cluster describe, andcluster listnow handle both cloud-hosted and hybrid clusters transparentlyFlag coverage
cluster createandcluster updatenow accept the full set of hybrid-specific flags:--service-type,--node-selector,--toleration,--topology-spread-constraint,--annotation,--pod-label,--service-annotation,--reserved-cpu-percentage, storage class flags, TLS flags, audit logging flags, and moreCode organization
internal/cmd/cluster/hybrid_helpers.goundiffableFlagsvariable identifies flags with complex nested values that can only show(changed)in restart prompts