Skip to content

Introduce new full-safe profile with a default resource deny list #134

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ardaguclu
Copy link
Contributor

After the #133 has merged, we'll have an option to deny operations for some resources.

This PR introduces new profile, namely full-safe that brings in with a set of resources that will be denied. Additionally, this profile will not serve a tool for viewing kubeconfig.

There won't be any change in default behaviors.

@ardaguclu
Copy link
Contributor Author

@manusa what is your opinion about this one?.

@manusa
Copy link
Owner

manusa commented Jun 20, 2025

@manusa what is your opinion about this one?.

Sorry for the late reply, it's been an intense morning.
It looks good.
My only doubt is about the name plus if this is aligned with @mrunalp expectations.

Since the changes are very isolated, I think we can hold it until he checks it out, I want to merge the dependabot PRs and maybe cut a release today.

@ardaguclu
Copy link
Contributor Author

@mrunalp could you please have a look at and drop your thoughts?.

@ardaguclu ardaguclu force-pushed the full-safe-profile branch from 56d1d18 to 922da8d Compare June 20, 2025 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants