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

[MIG-485] Document new helper annotations (BSL/VSL owner & original reclaim policy) #545

Open
eriknelson opened this issue Jan 8, 2021 · 2 comments
Assignees

Comments

@eriknelson
Copy link
Contributor

1.4.0 will be adding two utility annotations that should be documented both upstream and downstream:

  1. A customer reported an issue where MTC was installed used a bit, then uninstalled and reinstalled. A previous BSL was still around that contained stale credentials, but it was unclear which install this actually originated from. We've added an annotation to indicate which entity created certain resources so that they can be traced and we can more easily identify a case like this while debugging. Scott Seago Could you fill in the specifics for this one, I'm blanking on exactly which resources would be marked with the relation, and from where. Updated details in comment.

  2. From BZ: Bug 1906730 - PV policy has changed after running a migration using the "move" action

We'll create an annotation for any PVC where we modify the policy, but we won't actually modify the policy post-migration. Reverting the policy post-migration brings with it the risk that rollback will delete user data. We don't want that, but we want to provide users with the information necessary to manually restore the pre-migration policy. To do this we want to add an annotation indicating the previous policy any time we modify policy as part of a migration action.

@apinnick
Copy link

@eriknelson @sseago
Will this be ready in time for 1.4.0?

@apinnick
Copy link

I started downstream documentation. PR: openshift/openshift-docs#28994

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants