Revision 2063a21d984ebb3b11e296f245470aa711ffac8a authored by Timo Beckers on 20 February 2024, 15:23:34 UTC, committed by Timo Beckers on 29 February 2024, 13:38:41 UTC
This was already redundant when running Cilium inside a container, since the nsfs instance inside the container is bound to the container's lifecycle. Running Cilium outside of a container is currently rather involved and not officially supported. Remove the netns cleanup code. When the container exits, cilium-health and its enclosing namespace also disappears. Follow-up commits will remove the code in package netns being called here. Signed-off-by: Timo Beckers <timo@isovalent.com>
1 parent ed04ccd
SECURITY.md
# Security Policy
## Supported Versions
| Version | Supported |
|----------| ------------------ |
| main | :white_check_mark: |
| 1.15.x | :white_check_mark: |
| 1.14.x | :white_check_mark: |
| 1.13.x | :white_check_mark: |
| < 1.13.0 | :x: |
## Reporting a Vulnerability
We strongly encourage you to report security vulnerabilities to
our private security mailing list: security@cilium.io - first, before
disclosing them in any public forums.
A threat model for Cilium and recommendations for running Cilium in production
environments can be found [here][threat-model]. Please ensure that you have
taken this threat model into consideration before making a report, including
considering the feasibility of an attack against a correctly secured
environment.
This is a private mailing list where members of Cilium's
[Security Team](https://github.com/cilium/community/blob/main/roles/Security-Team.md)
are subscribed to, and is treated as top priority.
[threat-model]: https://docs.cilium.io/en/latest/security/threat-model/
Computing file changes ...
