-
Notifications
You must be signed in to change notification settings - Fork 988
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
Add runtime_class_name to pod #1895
Conversation
Hi @kylecarbs, Thank you for your contribution. I will review your PR this week. A few quick notes for now:
Thanks! |
Signed-off-by: Kyle Carberry <[email protected]>
Hi @kylecarbs, Thank you for updating the pod documentation and adding validation! As you can see, I have added a test for this new attribute. The idea is the following:
This test works in kind and GKE clusters. I couldn't make it work in EKS, so we skip it. Can you please also update P.S.: added a changelog file. Thank you. |
@arybolovlev done! Thank you for adding the tests, I appreciate it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for you contribution, @kylecarbs!🚀 Great job! 😊👍🏻
Approved! 😊 This change will be available in the upcoming release. Please keep an eye on the release notes. Thank you, @kylecarbs! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Signed-off-by: Kyle Carberry [email protected]
Description
This adds
runtime_class_name
to thekubernetes_pod
resource.Acceptance tests
It wasn't clear how we'd add an acceptance test for a custom runtime class without customizing the nodes. Maybe
gvisor
exists on the target nodes? In that case, I'll happily add a test.Release Note
Release note for CHANGELOG:
Community Note