Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: remove mention of enabling KubePrism after v1.6
I noticed in the docs [here](https://github.com/siderolabs/talos/blob/8df5b85ec7e8ca53fd73c9c095ee5c453d5c4e51/website/content/v1.8/kubernetes-guides/network/deploying-cilium.md?plain=1#L241) it mentions enabling the KubePrism feature. However, it mentions enabling the KubePrism feature. However, [here](https://github.com/siderolabs/talos/blob/8df5b85ec7e8ca53fd73c9c095ee5c453d5c4e51/website/content/v1.8/kubernetes-guides/configuration/kubeprism.md?plain=1#L25) the docs mention it's enabled by default since 1.6.. So I was wondering if mention of enabling KubePrism after v1.6 is a mistake? Note it was mentioned several times in the docs v1.5. ``` ❯ rg "kubePrism:" --glob "*deploying-cilium.md" -A1 website/content/v1.8/kubernetes-guides/network/deploying-cilium.md 240: kubePrism: 241- enabled: true website/content/v1.7/kubernetes-guides/network/deploying-cilium.md 240: kubePrism: 241- enabled: true website/content/v1.6/kubernetes-guides/network/deploying-cilium.md 240: kubePrism: 241- enabled: true website/content/v1.5/kubernetes-guides/network/deploying-cilium.md 32: kubePrism: 33- enabled: true -- 56: kubePrism: 57- enabled: true -- 212: kubePrism: 213- enabled: true -- 240: kubePrism: 241- enabled: true -- 264: kubePrism: 265- enabled: true ``` Signed-off-by: Will Bush <git@willbush.dev>
- Loading branch information