✨ deprecate flag component-config

[laxmikantbpandhare]

this will fix one of the requirements from #2782

This fix will mark the flag component-config as deprecated and throw the warning to the user whenever user tries to use it.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: laxmikantbpandhare
Once this PR has been reviewed and has the lgtm label, please assign jmrodri for approval by writing /assign @jmrodri in a comment. For more information see:The Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @laxmikantbpandhare. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[camilamacedo86]

HI @laxmikantbpandhare,

Before deprecating IMHO we need to have the solution which we will deprecate it for.
So, first, we need to create the plugin then we can go there and say we are deprecating this flag in favour of using the plugin. We also will need to update the tutorial to let users know that.

[camilamacedo86]

/hold
Until we have the other solution in place

[laxmikantbpandhare]

HI @laxmikantbpandhare,

Before deprecating IMHO we need to have the solution which we will deprecate it for. So, first, we need to create the plugin then we can go there and say we are deprecating this flag in favour of using the plugin. We also will need to update the tutorial to let users know that.

@camilamacedo86 - Yes, I am working on it and let it be on hold until we have a plugin for it.

[laxmikantbpandhare]

HI @laxmikantbpandhare,
Before deprecating IMHO we need to have the solution which we will deprecate it for. So, first, we need to create the plugin then we can go there and say we are deprecating this flag in favor of using the plugin. We also will need to update the tutorial to let users know that.

@camilamacedo86 - Yes, I am working on it and let it be on hold until we have a plugin for it.

@camilamacedo86 - PR is ready for review - #2944

[laxmikantbpandhare]

/assign @jmrodri

[laxmikantbpandhare]

these got closed automatically as head of the my repo got deleted. I will raise PR once again.