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

Remove security enforcement label from namespace in SaaS #531

Merged
merged 2 commits into from
Apr 30, 2024

Conversation

Zelldon
Copy link
Member

@Zelldon Zelldon commented Apr 30, 2024

In SaaS we recently introduced a label that indicates to prevent certain actions (security related), see related slack thread

In order to make sure that our experiments, and actions are successful in SaaS
we need to make sure that reconciliation is paused and the
security enforcement label is removed from the corresponding
target namespace. That is now always done when creating a client for a SaaS environment.

After doing so we can get further privileges, that are needed for
actions like putting stress on the CPU, network partition, etc.

In SaaS we recently introduced a label that indicates to prevent certain actions (security related)
In order to make sure that our experiments, actions are successful in SaaS
we need to make sure that reconciliation is paused and the
security enforcement label is removed from the corresponding
target namespace.

After doing so we are able to get furhter priviliges, that are needed for
actions like putting stress on CPU, network partition, etc.
@Zelldon Zelldon changed the title Ck fix saas security Remove security enforcement label from namespace in SaaS Apr 30, 2024
Copy link
Contributor

@lenaschoenburg lenaschoenburg left a comment

Choose a reason for hiding this comment

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

Thanks! 🚀

@Zelldon Zelldon merged commit 479929f into main Apr 30, 2024
3 checks passed
@Zelldon Zelldon deleted the ck-fix-saas-security branch April 30, 2024 13:05
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.

None yet

2 participants