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

Better support for analysis with specific ingress controllers #235

Open
adisos opened this issue Sep 11, 2023 · 1 comment
Open

Better support for analysis with specific ingress controllers #235

adisos opened this issue Sep 11, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@adisos
Copy link
Collaborator

adisos commented Sep 11, 2023

The problem : assume workload foo has an Ingress/Route rule, and a tight network policy that only permits ingress access to foo from a certain namespace/pod of a specific ingress-controller.
Currently the analysis does not identify specific ingress-controller, thus assumes the required connection from Ingres/Route rules is blocked by network policies. (Only if the ingress access is open to any in-cluster workload, it identifies permitted access from a general ingress-controller to the workload).

This can be refined.
Consider specific known labels of namespaces for ingress-controllers.
Consider new input parameter to specify such labels to be considered in the analysis.

@adisos adisos added the enhancement New feature or request label Oct 1, 2023
@adisos
Copy link
Collaborator Author

adisos commented Nov 14, 2023

initial enhancement: identify ingress-nginx by labels/namespace
and also openshifft ingress controller

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants