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
Is this a BUG REPORT or FEATURE REQUEST?:
Feature update
Stork currently has support for Couchbase and with a recent update to the Couchbase Operator in version 2.1, we added a hibernate {true|false} field along with an associated event that should make it easier for Stork to completely stop a CouchbaseCluster, so it can be un-hibernated at a later date (possibly replicated to another location by Stork).
Per discussion with @disrani-px and some others a few months back, it'd be great to update Stork to use this hibernate and the associated event.
Is this a BUG REPORT or FEATURE REQUEST?:
Feature update
Stork currently has support for Couchbase and with a recent update to the Couchbase Operator in version 2.1, we added a hibernate {true|false} field along with an associated event that should make it easier for Stork to completely stop a CouchbaseCluster, so it can be un-hibernated at a later date (possibly replicated to another location by Stork).
Per discussion with @disrani-px and some others a few months back, it'd be great to update Stork to use this hibernate and the associated event.
See the hibernation details in the docs, including the specific part of our custom resource to modify.
The text was updated successfully, but these errors were encountered: