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.

Sign up for GitHub

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

Jump to bottom

Making sure that service and ingress are in the same namespace #525

Merged
merged 4 commits into from
Oct 16, 2023

change control scope

3035658
Select commit
Loading
Failed to load commit list.
Merged

Making sure that service and ingress are in the same namespace #525

change control scope
3035658
Select commit
Loading
Failed to load commit list.
GitHub Advanced Security / kubescape succeeded Oct 16, 2023 in 10s

No new alerts in code changed by this pull request

View all branch alerts.

Annotations

Check warning on line 5 in rules/exposure-to-internet/test/failed_with_ingress/input/service.yaml

See this annotation in the file changed.

Code scanning / kubescape

CIS-5.7.4 The default namespace should not be used Warning test

Kubernetes provides a default namespace, where objects are placed if no namespace is specified for them. Placing objects in this namespace makes application of RBAC and other controls more difficult.