Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Krzysztof Wilczyński <[email protected]>
  • Loading branch information
saschagrunert and kwilczynski authored Nov 29, 2024
1 parent 0867284 commit acf2d2e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -177,7 +177,7 @@ dnf install -y cri-o kubelet kubeadm kubectl

#### Configure a Container Network Interface (CNI) plugin

CRI-O is capable to work with different [CNI plugins](https://github.com/containernetworking/cni),
CRI-O is capable of working with different [CNI plugins](https://github.com/containernetworking/cni),
which may require a custom configuration. The CRI-O package ships a default
[IPv4 and IPv6 (dual stack) configuration](templates/latest/cri-o/bundle/10-crio-bridge.conflist.disabled)
for the [`bridge`](https://www.cni.dev/plugins/current/main/bridge) plugin,
Expand All @@ -188,7 +188,7 @@ disabled configuration file in `/etc/cni/net.d`:
mv /etc/cni/net.d/10-crio-bridge.conflist.disabled /etc/cni/net.d/10-crio-bridge.conflist
```

The bridge plugin is mainly suitable for single node clusters in CI and testing
The bridge plugin is suitable for single-node clusters in CI and testing
environments. Different CNI plugins are recommended to use CRI-O in production.

#### Start CRI-O
Expand Down

0 comments on commit acf2d2e

Please sign in to comment.