Update 8.0 breaking change template to gather information on how to programmatically detect it. (#82905)

This commit is contained in:
CJ Cenizal 2020-11-09 11:56:56 -08:00 committed by GitHub
parent 76fd29a452
commit 729631a76d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -30,6 +30,8 @@ requesting the breaking change to be surfaced in the Upgrade Assistant.
<!-- e.g. Based on telemetry data, roughly 75% of our users will need to make changes to x. -->
<!-- e.g. A majority of users will need to make changes to x. -->
**How can we programmatically determine whether the cluster is affected by this breaking change?**
**What can users do to address the change manually?**
<!-- If applicable, describe the manual migration steps and/or link to available docs. -->