Cluster Keeper v1.0.2

• Throttling messages are reduced and performance improved (#36)
• Proper permissions for user's ~/.kube/config file are maintained (#35)
• ck creds will always output up-to-date credentials and will avoid waking a hibernating cluster to do so (#38 and #17)
• Several small bugs fixes and enhancements are delivered (#28, #29, #31, #34)

Cluster Keeper v1.0.1

• Fixes a formatting issue for ck list claims output in the HIBERNATE column (#24)
• Prevents the ck with command from invoking internal functions
• Allows initial Cluster Keeper setup when logged in as kube:admin (#27)
• Avoids conflicts with the CRD clusterclaims.cluster.open-cluster-management.io (#28)
• Fixes ck get pool to resolve the ClusterPool correctly (#29)
• Resolves an issue where the file provided by ck kubeconfig contains unresolved references to deleted temporary files (#30)
  • If you have such a file, you can restore it by running ck creds -r [CLAIMNAME]

And to top it all off, Cluster Keeper gets a new adorable mascot—a hibernating bear hugging a cluster (#25)!

Hello, Cluster Keeper!

This CLI has been renamed to Cluster Keeper.

If you were using a previous version, you must follow the migration steps.

1. Make sure all users of the ClusterPool suspend use of the CLI during migration.
2. With v0.9, run cm list claims and save the output. You will need to know which ClusterClaims have scheduled hibernation enabled and which have locks.
3. Update to v1.0.0. If using a symlink or alias for cm, update it to ck.
4. For each ClusterClaim with the schedule enabled, run ck enable-schedule CLAIM.
5. For each lock, run ck lock -i LOCKNAME CLAIM
6. Notify all users of the ClusterPool to update to v1.0.0 or newer.

Goodbye, Cluster Manager!

This is the last version of Cluster Manager. The CLI will be renamed to Cluster Keeper to avoid confusion with other projects.