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
Upgrade BE nodes Run the following command to specify a new BE image file, such as starrocks/be-ubuntu:latest:
kubectl -n starrocks patch starrockscluster starrockscluster-sample --type='merge' -p '{"spec":{"starRocksBeSpec":{"image":"starrocks/be-ubuntu:latest"}}}'
Upgrade FE nodes Run the following command to specify a new FE image file, such as starrocks/fe-ubuntu:latest:
kubectl -n starrocks patch starrockscluster starrockscluster-sample --type='merge' -p '{"spec":{"starRocksFeSpec":{"image":"starrocks/fe-ubuntu:latest"}}}'
Note
The upgrade process lasts for a while. You can run the command kubectl -n starrocks get pods to view the upgrade progress.
kubectl -n starrocks get pods
In flight SQL statements may need to be re-submitted to StarRocks due to bouncing the containers during the upgrade process.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Upgrade BE nodes
Run the following command to specify a new BE image file, such as starrocks/be-ubuntu:latest:
Upgrade FE nodes
Run the following command to specify a new FE image file, such as starrocks/fe-ubuntu:latest:
Note
The upgrade process lasts for a while. You can run the command
kubectl -n starrocks get pods
to view the upgrade progress.Note
In flight SQL statements may need to be re-submitted to StarRocks due to bouncing the containers during the upgrade process.
The text was updated successfully, but these errors were encountered: