Zenko is the open source multi-cloud data controller: own and keep control of your data on any cloud.
APACHE-2.0 License
Bot releases are hidden (Show)
Published by ssalaues about 6 years ago
helm upgrade <release-name> ./zenko --set redis-ha.enabled=false --timeout 600 && helm upgrade <release-name> ./zenko --set redis-ha.enabled=true
redis-ha
chart. On larger deployments, it's suggested to increase the timeout to prevent early termination of the upgrade.Init:2/3
process. While functionality is still present, it's necessary to resolve this manually
/work-dir/peer-finder -on-start=/init/on-start.sh -service=<release-name>-mongodb-replicaset
Published by ssalaues about 6 years ago
helm dependency build
is no longer a necessary part of the installationhelm upgrade <release-name> ./zenko --set redis-ha.enabled=false --timeout 600 && helm upgrade <release-name> ./zenko --set redis-ha.enabled=true
redis-ha
chart. On larger deployments, it's suggested to increase the timeout to prevent early termination of the upgrade.Init:2/3
process. While functionality is still present, it's necessary to resolve this manually
/work-dir/peer-finder -on-start=/init/on-start.sh -service=<release-name>-mongodb-replicaset
Published by ssalaues about 6 years ago
helm repo add scality https://scality.github.io/charts/
before building/rebuilding any helm dependencies [#246]Zenko/charts/zenko/charts
and rebuild using helm dependency build zenko
as there may be conflicts that occur from charts that have been removed. See #232 #246Full changelog for Zenko and dependencies changes from 1.0.0-RC3 to 1.0.0-RC4 can be found here.
Published by ssalaues about 6 years ago
When upgrading, be sure to clean up the old tarballs in Zenko/charts/zenko/charts
and rebuild using helm dependency build zenko
as there may be conflicts that occur because of the changes in #205.
The dependency on the stable/redis-ha chart can some times have issues due to a race-condition that causes multiple redis-servers to be set to master
. This can be remedied by running kubectl get pod -L redis-role
to get the list of redis-servers with the master role. Then delete any duplicate master pod therefore leaving only 1 redis-server pod with the master label.
Full changelog for Zenko and dependencies changes from 1.0.0-RC2 to 1.0.0-RC3 can be found here.
Published by ssalaues over 6 years ago
Full changelog for Zenko and dependencies changes from 1.0.0-beta to 1.0.0-RC2 can be found here.