Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate cluster sub command #7

Open
nirs opened this issue Feb 12, 2025 · 0 comments
Open

Validate cluster sub command #7

nirs opened this issue Feb 12, 2025 · 0 comments
Labels
scheduled Scheduled for next release

Comments

@nirs
Copy link
Member

nirs commented Feb 12, 2025

A DR environment have one or more hubs, and 2 managed clusters. Each cluster type have many components that has to be installed and configured in the right way to make it possible to preform DR flows successfully.

Partial list of possible issues:

  • drpolicy: missing drclusters
  • ramen config: missing or misconfigured
  • mirrorpeer: missing or misconfigured
  • secrets: missing on the hub or managed clusters
  • s3 store: down, failing, not accessible
  • vrc: missing
  • submariner: connectivity issue, globalnet
  • storage: full, broken
  • rbd mirror: down, broken
  • network: cluster is not accessible

The ramenctl tool should inspect all clusters and validate that the all the clusters are correct. The tool should create a report listing all the issues in the clusters, that can be attached easily to a bug tracker.

@nirs nirs added the scheduled Scheduled for next release label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scheduled Scheduled for next release
Projects
None yet
Development

No branches or pull requests

1 participant