-
Notifications
You must be signed in to change notification settings - Fork 139
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
PMM-11226 OLM Known issues #1835
Conversation
Co-authored-by: Diogo Recharte <diogo.recharte@percona.com>
Co-authored-by: Diogo Recharte <diogo.recharte@percona.com>
Co-authored-by: Diogo Recharte <diogo.recharte@percona.com>
Co-authored-by: Diogo Recharte <diogo.recharte@percona.com>
docs/dbaas/olm.md
Outdated
install-9rxvz percona-server-mongodb-operator.v1.13.1 Manual false | ||
install-mghbh percona-server-mongodb-operator.v1.13.1 Manual false | ||
``` | ||
It seems like both install plans are for PSMDB but examining the install plans individually can shed some light on the matter: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this sentence is required.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion, it is necessary. It describes the actual issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rasika-chivate can we keep this or can you help me to rephrase it?
In my opinion it is necessary because it describes the root cause of the problem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we rephrase to "Although both install plans seem to be for PSMDB, it's worth examining each separately:"
docs/dbaas/olm.md
Outdated
- percona-xtradb-cluster-operator.v1.12.0 | ||
``` | ||
So, only when getting the install plan details in yaml or json format we can see which operators are being handled by the install plan. | ||
The short version `kubectl get installplans` will show only the first operator in the list and this can be confusing and misleading. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we put this as a note?
Co-authored-by: Rasika Chivate <95711051+rasika-chivate@users.noreply.github.com>
Co-authored-by: Rasika Chivate <95711051+rasika-chivate@users.noreply.github.com>
Co-authored-by: Rasika Chivate <95711051+rasika-chivate@users.noreply.github.com>
Co-authored-by: Rasika Chivate <95711051+rasika-chivate@users.noreply.github.com>
Co-authored-by: Rasika Chivate <95711051+rasika-chivate@users.noreply.github.com>
Co-authored-by: Rasika Chivate <95711051+rasika-chivate@users.noreply.github.com>
PMM-0
Updated docs for OLM known issues.
Relevant information in RedHat:
How can Operators be updated independently from each other? Here
Subscription emits InstallPlan containing update to unrelated operator/clusterServiceVersion #1082
CSV required CRDs are resolved from an unpredictable catalog #1076