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 v2.6 hardening guides #3810

Merged
merged 7 commits into from
Mar 14, 2022
Merged

Add v2.6 hardening guides #3810

merged 7 commits into from
Mar 14, 2022

Conversation

macedogm
Copy link
Member

@macedogm macedogm commented Jan 21, 2022

Add hardening guides for Rancher v2.6.

We also need to upload, please, the following PDF files to our site:

Signed-off-by: Guilherme Macedo guilherme.macedo@suse.com

@macedogm
Copy link
Member Author

macedogm commented Jan 21, 2022

I'm moving this temporarily to draft, while we wait for @anupama2501's review.

@macedogm macedogm marked this pull request as ready for review February 2, 2022 09:23
@macedogm
Copy link
Member Author

macedogm commented Feb 2, 2022

As discussed with @cbron, PR is ready for review by Caleb and @paraglade.

Signed-off-by: Guilherme Macedo <guilherme.macedo@suse.com>
Copy link
Contributor

@paraglade paraglade left a comment

Choose a reason for hiding this comment

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

looks good enough to publish from what I can see

Signed-off-by: Guilherme Macedo <guilherme.macedo@suse.com>
@ryansann
Copy link
Contributor

@macedogm I have a few additional items in my cloud-config I use for hardening, posting here in case they are needed:

ssh_pwauth: false
runcmd:
...
# allow kubernetes api inbound traffic to 6443
- iptables -A INPUT -p tcp --dport 6443 -j ACCEPT
# allow etcd inbound traffic to 2379
- iptables -A INPUT -p tcp --dport 2379 -j ACCEPT

@ryansann
Copy link
Contributor

Something about the PDF generation for the benchmark assessment is causing not enough padding to be added between lines in the Contents

(I tried this in multiple browsers and saw the same)

Screenshot (3)

@macedogm
Copy link
Member Author

@macedogm I have a few additional items in my cloud-config I use for hardening, posting here in case they are needed:

ssh_pwauth: false
runcmd:
...
# allow kubernetes api inbound traffic to 6443
- iptables -A INPUT -p tcp --dport 6443 -j ACCEPT
# allow etcd inbound traffic to 2379
- iptables -A INPUT -p tcp --dport 2379 -j ACCEPT

@ryansann Thanks for this idea. For now I added only ssh_pwauth: false, which is a great hardening step. I would refrain from adding the iptables rules now, to avoid messing with other possible firewall rules from the users.

Signed-off-by: Guilherme Macedo <guilherme.macedo@suse.com>
@macedogm
Copy link
Member Author

macedogm commented Feb 21, 2022

Something about the PDF generation for the benchmark assessment is causing not enough padding to be added between lines in the Contents

(I tried this in multiple browsers and saw the same)

@ryansann Thanks for spotting this. Somehow I missed, but it's fixed now. Can you please have a look if the new style for the contents section is better?

@ryansann
Copy link
Contributor

Something about the PDF generation for the benchmark assessment is causing not enough padding to be added between lines in the Contents
(I tried this in multiple browsers and saw the same)

@ryansann Thanks for spotting this. Somehow I missed, but it's fixed now. Can you please have a look if the new style for the contents section is better?

No problem! I pulled the most recent changes and the PDFs look good now 👍

@cbron
Copy link
Contributor

cbron commented Feb 23, 2022

We either need to re-open this against staging, or do QA before we merge, as this PR will go live to docs site.

Copy link
Contributor

@cbron cbron left a comment

Choose a reason for hiding this comment

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

Didn't deep dive but seems fine to me besides branch changes. Will need to talk to docs team about PDFs.

| Kubernetes Version | CIS Benchmark Version | Self Assessment Guide | Hardening Guides |
| --- | --- | --- | --- |
| Kubernetes v1.18 | CIS v1.5 | [Link](https://docs.rke2.io/security/cis_self_assessment15/) | [Link](https://docs.rke2.io/security/hardening_guide/) |
| Kubernetes v1.20 | CIS v1.6 | [Link](https://docs.rke2.io/security/cis_self_assessment16/) | [Link](https://docs.rke2.io/security/hardening_guide/) |
Copy link
Contributor

Choose a reason for hiding this comment

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

Are we also going to link our rke2 guides down the road ? We can adjust then, just curious.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, in case you want to have them separated from the current RKE2 guides. My initial plan was only to update those guides in their current place (docs.rke2.io), instead of "forking" them to be inside rancher.com/docs. WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

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

If there are details specific to Rancher then it should be on Rancher side. RKE2 docs should be standalone RKE2 only.

@macedogm macedogm changed the base branch from master to staging February 23, 2022 10:26
@macedogm
Copy link
Member Author

macedogm commented Feb 23, 2022

We either need to re-open this against staging, or do QA before we merge, as this PR will go live to docs site.

@cbron okay, I changed the branch to go to staging.

@btat can you please advise how this now goes to staging and then master? Is this done automatically or do I need to keep track?

@macedogm macedogm requested a review from btat February 23, 2022 10:29
@macedogm
Copy link
Member Author

Didn't deep dive but seems fine to me besides branch changes. Will need to talk to docs team about PDFs.

@btat regarding this point raised by Caleb, do you want to change the format/styling of the PDFs? I reused the same format and style of the current guides, but a revamp in terms of branding might be good too. Please let me know if you want to chat about this.

@btat
Copy link
Contributor

btat commented Feb 24, 2022

We either need to re-open this against staging, or do QA before we merge, as this PR will go live to docs site.

@cbron okay, I changed the branch to go to staging.

@btat can you please advise how this now goes to staging and then master? Is this done automatically or do I need to keep track?

@macedogm after this is merged to staging, you do not need to keep track of it. The docs team will handle bringing over updates from staging back to master, which will happen around release time.

Didn't deep dive but seems fine to me besides branch changes. Will need to talk to docs team about PDFs.

@btat regarding this point raised by Caleb, do you want to change the format/styling of the PDFs? I reused the same format and style of the current guides, but a revamp in terms of branding might be good too. Please let me know if you want to chat about this.

The current format/styling looks fine to me, but I'm not familiar with the latest branding guidelines. I can circulate this among the docs team for additional feedback and then we can sync up afterwards if needed.

@macedogm
Copy link
Member Author

@btat

@macedogm after this is merged to staging, you do not need to keep track of it. The docs team will handle bringing over updates from staging back to master, which will happen around release time.

Thanks!

The current format/styling looks fine to me, but I'm not familiar with the latest branding guidelines. I can circulate this among the docs team for additional feedback and then we can sync up afterwards if needed.

Also thanks for checking this. 👍🏻

@macedogm
Copy link
Member Author

@btat I believe that this PR is also good to be merged to staging.

@btat btat merged commit 5fc62be into rancher:staging Mar 14, 2022
@btat
Copy link
Contributor

btat commented Mar 14, 2022

@btat I believe that this PR is also good to be merged to staging.

Done :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants