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

Do not use default namespace #211

Merged
merged 1 commit into from
Feb 19, 2025
Merged

Do not use default namespace #211

merged 1 commit into from
Feb 19, 2025

Conversation

mjura
Copy link
Contributor

@mjura mjura commented Feb 3, 2025

It is bad practice to use default namespace, due to:

  • lack of isolation
  • security risks
  • resources management
  • scalability issues

@mjura mjura requested a review from a team as a code owner February 3, 2025 08:26
Copy link
Contributor

@salasberryfin salasberryfin 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 typo

Copy link
Contributor

@furkatgofurov7 furkatgofurov7 left a comment

Choose a reason for hiding this comment

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

You could make the same changes in the v0.16 docs folder in the same PR (no need to backport in this case), otherwise LGTM

It is bad practice to use default namespace, due to:
- lack of isolation
- security risks
- resources management
- scalability issues
@mjura mjura merged commit 209ae97 into rancher:main Feb 19, 2025
1 check passed
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.

5 participants