There are some pain points that could be addressed if possible:
[ ] manually CRD update is required, this could be a pitfall even in case of fresh deployment of v0.9.0 operator
[ ] upgrade path from v0.8.0(v2.5.x) to v0.9(v2.5.x) seems to be not possible due to the CRD change, it will force the end-user to run production v0.8.0 to a redeployment
Thanks :)
PS. great job on the v0.9.0 on rolling upgrade support!
There are some pain points that could be addressed if possible:
Thanks :) PS. great job on the v0.9.0 on rolling upgrade support!