-
Notifications
You must be signed in to change notification settings - Fork 950
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
bugfix: we should make MaskedPaths and ReadonlyPaths to be nil when privileged be set #2720
Merged
fuweid
merged 1 commit into
AliyunContainerService:master
from
HusterWan:zr/fix-kube-proxy-start-failed
Feb 26, 2019
Merged
bugfix: we should make MaskedPaths and ReadonlyPaths to be nil when privileged be set #2720
fuweid
merged 1 commit into
AliyunContainerService:master
from
HusterWan:zr/fix-kube-proxy-start-failed
Feb 26, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #2720 +/- ##
==========================================
+ Coverage 69.26% 69.38% +0.12%
==========================================
Files 278 278
Lines 17486 17486
==========================================
+ Hits 12111 12132 +21
+ Misses 4035 4022 -13
+ Partials 1340 1332 -8
|
HusterWan
force-pushed
the
zr/fix-kube-proxy-start-failed
branch
from
February 21, 2019 07:36
86329ab
to
50570a4
Compare
…rivileged be set Signed-off-by: Michael Wan <zirenwan@gmail.com>
HusterWan
force-pushed
the
zr/fix-kube-proxy-start-failed
branch
from
February 21, 2019 08:00
50570a4
to
0befc91
Compare
HusterWan
changed the title
[wip]bugfix: we should make MaskedPaths and ReadonlyPaths to be nil when privileged be set
bugfix: we should make MaskedPaths and ReadonlyPaths to be nil when privileged be set
Feb 21, 2019
fuweid
reviewed
Feb 26, 2019
fuweid
reviewed
Feb 26, 2019
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Michael Wan zirenwan@gmail.com
Ⅰ. Describe what this PR did
When creating a privileged container, we should let the
proc
directories to be writable for the container.Now we have some users that have kubernetes 1.12/1.13 + pouch environment, but they can not start the kube-proxy daemonset pod because the container do not have write access to the
proc
directories.BTW, the
MaskedPaths
andReadonlyPaths
parameters should belong toHostConfig
notContainerConfig
.Ⅱ. Does this pull request fix one issue?
fixes: #2649
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗?)
yes add ut for the
MaskedPaths
andReadonlyPaths
parseⅣ. Describe how to verify it
Ⅴ. Special notes for reviews