To:
CC:

Hi, I'm jira-bot, Percona's Jira automation tool. I've detected that someone from
Percona has made an edit to the Summary field of an issue that you reported.

I'm not sentient (yet) so I'm not sure whether the person fixed a typo, changed
a few words, or completely rewrote the text. In any case, it is Percona Engineering's
intention to make the Summary and Description of an issue as accurate as possible
so that we're fixing the actual problem you're encountering, and to avoid
misunderstandings about symptoms and causes.

If the current Summary does not accurately reflect the problem you are reporting,
or if you feel the change was otherwise inappropriate in some way, please add a
new comment explaining things and we'll address it as soon as we can.

This message will be added only once per issue, regardless of how many times
the Summary is edited.

message-code:summary-edited

I can confirm the workaround works... I also agree it does not resemble like proper solution

While we can certainly do what you suggest as a workaround, it is just a workaround. Is there any intention to address the root cause?

Hi ,

CR object should have API version inside the annotation, it is set by kubectl by default, but if we use direct API calls it should be included manually.

you can create object from "kubectl apply" command and get object content with the next command

or please find the same field content in the upgrade doc