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
Remove deprecated --seccomp-profile-root
/seccompProfileRoot
config
#103941
Remove deprecated --seccomp-profile-root
/seccompProfileRoot
config
#103941
Conversation
/priority important-soon |
/retest |
/lgtm Thanks for handling this one @saschagrunert |
/triage accepted |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
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.
/lgtm
/assign @dchen1107 @erictune |
/approve |
@kubernetes/api-approvers PTAL |
pkg/kubelet/kuberuntime/helpers.go
Outdated
@@ -266,6 +266,11 @@ func (m *kubeGenericRuntimeManager) getSeccompProfilePath(annotations map[string | |||
return "" | |||
} | |||
|
|||
// seccompRootDirectory returns the path for the localhost seccomp profiles. | |||
func (m *kubeGenericRuntimeManager) seccompRootDirectory() string { |
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.
how frequently is this called? would it make sense to construct this once at startup? xref #16384 for cost of invoking Join methods repeatedly.
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.
Yes, I moved the construction of this path to the kuberuntime initialization: https://github.com/kubernetes/kubernetes/pull/103941/files#diff-0e1a8d22b0f1dc42d412749c6a916b4c76394ead739d4bfbf26564faedd74a2fR210
api doc change and flag bit lgtm, a couple questions about the implementation |
583ac14
to
5dc5cba
Compare
…guration The configuration is deprecated and targets removal for v1.23. Tests cases have been changed as well. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
5dc5cba
to
46077e6
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, mrunalp, pjbgf, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind api-change
What this PR does / why we need it:
The configuration is deprecated and targets removal for v1.23. Tests cases have been changed as well.
Which issue(s) this PR fixes:
Follow-up of #91182
Refers to kubernetes/enhancements#135
Special notes for your reviewer:
cc @knabben @pjbgf
/milestone v1.23
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: