-
Notifications
You must be signed in to change notification settings - Fork 363
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
Start document with security recommendations #1296
Start document with security recommendations #1296
Conversation
At the moment, the document discusses how to restrict access from Pods to the OVSDB file persisted on each Node's filesystem.
Thanks for your PR. The following commands are available:
|
Codecov Report
@@ Coverage Diff @@
## master #1296 +/- ##
==========================================
- Coverage 54.40% 54.39% -0.02%
==========================================
Files 115 115
Lines 10807 10807
==========================================
- Hits 5880 5878 -2
- Misses 4353 4354 +1
- Partials 574 575 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
wonder what the scope of this document will be going further? best practices? or only security related? if former then shall we name it best-practices.md? |
@abhiraut probably just security related, that's how I envision it |
nice.. i had not seen the 4Cs of security before. |
/skip-all |
At the moment, the document discusses how to restrict access from Pods to the OVSDB file persisted on each Node's filesystem.
At the moment, the document discusses how to restrict access from Pods to the OVSDB file persisted on each Node's filesystem.
At the moment, the document discusses how to restrict access from Pods
to the OVSDB file persisted on each Node's filesystem.