kubectl debug: change default profile and remove legacy profile

[mochizuki875]

At v1.32, the legacy profile is the default profile for kubectl debug.
However, a deprecation warning message is displayed after kubernetes/kubernetes#127230 has been merged and the user document says that legacy profile is deprecated as follows:

If you don't specify --profile, the legacy profile is used by default, but it is planned to be deprecated in the near future. So it is recommended to use other profiles such as general.

I think we should make some profile(e.g. general) default and remove the legacy profile in the near future.

According to Deprecating a feature or behavior:

Rule kubernetes/kubernetes#7: Deprecated behaviors must function for no less than 1 year after their announced deprecation.

Therefore the path seems to be as follows:

• Make general profile default: v1.33 or v1.34
• Remove legacy profile: At the earliest v1.35, or later

/sig cli

[mochizuki875]

/cc @ardaguclu
/cc @verb

[mochizuki875]

According to KEP-1441, the auto profile will become the default profile in the future.
However, the auto profile is currently WIP(#120687) and I think the general profile is suitable as an interim default because it has generic properties.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mpuckett159]

Sounds like a good plan
/remove-lifecycle stale
/triage accepted

[mochizuki875]

/assign