-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Move and revise overview for Security section #43176
Move and revise overview for Security section #43176
Conversation
* [Certified Kubernetes Security Specialist](https://training.linuxfoundation.org/certification/certified-kubernetes-security-specialist/) | ||
certification and official training course. | ||
|
||
Read more in this section: |
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.
This relies on simple_list: true
in the front matter. See the preview.
/label refactor |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
d3fea01
to
8a368b9
Compare
8a368b9
to
d7c996a
Compare
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.
Thanks,
A partial review from my end
|
||
### Observbility and runtime security | ||
|
||
As your applications run they - and the cluster they run on - give you ways to |
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.
The statement is semantically and grammatically correct, But should we make this more clear and concise?
As your applications run they - and the cluster they run on - give you ways to | |
Kubernetes enables you to observe and monitor your applications and the clusters they are running on |
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.
This change doesn't produce a sentence that makes sense. I'll adapt it.
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's this now?
6c62b42
to
857eb1b
Compare
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.
Some minor suggestions from my side
## _Deploy_ lifecycle phase {#lifecycle-phase-deploy} | ||
|
||
Ensure appropriate restrictions on what can be deployed, who can deploy it, | ||
and where it can be deployed to. |
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.
and where it can be deployed to. | |
and where it can be deployed. |
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.
I (still) think “where it can be deployed to” is how people who speak English would say it.
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.
+1 to what Tim said.
Thanks for the review @aj11anuj. However, please watch out for making suggestions that change text from good use of English to invalid or unidiomatic English. |
Part of #25119 |
08439ea
to
2f45b51
Compare
f56031d
to
cf22354
Compare
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.
Overall this LGTM. However, I am just curious if we want to link to the hardening guide for further reading?
## _Deploy_ lifecycle phase {#lifecycle-phase-deploy} | ||
|
||
Ensure appropriate restrictions on what can be deployed, who can deploy it, | ||
and where it can be deployed to. |
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.
+1 to what Tim said.
We actually have several (some are labelled as good practice, one as hardening, another as a security checklist). I'd love to see a follow-up land that tidies things up. See https://deploy-preview-43176--kubernetes-io-main-staging.netlify.app/docs/concepts/security/#what-s-next for a selection of what we have now. |
f414fc6
to
fc9f380
Compare
Looks good to me now. Hopefully one more person from sig security can review too |
A key security mechanism for any Kubernetes is to | ||
[control access to the Kubernetes API](/docs/concepts/security/controlling-access). | ||
|
||
You can define [encryption at rest](/docs/tasks/administer-cluster/encrypt-data/) |
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.
Nit: Recommend calling out TLS first in this paragraph, since it is essential to virtually any effort to secure a kubernetes cluster. Then move to "You can also configure encryption at rest..." because it's a good idea but less critical for many common use cases.
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.
(reworded)
{{< glossary_tooltip text="Containers" term_id="container" >}} provide two | ||
things: isolation between different applications, and a mechanism to combine | ||
those isolated applications to run on the same host computer. Those two | ||
aspects, isolation and aggregation, mean that runtime security involves |
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.
Just wanna say that I LOVE this sentence especially.
I left several nits, none of which should be interpreted as merge-blocking. This is beautiful! Thank you for the huge amount of thoughtful work that has gone into it. /lgtm Please ping me to re-LGTM if you choose to address any of the nits and the LGTM thus falls off. |
LGTM label has been added. Git tree hash: ccf8350debc22d3f702fda57085974e2bc413e0b
|
The [Secret](/docs/concepts/configuration/secret/) API provides basic protection for | ||
configuration values that require confidentiality. |
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.
Should we add that secrets are only base64 encoded and are stored unencrypted in the API server? (A premonition to the caution block under the secrets documentation)
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.
Maybe you'd like to propose that for a follow-up PR?
You can enforce measures from the _distribute_ phase, such as verifying the | ||
cryptographic identity of container image artefacts. | ||
|
||
When you deploy Kubernetes, you also set the foundation for your |
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.
When you deploy Kubernetes, you also set the foundation for your | |
When you deploy Kubernetes, you also set the foundation for your |
When you deploy Kubernetes
seems confusing. Do mean Deploy to Kubernetes
or Deploy a Kubernetes cluster
?
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.
I mean deploy at least one Kubernetes cluster; is that not as obvious as I'd've hoped?
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.
I guess it makes sense. 👍
Missed to comment lgtm /lgtm |
@AnshumanTripathi: changing LGTM is restricted to collaborators 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. |
Co-authored-by: Anshuman Tripathi <anshuman.tripathi305@gmail.com> Co-authored-by: Anuj Tiwari <aj11anuj123@gmail.com> Co-authored-by: Gaurav Padam <1032201077@tcetmumbai.in> Co-authored-by: Tabitha Sable <51767484+tabbysable@users.noreply.github.com>
9a51f85
to
9323995
Compare
@tabbysable, I think this is ready for another LGTM if you're happy with it. |
/lgtm ( @tabbysable hoping to save you some keystrokes ) |
LGTM label has been added. Git tree hash: a1b1242f846cb0ea779b57876b229ff1720b9a6a
|
This PR improves the security content in the docs |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: reylejano 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 |
A fix for #36591 (fixes #36591)
We should make this change because https://kubernetes.io/docs/concepts/security/overview/ is not really giving readers a good overview of how to secure a Kubernetes cluster. That page was much better than no advice; this PR aims to improve it further by explicitly aligning with the CNCF security white paper.
/language en
/sig security