This is documentation for the next version of Grafana k6 documentation. For the latest stable release, go to the latest version.
Upgrade the k6 Operator
This guide explains how to upgrade the k6 Operator, depending on your installation method. Before upgrading, make sure to read the release notes to know what changed and if any breaking changes happened.
k6 Operator installed with bundle
If you installed the k6 Operator with
bundle, you can usually upgrade by re-running the kubectl apply
command with the latest bundle file. However, this won’t remove resources that are no longer present in the new bundle. To avoid leaving outdated resources in your cluster, follow these steps:
Download the version of
bundle.yaml
you originally used and save it asold.bundle.yaml
.Delete the old installation:
kubectl -f old.bundle.yaml delete
Download the latest bundle and install it:
curl https://raw.githubusercontent.com/grafana/k6-operator/main/bundle.yaml > bundle.yaml kubectl apply -f bundle.yaml
Save the latest bundle as your new
old.bundle.yaml
for future upgrades:cp bundle.yaml old.bundle.yaml
Note
Always review the release notes and compare the new
bundle.yaml
with your previous version before upgrading.
Split the bundle for long-term maintenance
Bundle installation is quick, but not always flexible for long-term maintenance. You can split the bundle into separate manifest files and manage them with Kustomize or a GitOps workflow. For inspiration, refer to the run-tests.sh script in the k6 Operator repository.
k6 Operator installed with Helm
If you installed the k6 Operator with Helm, upgrade with these commands:
helm repo update
helm upgrade k6-operator grafana/k6-operator
k6 Operator installed with Makefile
If you installed the k6 Operator with a Makefile, upgrade with these commands:
git clone https://github.com/grafana/k6-operator && cd k6-operator
git checkout <LATEST_RELEASE_TAG>
make deploy
Replace <LATEST_RELEASE_TAG>
with the latest release tag from the k6 Operator releases.
Caution
Make sure to switch to the tagged commit before running
make deploy
. If you runmake deploy
from the latest commit of themain
branch, you may end up with a broken installation, because themain
branch isn’t guaranteed to be stable.
This method is similar to the split bundle approach, but it’s closer to development mode and requires Golang and Kustomize to be installed.