NOTE: This directory has some data and scripts to make test ease,but not automatically tested. To run these test cases, you probably need to modify these scripts. In the future, we will integrate these test cases to github workflow.
we use the following tools for test:
- use kind to create a kubernetes cluster.
- use kustomize to create the resources of each case.
- use helm to test our helm chart.
This script will do the following things:
- install a kubernetes cluster using kind.
- deploy the crd and starrocks operator to the cluster by version.
- deploy the StarRocksCluster resource to the cluster defined in './cluster'.
run the script:
bash install.sh v1.7.0
This is used to compare the resources of starrocks cluster created by the operator.
NOTE: you must run install.sh
first, and collect the resources of the cluster.
e.g.
bash diff.sh starrockscluster-sample v1.6.1 v1.7.0 >/tmp/diff.data
For every release, we will add some cases to test the new features.
In v1.7.0/cases
- test cases for operator。we use
kustomize
to create the resources of each case, and use thekubectl kustomize . | kubectl apply -f-
to deploy the resources. It makes test ease, but not automatically tested.mount_configmaps
: mount configmaps to starrocks cluster.mount_secrets
: mount secrets to starrocks cluster.support_fileds
: add the new added support fields of starrocks cluster.
- test cases for helm chart。We use customized values.yaml to render the helm chart, and check the correctness.
modify_start_configmap
: modify the start configmap of starrocks cluster, and expect the related pod will be restarted.operator_support_mode_fields
: add annotations, nodeSelector, tolerations to operator. use zsh to runcheck.sh
.init_password
: init password for starrocks cluster.install_uninstall
: install and uninstall the starrocks cluster by helm.set_cluster_by_chart
: set the starrocks cluster by modify the values.yaml, not modify the StarRocksCluster resource directly.