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
{{ message }}
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.
OpenEBS has a set of K8s Deployments which are typically control plane based services for OpenEBS
It will be good to place these (optionally, depends on customer environments/requirements) on control plane specific K8s Nodes.
This will ensure non-interference with data plane & application plane K8s Nodes
How to do this ?
Taint the K8s Nodes for controller plane services
Ensure this is an optional feature for the deployments where this is not applicable
Ensure this is an optional feature for the deployments where customer does not want this
Might want to build a Tool / Daemon / CLI that looks into existing K8s deployment, accepts/assumes admin entries, generates these yaml based operators & runs them as well.
Might want to break this into a series of smaller tasks/issues
Related Issues
The text was updated successfully, but these errors were encountered:
Added a bash script to test cstor volume covering both success and
failure scenarios.
1. Test to check successful creation and deletion of a cstor volume.
2. Test to check if the volume creation fails when the requested replicas are more than available pools.
3. Test to check if volume is writeable when all the replica pools are restarted.
4. Test to check if the volume is writeable when the target pod is restarted.
Reference: https://docs.google.com/document/d/15Ecf1ORhTeflCfrrkF-NB08727X9tUbYgGQxj2WP0_w/edit?usp=sharing
Signed-off-by: Prince Rachit Sinha <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST
Why is this required?
How to do this ?
Tool / Daemon / CLI
that looks into existing K8s deployment, accepts/assumes admin entries, generates these yaml based operators & runs them as well.Related Issues
The text was updated successfully, but these errors were encountered: