You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're building all images for k6-operator under the prefix ghcr.io/grafana/operator. This might be confusing since Grafana has other operators (which are not hosted on ghcr.io, AFAIK, so there is no conflict yet). Still, it's best if we change the prefix for images to something like ghcr.io/grafana/k6-operator.
Once implemented, this change somewhat forces people to adjust their setups around the k6-operator and in their Dockerfiles if they're building from our runner image. So if someone has opinions to share, they're welcome to.
Suggested Solution (optional)
No response
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered:
Feature Description
We're building all images for k6-operator under the prefix
ghcr.io/grafana/operator
. This might be confusing since Grafana has other operators (which are not hosted onghcr.io
, AFAIK, so there is no conflict yet). Still, it's best if we change the prefix for images to something likeghcr.io/grafana/k6-operator
.Once implemented, this change somewhat forces people to adjust their setups around the k6-operator and in their Dockerfiles if they're building from our runner image. So if someone has opinions to share, they're welcome to.
Suggested Solution (optional)
No response
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered: