Improve workflow for adding a new Pod IP Block to an existing cluster using update-cluster about docs-pks HOT 3 CLOSED

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

from docs-pks.

@lparis makes sense to add a new use case for "if you run out of IP addresses..." but instead of replacing that section on updating a cluster's network profile, how about just leaving it there, as a general reference? Referring to https://docs.pivotal.io/tkgi/1-8/network-profiles.html#update-profile There are probably other reasons to update an existing cluster's network profile.

If so, I'm thinking we should include or link to that section Limitation: Pod IP Block Changes https://docs.pivotal.io/tkgi/1-8/network-profiles-define.html#change-pod-ips in both the general instrux and the specific New IP Block use case.

from docs-pks.

#1196

from docs-pks.