Skip to content
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 sysctl patterns to PodSecurityPolicy and admission plugin #7

Merged
merged 2 commits into from
Jun 30, 2016

Conversation

sttts
Copy link
Owner

@sttts sttts commented Jun 28, 2016

No description provided.

@sttts
Copy link
Owner Author

sttts commented Jun 28, 2016

/cc @pweil- could you take a look at these PodSecurityPolicy changes for sysctls?

@sttts
Copy link
Owner Author

sttts commented Jun 29, 2016

/cc @hodovska

// Sysctls is a white list of allowed sysctls in a pod spec. Each entry
// is either a plain sysctl name or ends in "*" in which case it is considered
// as a prefix of allowed sysctls.
Sysctls []string `json:"sysctls,omitempty"`
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will * be a use case to allow all sysctls?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

disregard - I see this is covered in the use case. Maybe just need clarification in the comment that * is allowed as a full value and not just a suffix

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@sttts sttts merged this pull request into sysctl-implementation Jun 30, 2016
@sttts sttts deleted the sttts-sysctl-policy branch June 30, 2016 12:15
sttts pushed a commit that referenced this pull request Aug 5, 2016
- Cannot attach scsi devices to slot #7
- Limit of 4 scsi controllers per vm MAX
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants