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

fix(shield): apply kspm_analyzer agent app name #1999

Merged
merged 3 commits into from
Oct 29, 2024

Conversation

aroberts87
Copy link
Collaborator

What this PR does / why we need it:

The kspm analyzer requires the agent_app_name parameter to be set to the value given to the app.kubernetes.io/name label on the host shield pod, which is shield when installed via the shield chart.

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

@aroberts87 aroberts87 self-assigned this Oct 29, 2024
@aroberts87 aroberts87 requested a review from a team as a code owner October 29, 2024 13:30
aroberts87 and others added 3 commits October 29, 2024 09:51
The kspm analyzer requires the 'agent_app_name' parameter to be set to
the value given to the 'app.kubernetes.io/name' label on the host shield
pod, which is 'shield' when installed via the shield chart.
correct source of agent_app_name value

Co-authored-by: Alberto Barba <[email protected]>
@aroberts87 aroberts87 force-pushed the aroberts/fix/shield-agent-app-name branch from 5792813 to 1c43bcb Compare October 29, 2024 13:51
@aroberts87 aroberts87 merged commit a08bf37 into main Oct 29, 2024
4 checks passed
@aroberts87 aroberts87 deleted the aroberts/fix/shield-agent-app-name branch October 29, 2024 14:15
fnonay pushed a commit that referenced this pull request Oct 30, 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.

2 participants