Skip to content

Support IAR CID from existing secret#523

Open
pkill2913 wants to merge 1 commit into
CrowdStrike:mainfrom
pkill2913:iar-support-agent-cid-existing-secret
Open

Support IAR CID from existing secret#523
pkill2913 wants to merge 1 commit into
CrowdStrike:mainfrom
pkill2913:iar-support-agent-cid-existing-secret

Conversation

@pkill2913

Copy link
Copy Markdown

Summary

Adds support for providing Falcon Image Analyzer CID through an existing Kubernetes secret using AGENT_CID.

Previously, IAR supported crowdstrikeConfig.existingSecret for AGENT_CLIENT_ID and AGENT_CLIENT_SECRET, but still required the CID through crowdstrikeConfig.cid or global.falcon.cid. This change allows the CID to come from the
same existing secret.

Changes

  • Omits AGENT_CID from the ConfigMap when CID is provided by an existing secret.
  • Allows crowdstrikeConfig.existingSecret or global.falconSecret.secretName to satisfy CID configuration.
  • Updates schema validation.
  • Updates IAR and falcon-platform documentation.
  • Bumps chart versions:
    • falcon-image-analyzer: 1.1.20 -> 1.1.21
    • falcon-platform: 1.4.0 -> 1.4.1

Testing

  • helm template with crowdstrikeConfig.existingSecret
  • helm template with global.falconSecret.secretName
  • helm template with direct crowdstrikeConfig.cid
  • helm lint helm-charts/falcon-image-analyzer
  • helm lint helm-charts/falcon-platform

@pkill2913 pkill2913 force-pushed the iar-support-agent-cid-existing-secret branch from 19a10b9 to 1d3ebaa Compare June 10, 2026 12:39
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.

1 participant