-
Notifications
You must be signed in to change notification settings - Fork 80
Weekly Master Builds
Guy Margalit edited this page Jul 2, 2021
·
6 revisions
Weekly builds of the core and operator images are pushed to:
- https://hub.docker.com/r/noobaa/noobaa-core/tags
- https://hub.docker.com/r/noobaa/noobaa-operator/tags
There are currently two sets of version builds which are being pushed to those repos: master branch and the 5.8 release branch. Each build is tagged with the date in the form of YYYYMMDD
Operator CLIs are also built weekly and have a corresponding timestamp and version to the matching core and operator images.
Download the operator CLI:
curl 'https://noobaa-operator-cli.s3.amazonaws.com/noobaa-linux-master-20210701' > noobaa
chmod +x noobaa
alias noobaa=./noobaa # or you can keep using ./noobaa
You should have a kubernetes cluster, and kubectl configured to use it, and then use the CLI to deploy (to the noobaa namespace in this example):
noobaa install -n noobaa \
--noobaa-image='noobaa/noobaa-core:master-20210701' \
--operator-image='noobaa/noobaa-operator:master-20210701'
We suggest setting the current namespace to noobaa so you don’t need to add -n noobaa
to all kubectl / noobaa commands:
kubectl config set-context --current --namespace noobaa
To upgrade already installed:
For Operator:
kubectl patch deployment noobaa-operator --patch '{"spec": {"template": {"spec": {"containers": [{"name": "noobaa-operator","image": "noobaa/noobaa-operator:master-20210701"}]}}}}'
For Core/Endpoints:
kubectl patch noobaa noobaa --patch '{"spec": {"image": "noobaa/noobaa-core:master-20210701"}}' --type="merge"