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.

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

Remove usage of offensive language from user-guide #698

Merged
merged 1 commit into from
Feb 16, 2021
Merged
Changes from all commits
Commits
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: 6 additions & 6 deletions docs/user-guide/102-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,7 @@ status:
```

As seen in the output, the configuration is indeed applied and there is a bond
available with two NICs used as its slaves.
available with two NICs used as its ports.

## Removing interfaces

Expand Down Expand Up @@ -294,10 +294,10 @@ kubectl delete nncp bond0-eth1-eth2

Another maybe surprising behavior is, that by removing an interface, original
configuration of the node interfaces is not restored. In case of the bonding it
means that after it is deleted, its slave NICs won't come back up, even if they
had previously configured IP address. The operator is not owning the interfaces
and does not want to do anything that is not explicitly specified, that's up to
the user.
means that after it is deleted, its ports won't come back up as standalone
ports, even if they had previously configured IP address. The operator is not
owning the interfaces and does not want to do anything that is not explicitly
specified, that's up to the user.

`NodeNetworkState` shows that both of the NICs are now down and without any IP
configuration.
Expand Down Expand Up @@ -330,7 +330,7 @@ status:
type: ethernet
```

In order to configure IP on previously enslaved NICs, apply a new Policy:
In order to configure IP on previously attached NICs, apply a new Policy:

<!-- When updating following example, don't forget to update respective attached file -->

Expand Down