Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

📖 Removed duplicate text block #8729

Merged
merged 1 commit into from
May 23, 2023
Merged

📖 Removed duplicate text block #8729

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions docs/book/src/tasks/experimental-features/cluster-class/change-clusterclass.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,14 +136,10 @@ expect when planning your ClusterClass changes:
is applied to the KCP template in ClusterClass.

- User should expect the Cluster topology to change consistently irrespective of how the change has been
implemented inside the ClusterClass; in other words, if you change a template field "in place", if you
rotate the template referenced in the ClusterClass by pointing to a new template with the same field
changed, or if you change the same field via a patch, the effects on the Cluster are the same.

- Users should expect the Cluster topology to change consistently irrespective of how the change has been
applied to the ClusterClass. In other words, if you change a template field "in place", or if you
rotate the template referenced in the ClusterClass by pointing to a new template with the same field
changed, or if you change the same field via a patch, the effects on the Cluster are the same.
implemented inside the ClusterClass or applied to the ClusterClass. In other words,
if you change a template field "in place", or if you rotate the template referenced in the
ClusterClass by pointing to a new template with the same field changed, or if you change the
same field via a patch, the effects on the Cluster are the same.

See [reference](#reference) for more details.

Expand Down