Add docs on how to upgrade the metrics components between versions.

[mwringe]

No description provided.

[mwringe]

Bump, any news on this?

[tnguyen-rh]

@mwringe This is for 3.2 only, right?

[mwringe]

@tnguyen-rh yes, its for when people are moving between 3.1 and 3.2 (since that is the only main version update they have so far). But it will also be required for going between 3.2 and 3.3, etc

[tnguyen-rh]

@mwringe Thanks. For future reference, feel free to add the label branch/enterprise-3.2 directly, and tag me or @openshift/team-documentation to call (more) timely attention to the PR.

[adellape]

@tnguyen-rh Added a milestone.

[mwringe]

Any idea when this will appear in the 3.2 docs? I can see it in the origin docs but not the 3.2 ones.

[bfallonf]

@mwringe Once a PR is merged it's in Origin fairly quickly, but isn't released until the followup label (to double-check if it hits all the CCS standards) is removed and after our weekly async release.

Does this need to be in the Enterprise docs quickly?

[tnguyen-rh]

@mwringe To expand on what @bfallonf said, the to_followup label will be removed once #2234 is merged.

[tnguyen-rh]

@mwringe
Hmm, there is a discrepency between this example (which uses redeploy) and the introductory text (which uses refresh). Which is correct? (I will make the change in #2234.)

[mwringe]

Oops, it should be 'refresh' not 'redeploy' here. Thanks for the catch

[tnguyen-rh]

PR #2234 has rev history and has merged. Removing to_followup label.

[mwringe]

@adellape I still don't see this in the OSE 3.2 docs, this should have been a high priority fix as its essential for anyone updating to OSE 3.2 who had metrics deployed before.

[adellape]

@mwringe It's in the Staging milestone currently, meaning we're currently working on cherry-picking and publishing to OSE docs. I'll bump you when it's live.

[adellape]

@mwringe This is live now for OSE 3.2:

https://docs.openshift.com/enterprise/3.2/install_config/upgrading/manual_upgrades.html#manual-upgrading-cluster-metrics

[mwringe]

@adellape awesome, thanks so much!