KEP-1753 Deprecate Kubernetes system components logs sanitization

[husky-parul]

Placeholder PR for updating the website documentation to remove references to the Kubernetes system components logs sanitization feature. The proposal for the deprecation of the feature was discussed at SIG Instrumentation and ack from SIG Security: https://groups.google.com/g/kubernetes-dev/c/xhQuwdd2Smw/m/L_EyHKbDAAAJ

• enhancement issue Kubernetes system components logs sanitization enhancements#1753 (comment)
• kubernetes PR Deprecate dynamic log sanitization kubernetes#107207

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit	870d126
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/623cb65147193a00096d0a99

[k8s-ci-robot]

Welcome @husky-parul!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[ehashman]

/lgtm
for SIG Instrumentation

do we need to remove any other instances of e.g. the command line flag in component docs?

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 7dbacf138eb949410f3d2f024d699c77e60efecf

[chrisnegus]

A quick search shows the experimental-logging-sanitization flag showing up in these files in the command-line-tools-reference: kube-controller-manager.md, kube-scheduler.md, and kube-apiserver.md. I believe they are auto-generated, but I'm not sure if the feature docs just go away when the related feature is removed. Maybe someone from sig-docs can provide some insight.

[mehabhalodiya]

@kubernetes/sig-docs-en-reviews Please have some insights on this!

[pohly]

A quick search shows the experimental-logging-sanitization flag showing up in these files in the command-line-tools-reference: kube-controller-manager.md, kube-scheduler.md, and kube-apiserver.md. I believe they are auto-generated, but I'm not sure if the feature docs just go away when the related feature is removed. Maybe someone from sig-docs can provide some insight.

I asked about that in one of my previous PRs and was told that those other pages are indeed auto-generated and do not need to be edited. Therefore this PR here should be complete. Can we merge it? I need to make further changes to that page.

/assign @savitharaghunathan

For approval.

[pohly]

@husky-parul : please remove the draft flag.

[mehabhalodiya]

enhancement ref: kubernetes/enhancements#1753
/assign @chrisnegus
/sig instrumentation

[chrisnegus]

/lgtm

[nate-double-u]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nate-double-u

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/OWNERS [nate-double-u]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment