We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the env
Kubernetes: v1.30.4-eks-a737599 KubeBlocks: 1.0.0-beta.2 kbcli: 1.0.0-alpha.1
To Reproduce Steps to reproduce the behavior:
k get cluster -A NAMESPACE NAME CLUSTER-DEFINITION TERMINATION-POLICY STATUS AGE default mysql-ninaym Delete Running 4h21m
expose mysql-ninaym failed kbcli cluster expose mysql-ninaym --auto-approve --force=true --type vpc --enable true --components mysql --namespace default error: unsupported expose type: vpc on provider EKS
The same scenario runs well on kb0.9 (eks - the same testing environment) https://github.com/apecloud/kubeblocks/actions/runs/11835055091/job/32978654205
The text was updated successfully, but these errors were encountered:
in KB 1.0, expose ops only support types of [intranet|internet], vpc is deprecated. pr is here:
https://github.com/apecloud/kbcli/pull/467/files#diff-228dfd53d77d777a840a35fc2b711bbf18dafe36a69f44909d62b8adfc1142c6R844
Sorry, something went wrong.
yipeng1030
shanshanying
No branches or pull requests
Describe the env
To Reproduce
Steps to reproduce the behavior:
expose mysql-ninaym failed
kbcli cluster expose mysql-ninaym --auto-approve --force=true --type vpc --enable true --components mysql --namespace default
error: unsupported expose type: vpc on provider EKS
The same scenario runs well on kb0.9 (eks - the same testing environment)
https://github.com/apecloud/kubeblocks/actions/runs/11835055091/job/32978654205
The text was updated successfully, but these errors were encountered: