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

Confusing installNamespace requirement for AKS (and likely more) #553

Open
coolhome opened this issue Jun 14, 2024 · 1 comment
Open

Confusing installNamespace requirement for AKS (and likely more) #553

coolhome opened this issue Jun 14, 2024 · 1 comment

Comments

@coolhome
Copy link

https://github.com/CrowdStrike/falcon-operator/tree/main/docs/deployment/azure

When I was installing a lot of these components, I noticed something changed recently in1.0.0 where the installNamespace from FalconContainer is now falcon-system - which conflicts with the FalconNodeSensor default namespace. The FalconContainer being deployed after FalconNodeSensor will error for must be installed in a workload alone. I think the documentation should include this or revert back to the original default namespace for FalconContainer.

@redhatrises
Copy link
Contributor

falcon-system is the original namespace. In AKS, we really only recommend deploying the node sensor or falcon container and not both.

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

No branches or pull requests

2 participants