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.

Sign up for GitHub

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

Jump to bottom

The update steps for the pelorus operator should be clear including PV retention #960

Open
1 task done
mpryc opened this issue Apr 28, 2023 · 0 comments
Open
1 task done

The update steps for the pelorus operator should be clear including PV retention #960

mpryc opened this issue Apr 28, 2023 · 0 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@mpryc
Copy link
Collaborator

mpryc commented Apr 28, 2023

OpenShift version

Not related to OpenShift

Problem description

Currently we do have documentation how to create Pelorus instances, but it's lacking clear information about 2 day operations (updates&upgrades) including retaining PV/Thanos stored data.

Steps to reproduce

  1. Go to the https://pelorus.readthedocs.io/en/v2.0.9/
  2. Try to find information how to recreate Pelorus instance with updated configuration
  3. Try to find information if PV is preserved across updates

Current behavior

lack of such information

Expected behavior

clear steps and informations on the 2 day operations

Code of Conduct

  • I agree to follow Pelorus's Code of Conduct
@mpryc mpryc added kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mpryc