add Private Operator Upgrade Policy

[genwhittTTD]

add Private Operator Upgrade Policy, in 4 Private Operator guides plus overview.

[atarassov-ttd]

Curious why this is separated from the Operator Version section - other cloud pages have the two sections next to each other.

[genwhittTTD]

Hi @atarassov-ttd the structure of the AKS doc is different, and the Operator Version section is in the middle of the Deployment section. It'll be great to revisit these docs and make them more parallel. For now, I moved Operator Version up out of the Deployment section so all four docs have these two sections together. They are now both at the top, top heading level, basically -- consistently across all versions. A small step towards consistent structure.

[atarassov-ttd]

I feel like this should go under Private Operator Versions section below. Otherwise it looks out of context.

[genwhittTTD]

@atarassov-ttd done. But then, I wonder if the version table should go first, and then the upgrade policy second, in the main docs? I put the upgrade policy first, to be noticed. But versioning is first, upgrade is second. I will switch those around actually. (done)

[atarassov-ttd]

If upgrade policy is moved here, this note would look redundant. Wonder if the recommendation (without reference to the upgrade policy) should go into the Deprecation Schedule section (where the policy is now).

[genwhittTTD]

Not totally sure I understood this but I updated the wording to refer to the applicable table. I think it's clear. We can do post-release updates if needed.

[atarassov-ttd]

There is no ZIP file for AWS deployments, so this text does not apply.

[genwhittTTD]

Good point, thx. Updated to:

The latest ZIP file is available in the Assets section at the bottom of the linked Release Notes in the following table.

[atarassov-ttd]

Curious why this is commented out?

[genwhittTTD]

@atarassov-ttd good point. It should probably come out -- but we did have this release. The info I was given (LC Confluence page) had it, but if you click through on the link, this artifact does not exist on the page.
If we could provide a different link, we could include this version. Otherwise, we should leave it out.
@clarkxuyang any input?

[clarkxuyang]

At the time of release Q1 2025, aks private operator was in final testing. It is not announced as part of Q1 release.

[atarassov-ttd]

Should we also include projected timelines for the Q4 2025 release?

[genwhittTTD]

To my understanding, we should mention future releases as little as possible -- ideally not at all. I think we should stick with schedules for what we have. Perhaps a KK adjudication.

[atarassov-ttd]

Suggest moving the policy here.

[genwhittTTD]

Hi @atarassov-ttd oops about to publish and just noticed this comment.
I'd previously moved this to below the versions section based on your earlier comment #894 (comment).
The trouble is, the Important note is at the end of the H2 intro and then we have the individual H3 sections for each Private Operator. So it isn't good to interject another H2 section in there. To me, "the versions section" includes the parent and the children.
Given we need to get this out, keeping it as is. But if you take a look and need it moved still, happy to do it as a fast follow.

[atarassov-ttd]

@clarkxuyang there is indeed a ZIP for AWS in the release notes. Is it worthwhile linking it here? Our docs are centered around marketplace experience which does not require the zip. Is zip required only for setup experience outside of marketplace?

[clarkxuyang]

The ZIP is only required for the setup experience outside of the marketplace. The public documentation doesn’t explain how to use it, I feel including the link might cause confusion.