Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add monitoring for RuntimeClass usage #73058

Closed
tallclair opened this issue Jan 18, 2019 · 5 comments
Closed

Add monitoring for RuntimeClass usage #73058

tallclair opened this issue Jan 18, 2019 · 5 comments
Labels
area/monitoring kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Milestone
v1.14

Comments

@tallclair
Copy link
Member

RuntimeClass went to alpha in 1.12, but lacks good monitoring coverage. Prior to promoting the feature to beta (currently targeting v1.14), we need to have monitoring for the feature.

/sig node
/kind bug
/area monitoring
@tallclair tallclair added the kind/bug Categorizes issue or PR as related to a bug. label Jan 18, 2019
@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. area/monitoring labels Jan 18, 2019
@tallclair
Copy link
Member Author

/assign @haiyanmeng
/milestone v1.14

@k8s-ci-robot
Copy link
Contributor

@tallclair: GitHub didn't allow me to assign the following users: haiyanmeng.

Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @haiyanmeng
/milestone v1.14

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.

@k8s-ci-robot k8s-ci-robot added this to the v1.14 milestone Jan 18, 2019
@tallclair tallclair added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jan 18, 2019
@WanLinghao
Copy link
Contributor

/cc

@haiyanmeng haiyanmeng mentioned this issue Jan 30, 2019
Merged
@haiyanmeng haiyanmeng mentioned this issue Feb 7, 2019
Merged
@nikopen
Copy link
Contributor

nikopen commented Mar 1, 2019

/assign @haiyanmeng

@k8s-ci-robot
Copy link
Contributor

@nikopen: GitHub didn't allow me to assign the following users: haiyanmeng.

Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @haiyanmeng

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/monitoring kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
v1.14
Development

No branches or pull requests
4 participants
@WanLinghao @k8s-ci-robot @tallclair @nikopen