Popeye Scan Report
Scanned
n/a/n/a
2026-09-11T05:12:31Z
C
78
CILIUMCLUSTERWIDENETWORKPOLICIES (0 SCANNED)
0
0
0
0
100%
CILIUMENDPOINTS (38 SCANNED)
0
0
0
38
100%
CILIUMIDENTITIES (1 SCANNED)
0
1
0
0
0%
-
materiel/1097
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
CILIUMNETWORKPOLICIES (0 SCANNED)
0
0
0
0
100%
CLUSTERS (1 SCANNED)
0
0
0
1
100%
-
Version
- [POP-406] K8s version OK
CLUSTERROLES (107 SCANNED)
0
0
5
102
100%
-
cert-manager-cluster-view
- [POP-400] Used? Unable to locate resource reference
-
cnpg-cloudnative-pg-edit
- [POP-400] Used? Unable to locate resource reference
-
cnpg-cloudnative-pg-view
- [POP-400] Used? Unable to locate resource reference
-
external-secrets-servicebindings
- [POP-400] Used? Unable to locate resource reference
-
velero-ui
- [POP-400] Used? Unable to locate resource reference
CLUSTERROLEBINDINGS (89 SCANNED)
0
4
0
85
95%
-
system:controller:route-controller
- [POP-1300] References a ServiceAccount (kube-system/route-controller) which does not exist
-
system:controller:selinux-warning-controller
- [POP-1300] References a ServiceAccount (kube-system/selinux-warning-controller) which does not exist
-
system:controller:service-controller
- [POP-1300] References a ServiceAccount (kube-system/service-controller) which does not exist
-
system:kube-dns
- [POP-1300] References a ServiceAccount (kube-system/kube-dns) which does not exist
CONFIGMAPS (48 SCANNED)
0
0
16
32
100%
-
botkube/botkube-system
- [POP-400] Used? Unable to locate resource reference
-
cooptation/cnpg-default-monitoring
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-gitlab-upgrade-check
- [POP-400] Used? Unable to locate resource reference
-
intranet/intranet-mysql-backup
- [POP-400] Used? Unable to locate resource reference
-
intranet/intranet-mysql-test
- [POP-400] Used? Unable to locate resource reference
-
kube-system/cluster-autoscaler-status
- [POP-400] Used? Unable to locate resource reference
-
kube-system/extension-apiserver-authentication
- [POP-400] Used? Unable to locate resource reference
-
kube-system/kube-apiserver-legacy-service-account-token-tracking
- [POP-400] Used? Unable to locate resource reference
-
kube-system/kube-proxy
- [POP-400] Used? Unable to locate resource reference
-
les-projets-cagnottes/cnpg-default-monitoring
- [POP-400] Used? Unable to locate resource reference
-
materiel/materiel-mysql-test
- [POP-400] Used? Unable to locate resource reference
-
val-system/cnpg-controller-manager-config
- [POP-400] Used? Unable to locate resource reference
-
val-system/cnpg-default-monitoring
- [POP-400] Used? Unable to locate resource reference
-
velero/ingress-host-modifier
- [POP-400] Used? Unable to locate resource reference
-
velero/velero-repo-maintenance
- [POP-400] Used? Unable to locate resource reference
-
velero/velero-ui
- [POP-400] Used? Unable to locate resource reference
CRONJOBS (5 SCANNED)
0
4
0
1
20%
-
kivaou/bookings-snapshot
- [POP-1501] No active jobs detected
- trigger-bookings-snapshot
- [POP-106] No resources requests/limits defined
kivaou/kivaou-cron-confirmation-booking
- [POP-1501] No active jobs detected
- [POP-106] No resources requests/limits defined
kube-system/hubble-generate-certs
- [POP-1501] No active jobs detected
- [POP-106] No resources requests/limits defined
materiel/materiel-snipeit-requestcleanup
- [POP-1501] No active jobs detected
- [POP-106] No resources requests/limits defined
DAEMONSETS (5 SCANNED)
1
4
0
0
0%
-
kube-system/cilium
- [POP-505] At current load, Memory under allocated. Current:1236Mi vs Requested:330Mi (374.55%)
- apply-sysctl-overwrites
- [POP-106] No resources requests/limits defined
- cilium-agent
- [POP-106] No resources requests/limits defined
- clean-cilium-state
- [POP-107] No resource limits defined
- config
- [POP-106] No resources requests/limits defined
- mount-bpf-fs
- [POP-106] No resources requests/limits defined
- mount-cgroup
- [POP-106] No resources requests/limits defined
kube-system/csi-node
- [POP-106] No resources requests/limits defined
- [POP-106] No resources requests/limits defined
kube-system/konnectivity-agent
- [POP-106] No resources requests/limits defined
kube-system/kube-proxy
- [POP-508] No pods match controller selector: app=kube-proxy
- [POP-107] No resource limits defined
monitoring/alloy
- [POP-503] At current load, CPU under allocated. Current:120m vs Requested:30m (400.00%)
- [POP-505] At current load, Memory under allocated. Current:1102Mi vs Requested:150Mi (734.67%)
- [POP-106] No resources requests/limits defined
- [POP-107] No resource limits defined
DEPLOYMENTS (33 SCANNED)
1
25
0
7
21%
-
botkube/botkube
- botkube
- [POP-106] No resources requests/limits defined
cooptation/cooptation-api
- [POP-106] No resources requests/limits defined
- [POP-106] No resources requests/limits defined
cooptation/cooptation-web
- [POP-106] No resources requests/limits defined
intranet/intranet-mysql
- [POP-107] No resource limits defined
- [POP-107] No resource limits defined
intranet/intranet-wordpress
- [POP-107] No resource limits defined
- [POP-107] No resource limits defined
kivaou/kivaou-front
- [POP-106] No resources requests/limits defined
kivaou/kivaou-mongodb
- [POP-107] No resource limits defined
kube-system/cilium-operator
- [POP-106] No resources requests/limits defined
kube-system/metrics-server
- [POP-107] No resource limits defined
les-projets-cagnottes/les-projets-cagnottes-api
- [POP-106] No resources requests/limits defined
materiel/materiel-mysql
- [POP-107] No resource limits defined
- [POP-107] No resource limits defined
materiel/materiel-snipeit
- [POP-100] Untagged docker image in use
- [POP-106] No resources requests/limits defined
- [POP-106] No resources requests/limits defined
monitoring/oauth2-proxy
- [POP-106] No resources requests/limits defined
monitoring/popeye-nginx
- [POP-106] No resources requests/limits defined
val-system/cert-manager
- [POP-106] No resources requests/limits defined
val-system/cert-manager-cainjector
- [POP-106] No resources requests/limits defined
val-system/cert-manager-webhook
- [POP-106] No resources requests/limits defined
val-system/cnpg-cloudnative-pg
- [POP-106] No resources requests/limits defined
val-system/emberstack-reflector
- [POP-106] No resources requests/limits defined
val-system/external-secrets
- [POP-106] No resources requests/limits defined
val-system/external-secrets-cert-controller
- [POP-106] No resources requests/limits defined
val-system/external-secrets-webhook
- [POP-106] No resources requests/limits defined
val-system/scaleway-certmanager-webhook
- [POP-106] No resources requests/limits defined
val-system/traefik
- [POP-106] No resources requests/limits defined
velero/velero
- [POP-106] No resources requests/limits defined
- [POP-106] No resources requests/limits defined
velero/velero-ui
- [POP-106] No resources requests/limits defined
GATEWAYS (0 SCANNED)
0
0
0
0
100%
GATEWAYCLASSES (0 SCANNED)
0
0
0
0
100%
HORIZONTALPODAUTOSCALERS (0 SCANNED)
0
0
0
0
100%
HTTPROUTES (0 SCANNED)
0
0
0
0
100%
INGRESSES (9 SCANNED)
0
0
7
2
100%
-
cooptation/cooptation
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
-
kivaou/kivaou
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
- [POP-1403] Ingress backend uses a port#, prefer a named port: 8080
- [POP-1403] Ingress backend uses a port#, prefer a named port: 8080
-
les-projets-cagnottes/les-projets-cagnottes
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
-
monitoring/oauth2-proxy
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
-
monitoring/popeye-report
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
-
n8n/n8n
- [POP-1403] Ingress backend uses a port#, prefer a named port: 5678
-
velero/velero-ui
- [POP-1403] Ingress backend uses a port#, prefer a named port: 3000
JOBS (18 SCANNED)
0
13
0
5
27%
-
gitlab/gitlab-migrations-283f682
- certificates
- [POP-107] No resource limits defined
- configure
- [POP-107] No resource limits defined
- migrations
- [POP-107] No resource limits defined
gitlab/gitlab-minio-create-buckets-b2dffbe
- [POP-107] No resource limits defined
kivaou/bookings-snapshot-29473020
- [POP-106] No resources requests/limits defined
kivaou/bookings-snapshot-29474460
- [POP-106] No resources requests/limits defined
kivaou/bookings-snapshot-29475900
- [POP-106] No resources requests/limits defined
kivaou/bookings-snapshot-29817180
- [POP-106] No resources requests/limits defined
kivaou/kivaou-cron-confirmation-booking-29473020
- [POP-106] No resources requests/limits defined
kivaou/kivaou-cron-confirmation-booking-29474460
- [POP-106] No resources requests/limits defined
kivaou/kivaou-cron-confirmation-booking-29475900
- [POP-106] No resources requests/limits defined
kivaou/kivaou-cron-confirmation-booking-29817180
- [POP-106] No resources requests/limits defined
materiel/materiel-snipeit-requestcleanup-29818260
- [POP-106] No resources requests/limits defined
materiel/materiel-snipeit-requestcleanup-29818320
- [POP-106] No resources requests/limits defined
materiel/materiel-snipeit-requestcleanup-29818380
- [POP-106] No resources requests/limits defined
NAMESPACES (17 SCANNED)
0
0
0
17
100%
NETWORKPOLICIES (3 SCANNED)
0
0
0
3
100%
NODES (3 SCANNED)
0
1
0
2
66%
-
scw-tf-k8s-product-tf-pool-fr-par-2-dev-a5265c
- [POP-710] Memory threshold (80%) reached 107%
PERSISTENTVOLUMES (12 SCANNED)
0
0
0
12
100%
PERSISTENTVOLUMECLAIMS (12 SCANNED)
0
0
1
11
100%
-
cooptation/data-cooptation-postgresql-0
- [POP-400] Used? Unable to locate resource reference
PODS (74 SCANNED)
11
63
0
0
0%
-
botkube/botkube-558c87856f-qxs5l
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- botkube
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
botkube/botkube-558c87856f-vwf4p
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
cooptation/cooptation-api-54956dcbcc-9dsz8
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
cooptation/cooptation-api-54956dcbcc-psqd7
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
cooptation/cooptation-db-cluster-1
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-106] No resources requests/limits defined
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
cooptation/cooptation-web-7c44594f66-8vb8l
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
cooptation/cooptation-web-7c44594f66-xgh9b
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
intranet/intranet-mysql-6f4dcff48c-sdnzd
- [POP-110] Memory Current/Request (230Mi/256Mi) reached user 80% threshold (89%)
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
intranet/intranet-wordpress-7f8cc7f94-qg4nw
- [POP-107] No resource limits defined
- [POP-107] No resource limits defined
kivaou/kivaou-back-5b99d4f9bb-fvd67
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kivaou/kivaou-back-5b99d4f9bb-jrgvv
- [POP-110] Memory Current/Request (180Mi/200Mi) reached user 80% threshold (90%)
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kivaou/kivaou-front-845b8b9fc7-p5wts
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kivaou/kivaou-mongodb-786887bfc5-c62jb
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-107] No resource limits defined
kivaou/kivaou-mongodb-786887bfc5-m4q7k
- [POP-109] CPU Current/Request (137m/150m) reached user 80% threshold (91%)
- [POP-110] Memory Current/Request (219Mi/256Mi) reached user 80% threshold (85%)
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-107] No resource limits defined
kube-system/cilium-l7v8x
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/cilium-m7kgd
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/cilium-operator-5f567c5576-pldv4
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/cilium-z7nk2
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/coredns-fcc85d7cb-p5bhv
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/csi-node-4tg84
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/csi-node-5hlmt
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/csi-node-qmpc6
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/konnectivity-agent-7q74b
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-104] No readiness probe
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/konnectivity-agent-bvkcn
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-104] No readiness probe
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/konnectivity-agent-kmwqn
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-104] No readiness probe
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/metrics-server-6c8d87b6dd-7gnvb
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-107] No resource limits defined
les-projets-cagnottes/les-projets-cagnottes-api-56698cf6d-gntzp
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-106] No resources requests/limits defined
les-projets-cagnottes/les-projets-cagnottes-api-56698cf6d-gwwpg
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-106] No resources requests/limits defined
les-projets-cagnottes/les-projets-cagnottes-slack-events-catcher-5f966c49cc-chmxr
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
les-projets-cagnottes/les-projets-cagnottes-slack-events-catcher-5f966c49cc-qjzhb
- [POP-109] CPU Current/Request (1m/1m) reached user 80% threshold (100%)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
les-projets-cagnottes/les-projets-cagnottes-web-6d9bb9766d-bxj8t
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
les-projets-cagnottes/les-projets-cagnottes-web-6d9bb9766d-hlzrx
- [POP-109] CPU Current/Request (1m/1m) reached user 80% threshold (100%)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
les-projets-cagnottes/lesprojetscagnottes-db-cluster-1
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-106] No resources requests/limits defined
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
materiel/materiel-mysql-5688cd4747-kdjbk
- [POP-110] Memory Current/Request (208Mi/256Mi) reached user 80% threshold (81%)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
materiel/materiel-mysql-5688cd4747-pmh8t
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
materiel/materiel-snipeit-7c7bb84b45-62njp
- [POP-110] Memory Current/Request (108Mi/128Mi) reached user 80% threshold (84%)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-100] Untagged docker image in use
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
materiel/materiel-snipeit-requestcleanup-29818260-w4n8w
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
materiel/materiel-snipeit-requestcleanup-29818320-brq2p
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
materiel/materiel-snipeit-requestcleanup-29818380-v7g4m
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/alloy-64n6n
- [POP-110] Memory Current/Request (44Mi/50Mi) reached user 80% threshold (88%)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-103] No liveness probe
- [POP-105] Readiness uses a port#, prefer a named port
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-102] No probes defined
monitoring/alloy-n866z
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-103] No liveness probe
- [POP-105] Readiness uses a port#, prefer a named port
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-102] No probes defined
monitoring/alloy-p4f5p
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-103] No liveness probe
- [POP-105] Readiness uses a port#, prefer a named port
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-107] No resource limits defined
- [POP-102] No probes defined
monitoring/oauth2-proxy-55588c97ff-857nq
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
monitoring/oauth2-proxy-55588c97ff-tks7n
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
monitoring/popeye-29816280-d2k5d
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/popeye-29816340-8fzts
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/popeye-29817000-d6267
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/popeye-29818380-xp4hp
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/popeye-nginx-5f97d756d-jrfpk
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/pushgateway-prometheus-pushgateway-65ffd69ddb-zq7ft
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
n8n/n8n-7d4fcbc8d7-t5qs9
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
n8n/n8n-7d4fcbc8d7-tlhfc
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
val-system/cert-manager-696988756c-8pzll
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
- [POP-104] No readiness probe
val-system/cert-manager-cainjector-75fc4b748b-xp55d
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
val-system/cert-manager-webhook-766f985c59-7wbqf
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
val-system/cert-manager-webhook-766f985c59-r4hz2
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
val-system/cnpg-cloudnative-pg-84bd9cb476-tlkps
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-106] No resources requests/limits defined
val-system/cnpg-cloudnative-pg-84bd9cb476-xvkbq
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-106] No resources requests/limits defined
val-system/emberstack-reflector-6b9f8766d-28sc2
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-106] No resources requests/limits defined
val-system/emberstack-reflector-6b9f8766d-jldcz
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-106] No resources requests/limits defined
val-system/external-dns-5d4954bb77-jhg7h
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-301] Connects to API Server? ServiceAccount token is mounted
val-system/external-dns-5d4954bb77-t4msm
- [POP-301] Connects to API Server? ServiceAccount token is mounted
val-system/external-secrets-bfb7c98c4-nqmcm
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
val-system/external-secrets-cert-controller-5c44687f97-qnz2n
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
- [POP-103] No liveness probe
- [POP-105] Readiness uses a port#, prefer a named port
val-system/external-secrets-cert-controller-5c44687f97-w4h9r
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
- [POP-103] No liveness probe
- [POP-105] Readiness uses a port#, prefer a named port
val-system/external-secrets-webhook-64d9476d79-4vkjv
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
- [POP-103] No liveness probe
- [POP-105] Readiness uses a port#, prefer a named port
val-system/external-secrets-webhook-64d9476d79-vbbpb
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
- [POP-103] No liveness probe
- [POP-105] Readiness uses a port#, prefer a named port
val-system/scaleway-certmanager-webhook-64d4b9ffbc-psj9f
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
val-system/traefik-c49cd9b66-gkc5z
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
val-system/traefik-c49cd9b66-qbwt9
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
velero/velero-69b7f45c6d-vsrxr
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
velero/velero-69b7f45c6d-xxctn
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
velero/velero-ui-b5cd67d6c-9rgfv
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
velero/velero-ui-b5cd67d6c-xstrc
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
PODDISRUPTIONBUDGETS (5 SCANNED)
0
0
0
5
100%
REPLICASETS (70 SCANNED)
0
0
0
70
100%
ROLES (22 SCANNED)
0
0
0
22
100%
ROLEBINDINGS (24 SCANNED)
0
0
0
24
100%
SECRETS (169 SCANNED)
0
0
136
33
100%
-
botkube/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
botkube/sh.helm.release.v1.botkube.v1
- [POP-400] Used? Unable to locate resource reference
-
botkube/sh.helm.release.v1.botkube.v2
- [POP-400] Used? Unable to locate resource reference
-
botkube/sh.helm.release.v1.botkube.v3
- [POP-400] Used? Unable to locate resource reference
-
botkube/sh.helm.release.v1.botkube.v4
- [POP-400] Used? Unable to locate resource reference
-
cilium-secrets/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
cooptation/access-token-github
- [POP-400] Used? Unable to locate resource reference
-
cooptation/cooptation-db-cluster-ca
- [POP-400] Used? Unable to locate resource reference
-
cooptation/cooptation-db-cluster-replication
- [POP-400] Used? Unable to locate resource reference
-
cooptation/cooptation-db-cluster-server
- [POP-400] Used? Unable to locate resource reference
-
cooptation/cooptation.local-tls
- [POP-400] Used? Unable to locate resource reference
-
cooptation/sh.helm.release.v1.cooptation.v1
- [POP-400] Used? Unable to locate resource reference
-
cooptation/sh.helm.release.v1.cooptation.v2
- [POP-400] Used? Unable to locate resource reference
-
cooptation/sh.helm.release.v1.cooptation.v3
- [POP-400] Used? Unable to locate resource reference
-
cooptation/sh.helm.release.v1.cooptation.v4
- [POP-400] Used? Unable to locate resource reference
-
cooptation/sh.helm.release.v1.cooptation.v5
- [POP-400] Used? Unable to locate resource reference
-
cooptation/sh.helm.release.v1.cooptation.v6
- [POP-400] Used? Unable to locate resource reference
-
cooptation/sh.helm.release.v1.cooptation.v7
- [POP-400] Used? Unable to locate resource reference
-
cooptation/sh.helm.release.v1.cooptation.v8
- [POP-400] Used? Unable to locate resource reference
-
default/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-gitaly-secret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-gitlab-initial-root-password
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-gitlab-kas-secret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-gitlab-runner-secret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-gitlab-shell-host-keys
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-gitlab-shell-secret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-gitlab-suggested-reviewers
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-gitlab-workhorse-secret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-kas-private-api
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-kas-websocket-token
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-minio-secret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-postgresql-password
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-rails-secret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-redis-secret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-registry-database-password
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-registry-httpsecret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-registry-notification
- [POP-400] Used? Unable to locate resource reference
-
gitlab/gitlab-registry-secret
- [POP-400] Used? Unable to locate resource reference
-
gitlab/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
intranet/intranet-mysql-backup-gcs
- [POP-400] Used? Unable to locate resource reference
-
intranet/intranet-mysql-backup-mysql
- [POP-400] Used? Unable to locate resource reference
-
intranet/intranet.local-tls
- [POP-400] Used? Unable to locate resource reference
-
intranet/intranet.valeuriad.fr-tls
- [POP-400] Used? Unable to locate resource reference
-
intranet/sh.helm.release.v1.intranet.v1
- [POP-400] Used? Unable to locate resource reference
-
intranet/sh.helm.release.v1.intranet.v2
- [POP-400] Used? Unable to locate resource reference
-
intranet/sh.helm.release.v1.intranet.v3
- [POP-400] Used? Unable to locate resource reference
-
intranet/sh.helm.release.v1.intranet.v4
- [POP-400] Used? Unable to locate resource reference
-
intranet/sh.helm.release.v1.intranet.v5
- [POP-400] Used? Unable to locate resource reference
-
intranet/sh.helm.release.v1.intranet.v6
- [POP-400] Used? Unable to locate resource reference
-
kivaou/kivaou.local-tls
- [POP-400] Used? Unable to locate resource reference
-
kivaou/mongo
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v10
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v11
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v12
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v3
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v4
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v5
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v6
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v7
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v8
- [POP-400] Used? Unable to locate resource reference
-
kivaou/sh.helm.release.v1.kivaou.v9
- [POP-400] Used? Unable to locate resource reference
-
kube-node-lease/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
kube-public/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
kube-system/cilium-ca
- [POP-400] Used? Unable to locate resource reference
-
kube-system/hubble-relay-client-certs
- [POP-400] Used? Unable to locate resource reference
-
kube-system/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
les-projets-cagnottes/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
les-projets-cagnottes/lesprojetscagnottes-db-cluster-ca
- [POP-400] Used? Unable to locate resource reference
-
les-projets-cagnottes/lesprojetscagnottes-db-cluster-replication
- [POP-400] Used? Unable to locate resource reference
-
les-projets-cagnottes/lesprojetscagnottes-db-cluster-server
- [POP-400] Used? Unable to locate resource reference
-
les-projets-cagnottes/sh.helm.release.v1.les-projets-cagnottes.v1
- [POP-400] Used? Unable to locate resource reference
-
materiel/materiel.local-tls
- [POP-400] Used? Unable to locate resource reference
-
materiel/sh.helm.release.v1.materiel.v1
- [POP-400] Used? Unable to locate resource reference
-
materiel/sh.helm.release.v1.materiel.v2
- [POP-400] Used? Unable to locate resource reference
-
materiel/sh.helm.release.v1.materiel.v3
- [POP-400] Used? Unable to locate resource reference
-
materiel/sh.helm.release.v1.materiel.v4
- [POP-400] Used? Unable to locate resource reference
-
materiel/sh.helm.release.v1.materiel.v5
- [POP-400] Used? Unable to locate resource reference
-
materiel/sh.helm.release.v1.materiel.v6
- [POP-400] Used? Unable to locate resource reference
-
materiel/sh.helm.release.v1.materiel.v7
- [POP-400] Used? Unable to locate resource reference
-
materiel/sh.helm.release.v1.materiel.v8
- [POP-400] Used? Unable to locate resource reference
-
monitoring/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.alloy.v1
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.alloy.v2
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.alloy.v3
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.alloy.v4
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.alloy.v5
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.oauth2-proxy.v1
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.pushgateway.v1
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.pushgateway.v2
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.pushgateway.v3
- [POP-400] Used? Unable to locate resource reference
-
monitoring/sh.helm.release.v1.pushgateway.v4
- [POP-400] Used? Unable to locate resource reference
-
n8n/n8n.valeuriad.fr-tls
- [POP-400] Used? Unable to locate resource reference
-
n8n/sh.helm.release.v1.n8n.v1
- [POP-400] Used? Unable to locate resource reference
-
n8n/sh.helm.release.v1.n8n.v2
- [POP-400] Used? Unable to locate resource reference
-
snipeit/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
val-system/cert-manager-webhook-ca
- [POP-400] Used? Unable to locate resource reference
-
val-system/cnpg-ca-secret
- [POP-400] Used? Unable to locate resource reference
-
val-system/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
val-system/letsencrypt
- [POP-400] Used? Unable to locate resource reference
-
val-system/nginx-ingress-controller-ingress-nginx-admission
- [POP-400] Used? Unable to locate resource reference
-
val-system/scaleway-certmanager-webhook-ca
- [POP-400] Used? Unable to locate resource reference
-
val-system/scwsm-secret
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.cert-manager.v1
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.cert-manager.v2
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.cert-manager.v3
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.cert-manager.v4
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.cnpg.v1
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.cnpg.v2
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.emberstack-reflector.v1
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.external-dns.v1
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.external-dns.v2
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.external-dns.v3
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.external-secrets.v1
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.scaleway-certmanager-webhook.v1
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.scaleway-certmanager-webhook.v2
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.traefik.v1
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.traefik.v2
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.traefik.v3
- [POP-400] Used? Unable to locate resource reference
-
velero/iac-valeuriad-cert-star
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero-ui.v1
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero-ui.v2
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero-ui.v3
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero-ui.v4
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero-ui.v5
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero-ui.v6
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero.v1
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero.v2
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero.v3
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero.v4
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero.v5
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero.v6
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero.v7
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero.v8
- [POP-400] Used? Unable to locate resource reference
-
velero/sh.helm.release.v1.velero.v9
- [POP-400] Used? Unable to locate resource reference
-
velero/velero-repo-credentials
- [POP-400] Used? Unable to locate resource reference
-
velero/velero-ui-passphrase
- [POP-400] Used? Unable to locate resource reference
SERVICES (38 SCANNED)
2
33
1
2
7%
-
botkube/botkube
- [POP-1101] Skip ports check. No explicit ports detected on pod botkube/botkube-558c87856f-qxs5l
- [POP-1109] Single endpoint is associated with this service
-
cooptation/cooptation-api
- [POP-1109] Single endpoint is associated with this service
-
cooptation/cooptation-db-cluster-r
- [POP-1102] Use of target port #5432 for service port TCP:postgres:5432. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
cooptation/cooptation-db-cluster-ro
- [POP-1100] No pods match service selector
- [POP-1110] Match EP has no subsets
-
cooptation/cooptation-db-cluster-rw
- [POP-1102] Use of target port #5432 for service port TCP:postgres:5432. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
cooptation/cooptation-web
- [POP-1109] Single endpoint is associated with this service
-
intranet/intranet-mysql
- [POP-1109] Single endpoint is associated with this service
-
intranet/intranet-wordpress
- [POP-1109] Single endpoint is associated with this service
-
kivaou/kivaou-back
- [POP-1102] Use of target port #8080 for service port TCP:http:8080. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
kivaou/kivaou-front
- [POP-1109] Single endpoint is associated with this service
-
kivaou/kivaou-mongodb
- [POP-1109] Single endpoint is associated with this service
-
kube-system/coredns
- [POP-1102] Use of target port #53 for service port UDP:dns:53. Prefer named port
- [POP-1102] Use of target port #53 for service port TCP:dns-tcp:53. Prefer named port
- [POP-1102] Use of target port #9153 for service port TCP:metrics:9153. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
kube-system/metrics-server
- [POP-1109] Single endpoint is associated with this service
-
les-projets-cagnottes/les-projets-cagnottes-api
- [POP-1109] Single endpoint is associated with this service
-
les-projets-cagnottes/les-projets-cagnottes-slack-events-catcher
- [POP-1109] Single endpoint is associated with this service
-
les-projets-cagnottes/les-projets-cagnottes-web
- [POP-1109] Single endpoint is associated with this service
-
les-projets-cagnottes/lesprojetscagnottes-db-cluster-r
- [POP-1102] Use of target port #5432 for service port TCP:postgres:5432. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
les-projets-cagnottes/lesprojetscagnottes-db-cluster-ro
- [POP-1100] No pods match service selector
- [POP-1110] Match EP has no subsets
-
les-projets-cagnottes/lesprojetscagnottes-db-cluster-rw
- [POP-1102] Use of target port #5432 for service port TCP:postgres:5432. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
materiel/materiel-mysql
- [POP-1109] Single endpoint is associated with this service
-
materiel/materiel-snipeit
- [POP-1102] Use of target port #80 for service port TCP:http:80. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
monitoring/alloy
- [POP-1102] Use of target port #12345 for service port TCP:http-metrics:12345. Prefer named port
-
monitoring/oauth2-proxy
- [POP-1109] Single endpoint is associated with this service
-
monitoring/popeye-nginx
- [POP-1102] Use of target port #80 for service port TCP:http:80. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
monitoring/pushgateway-prometheus-pushgateway
- [POP-1102] Use of target port #9091 for service port TCP:http:9091. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
n8n/n8n
- [POP-1109] Single endpoint is associated with this service
-
val-system/cert-manager
- [POP-1102] Use of target port #9402 for service port TCP:http-metrics:9402. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
val-system/cert-manager-cainjector
- [POP-1102] Use of target port #9402 for service port TCP:http-metrics:9402. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
val-system/cert-manager-webhook
- [POP-1109] Single endpoint is associated with this service
-
val-system/cnpg-webhook-service
- [POP-1109] Single endpoint is associated with this service
-
val-system/external-dns
- [POP-1109] Single endpoint is associated with this service
-
val-system/external-secrets-webhook
- [POP-1102] Use of target port #10250 for service port TCP:webhook:443. Prefer named port
- [POP-1109] Single endpoint is associated with this service
-
val-system/scaleway-certmanager-webhook
- [POP-1109] Single endpoint is associated with this service
-
val-system/traefik
- [POP-1109] Single endpoint is associated with this service
- [POP-1103] Type LoadBalancer detected. Could be expensive
- [POP-1107] LoadBalancer detected but service sets externalTrafficPolicy to "Cluster"
-
velero/velero
- [POP-1109] Single endpoint is associated with this service
-
velero/velero-ui
- [POP-1109] Single endpoint is associated with this service
SERVICEACCOUNTS (86 SCANNED)
1
10
0
75
87%
-
kivaou/kivaou-mongodb
- [POP-304] References a secret "kivaou/kivaou-mongodb" which does not exist
-
monitoring/alloy
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
-
monitoring/oauth2-proxy
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
-
monitoring/popeye
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
-
monitoring/pushgateway-prometheus-pushgateway
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
-
n8n/n8n
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
-
val-system/cert-manager
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
-
val-system/cert-manager-cainjector
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
-
val-system/cert-manager-webhook
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
-
velero/velero-server
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
-
velero/velero-ui
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
STATEFULSETS (0 SCANNED)
0
0
0
0
100%