-
Notifications
You must be signed in to change notification settings - Fork 241
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
Install apparmor-utils to include apparmor_parser on Hetzner Baremetal Ubuntu Servers #3233
Conversation
/assign |
/approve |
LGTM label has been added. Git tree hash: 0d6854094f5323ba000bc457f33ec6da210cedf3
|
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.
/kind bug
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kron4eg, xmudrii 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 |
@mohamed-rafraf Can you add a release note about this change? Something like:
|
/cherrypick release/v1.8 |
/cherrypick release/v1.7 |
@xmudrii: new pull request created: #3235 In response to this:
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. |
@xmudrii: new pull request created: #3236 In response to this:
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. |
What this PR does / why we need it:
Ensures apparmor_parser is installed by adding the apparmor-utils package, and fixing kubelet container start issues on Hetzner Baremetal Ubuntu Servers.
Which issue(s) this PR fixes:
Fixes #2133
What type of PR is this?
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: