Skip to content

fix(cluster-shield,shield): remove allowedUnsafeSysctls #2271

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

Conversation

Juravenator
Copy link
Contributor

What this PR does / why we need it:

This restores some changes made in #2005. For some reason commit #2173 (chore) reverted some of them (I'm guessing unintentional).

Encountered by using OpenShift GitOps (Argo CD) with the Shield chart v1.7.1 as explained in #2005.

Checklist

  • Title of the PR starts with type and scope, (e.g. feat(agent,node-analyzer,sysdig-deploy):)
  • Chart Version bumped for the respective charts
  • Variables are documented in the README.md (or README.tpl in some charts)
  • Check GithubAction checks (like lint) to avoid merge-check stoppers
  • All test files are added in the tests folder of their respective chart and have a "_test" suffix

@Juravenator Juravenator requested a review from a team as a code owner June 4, 2025 12:37
Copy link
Contributor

github-actions bot commented Jun 4, 2025

Hi @Juravenator. Thanks for your PR.

After inspecting your changes someone with write access to this repo needs
to approve and run the workflow.

@Juravenator Juravenator force-pushed the fix-remove-unused-constraint-again branch from f7f47fe to 921636b Compare June 6, 2025 08:52
Copy link
Contributor

github-actions bot commented Aug 6, 2025

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale The issue or pull request is inactive and will be closed soon label Aug 6, 2025
Copy link
Contributor

This PR has been closed due to inactivity.

@github-actions github-actions bot closed this Aug 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The issue or pull request is inactive and will be closed soon
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant