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

#1283 update Rancher security best practices to address public IP exposure #1287

Conversation

martyav
Copy link
Contributor

@martyav martyav commented May 14, 2024

Fixes #1283

Reminders

  • See the README for more details on how to work with the Rancher docs.

  • Verify if changes pertain to other versions of Rancher. If they do, finalize the edits on one version of the page, then apply the edits to the other versions.

  • If the pull request is dependent on an upcoming release, make sure to target the release branch instead of main.

Description

This adds some information about how to protect from nodes' public IP addresses being exposed. It's an internal request from the security repo. The PR also reduces the levels on the headings from 3 to 2, since there is no intervening second level heading between them and the H1 title.

Comments

@martyav martyav added the sync-versions Reminder to sync versioned pages label May 14, 2024
Copy link
Contributor

@sunilarjun sunilarjun left a comment

Choose a reason for hiding this comment

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

Just a small addition, but otherwise looks good. thanks Marty!

You should protect the following ports behind an [external load balancer](../../how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/layer-4-and-layer-7-load-balancing.md#layer-4-load-balancer) that has SSL offload enabled:

- **K3s:** Port 6443, used by the Kubernetes API.
- **RKE2:** Port 6443, used by the Kubernetes API, and port 9345, used for node registration.
Copy link
Contributor

Choose a reason for hiding this comment

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

Does RKE(1) require any action?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I left a comment asking about this on the associated security issue

@martyav
Copy link
Contributor Author

martyav commented Jun 3, 2024

I haven't heard back in 3 weeks, I'm just going to merge as the information is important and relevant. If we do hear back on RKE1 we can update the page.

@martyav martyav removed sync-versions Reminder to sync versioned pages labels Jun 3, 2024
@martyav martyav merged commit e1634c6 into rancher:main Jun 3, 2024
2 checks passed
martyav added a commit to martyav/rancher-docs that referenced this pull request Jun 10, 2024
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.

Update rancher-security-best-practices to address public IP exposure
3 participants