ADD "disable_specific_metrics" which can remove specific metric by name or regex

[Alexbyy]

#2769
This param is a denyList which named "disable_specific_metrics". Comma-separated list of metrics not to be enabled.It can remove specific metric by name or regex.

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[k8s-ci-robot]

Hi @Alexbyy. Thanks for your PR.

I'm waiting for a google 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.

[Alexbyy]

@googlebot I signed it!

[iwankgb]

This code seems to be copied from kube-state-metrics but misses licence requirements (Apache 2 requires you to state when code from a project is used elsewhere and kube-state-metrics uses Apache 2).
I added some comments too.

[Alexbyy]

Would you tell me How can I triger the pull-cadvisor-e2e check? It's always waiting for status to be reported
@iwankgb
Many thanks!

[iwankgb]

/ok-to-test

[iwankgb]

@bobbypage I consider this work to be complete. Can you review, please?

[iwankgb]

LGTM

[bobbypage]

Couple small comments. Can you please also squash this PR? Thanks!

[Alexbyy]

Couple small comments. Can you please also squash this PR? Thanks!

I have done these requests,review it, please!
And could you tell me why these six tests didn't be triggered?It's status is not "in progress"

[bobbypage]

Couple small comments. Can you please also squash this PR? Thanks!

I have done these requests,review it, please!
And could you tell me why these six tests didn't be triggered?It's status is not "in progress"

I think that's somehow related to #2818 which dropped github actions on 1.14. Not sure, why it's still showing up, but the important thing is the 1.15 / 1.16 variants.

[bobbypage]

thanks for the updates. Can you please also send a followup PR to update the docs https://github.com/google/cadvisor/blob/master/docs/runtime_options.md with the new flag as well? Thanks!