-
Notifications
You must be signed in to change notification settings - Fork 1.1k
include workload allowed_annotations in crio config output #9468
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
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: prasad89 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @prasad89. Thanks for your PR. I'm waiting for a cri-o member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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-sigs/prow repository. |
Signed-off-by: prasad89 <vdbhaleraovb@gmail.com>
f578449
to
1cfad5d
Compare
/ok-to-test |
Codecov Report✅ All modified and coverable lines are covered by tests.
Additional details and impacted files@@ Coverage Diff @@
## main #9468 +/- ##
===========================================
- Coverage 67.24% 56.16% -11.08%
===========================================
Files 202 191 -11
Lines 28025 27969 -56
===========================================
- Hits 18845 15710 -3135
- Misses 7602 10525 +2923
- Partials 1578 1734 +156 🚀 New features to boost your workflow:
|
/test e2e-aws-ovn |
pkg/config/template_test.go
Outdated
Expect(output).To(ContainSubstring("allowed_annotations = [")) | ||
Expect(output).To(ContainSubstring(`"io.kubernetes.cri-o.userns-mode",`)) | ||
Expect(output).To(ContainSubstring(`"io.kubernetes.cri-o.umask",`)) | ||
Expect(output).To(ContainSubstring(`"io.kubernetes.cri-o.Devices",`)) |
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.
Can you modify it to check if it has the whole array to enforce it has allowed_annotations in the expected format?
allowed_annotations = [
"io.kubernetes.cri-o.userns-mode",
"io.kubernetes.cri-o.umask",
"io.kubernetes.cri-o.Devices",
]
Thank you for the fix! @prasad89 |
Co-authored-by: Ayato Tokubi <atokubi@redhat.com> Signed-off-by: Prasad Bhalerao <67261499+prasad89@users.noreply.github.com> Signed-off-by: prasad89 <vdbhaleraovb@gmail.com>
@prasad89: The following test failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
@prasad89 It seems you need to fix the unit tests |
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR updates
pkg/config/template.go
to includeallowed_annotations
in the generatedcrio config
output for each workload.Previously, even if
allowed_annotations
were set incrio.conf
, they were missing from the printed configuration, making it hard for users to verify workload configuration.Which issue(s) this PR fixes:
Fixes #9467
Special notes for your reviewer:
allowed_annotations
when non-emptybin/crio config
now showsallowed_annotations
as expectedDoes this PR introduce a user-facing change?