Popeye Scan Report
Scanned
n/a/n/a
2026-07-13T07:00:12Z
C
79
CILIUMCLUSTERWIDENETWORKPOLICIES (0 SCANNED)
0
0
0
0
100%
CILIUMENDPOINTS (42 SCANNED)
1
0
0
41
97%
-
materiel/materiel-snipeit-requestcleanup-29732100-htv54
- [POP-1703] Pod owner is not in a running state: materiel/materiel-snipeit-requestcleanup-29732100-htv54 (ContainerCreating)
CILIUMIDENTITIES (108 SCANNED)
0
68
0
40
37%
-
cooptation/49389
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
les-projets-cagnottes/59925
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/11519
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/11573
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/13462
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/13996
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/14043
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/14160
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/14259
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/16509
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/16689
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/16808
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/17877
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/18135
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/20475
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/20764
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/22458
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/23152
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/23414
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/2429
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/26325
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/26530
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/2788
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/29902
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/30186
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/30606
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/31677
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/3440
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/34683
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/35193
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/3990
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/4119
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/41301
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/42944
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/43523
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/43722
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/43840
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/44246
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/45311
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/45952
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/46221
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/46404
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/47361
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/48284
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/50757
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/53133
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/56566
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/57189
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/57505
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/58332
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/6025
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/60514
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/6382
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/64520
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/6592
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/6907
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/710
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/7287
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/8002
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/8312
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/8858
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/912
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
materiel/9464
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
monitoring/20040
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
monitoring/2049
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
monitoring/3255
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
monitoring/8154
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
-
weblex/13702
- [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 (106 SCANNED)
0
0
5
101
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 (88 SCANNED)
0
4
0
84
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 (51 SCANNED)
0
0
18
33
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
-
val-system/nginx-ingress-controller-ingress-nginx-controller
- [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
-
weblex/cnpg-default-monitoring
- [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-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:1179Mi vs Requested:330Mi (357.27%)
- 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
- install-cni-binaries
- [POP-107] No resource 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:145m vs Requested:30m (483.33%)
- [POP-505] At current load, Memory under allocated. Current:1156Mi vs Requested:150Mi (770.67%)
- [POP-106] No resources requests/limits defined
- [POP-107] No resource limits defined
DEPLOYMENTS (35 SCANNED)
1
27
0
7
20%
-
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/nginx-ingress-controller-ingress-nginx-controller
- [POP-107] No resource 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
weblex/weblex
- [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 (10 SCANNED)
0
0
8
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
-
weblex/weblex
- [POP-1403] Ingress backend uses a port#, prefer a named port: 8501
JOBS (19 SCANNED)
0
14
0
5
26%
-
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-29727900
- [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-29727900
- [POP-106] No resources requests/limits defined
materiel/materiel-snipeit-requestcleanup-29731920
- [POP-106] No resources requests/limits defined
materiel/materiel-snipeit-requestcleanup-29731980
- [POP-106] No resources requests/limits defined
materiel/materiel-snipeit-requestcleanup-29732040
- [POP-106] No resources requests/limits defined
materiel/materiel-snipeit-requestcleanup-29732100
- [POP-106] No resources requests/limits defined
NAMESPACES (18 SCANNED)
0
0
0
18
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-1-dev-4598f7
- [POP-710] Memory threshold (80%) reached 110%
PERSISTENTVOLUMES (13 SCANNED)
0
0
0
13
100%
PERSISTENTVOLUMECLAIMS (13 SCANNED)
0
0
1
12
100%
-
cooptation/data-cooptation-postgresql-0
- [POP-400] Used? Unable to locate resource reference
PODS (75 SCANNED)
17
58
0
0
0%
-
botkube/botkube-9b8db96bc-ccbhw
- [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-9b8db96bc-jxrcj
- [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-txgw4
- [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-c5rpz
- [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-pgmt7
- [POP-110] Memory Current/Request (218Mi/256Mi) reached user 80% threshold (85%)
- [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-nw96s
- [POP-107] No resource limits defined
- [POP-107] No resource limits defined
kivaou/kivaou-back-5b99d4f9bb-2gbll
- [POP-110] Memory Current/Request (173Mi/200Mi) reached user 80% threshold (86%)
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- [POP-205] Pod was restarted (9) times
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kivaou/kivaou-back-5b99d4f9bb-w5msg
- [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-front-845b8b9fc7-f47mf
- [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-front-845b8b9fc7-j75p7
- [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-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kivaou/kivaou-mongodb-786887bfc5-2kfdb
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-107] No resource limits defined
kube-system/cilium-56c76
- [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-205] Pod was restarted (136) times
- [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
- [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-205] Pod was restarted (43) times
- [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-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/cilium-operator-68758d8dc7-dmckj
- [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-205] Pod was restarted (211) times
- [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
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/cilium-w5jp5
- [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-205] Pod was restarted (182) times
- [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
- [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-205] Pod was restarted (174) times
- [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-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/cilium-w92xw
- [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-205] Pod was restarted (181) times
- [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
- [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-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-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
kube-system/coredns-64bc75b9b-5t7k7
- [POP-110] Memory Current/Request (87Mi/70Mi) reached user 80% threshold (124%)
- [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-7mmlf
- [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-205] Pod was restarted (173) times
- [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-205] Pod was restarted (173) times
- [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-qqth7
- [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-205] Pod was restarted (129) times
- [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-205] Pod was restarted (129) times
- [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-xm6sj
- [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-205] Pod was restarted (174) times
- [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-205] Pod was restarted (174) times
- [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-8nh6k
- [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-205] Pod was restarted (36) times
- [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-f8wrg
- [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-205] Pod was restarted (36) times
- [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-l85pv
- [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-205] Pod was restarted (36) times
- [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-7c4f55784d-2swsl
- [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-h4sw5
- [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-fdhl9
- [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-slack-events-catcher-5f966c49cc-ss88p
- [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-bclg6
- [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-d7w76
- [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/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-wnnnj
- [POP-110] Memory Current/Request (219Mi/256Mi) reached user 80% threshold (85%)
- [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-c4bcdffbd-lpch8
- [POP-110] Memory Current/Request (117Mi/128Mi) reached user 80% threshold (91%)
- [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-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
- [POP-205] Pod was restarted (11) times
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
materiel/materiel-snipeit-requestcleanup-29731920-bk4q5
- [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-29731980-dqh52
- [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-29732040-876tc
- [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-29732100-htv54
- [POP-207] Pod is in an unhappy phase (Pending)
- [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-203] Pod is waiting [0/1] ContainerCreating
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/alloy-gpjm7
- [POP-110] Memory Current/Request (46Mi/50Mi) reached user 80% threshold (92%)
- [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
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/alloy-lqs4g
- [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
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/alloy-nnm76
- [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
- [POP-306] Container could be running as root user. Check SecurityContext/Image
monitoring/oauth2-proxy-55588c97ff-dwkvx
- [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-k8lgw
- [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-106] No resources requests/limits defined
monitoring/popeye-29728500-4j66b
- [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-29732040-bgpdq
- [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-29732100-4tmkq
- [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-fg4nq
- [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-554fb89dfd-dp6s8
- [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
monitoring/pushgateway-prometheus-pushgateway-554fb89dfd-sqxsc
- [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-jv5kw
- [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-7ccbc46c67-28r28
- [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-655bb66698-kbb5r
- [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-586666dcd7-fqs4f
- [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-6676594c84-gbm74
- [POP-207] Pod is in an unhappy phase (Failed)
- [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
val-system/cnpg-cloudnative-pg-6676594c84-zfxlw
- [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
val-system/emberstack-reflector-6b9f8766d-j2b52
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-106] No resources requests/limits defined
val-system/external-dns-747b8cd76c-6lr56
- [POP-301] Connects to API Server? ServiceAccount token is mounted
val-system/external-dns-747b8cd76c-c4nw6
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-301] Connects to API Server? ServiceAccount token is mounted
val-system/external-secrets-bfb7c98c4-dnjfp
- [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-102] No probes defined
val-system/external-secrets-bfb7c98c4-v58cf
- [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-9gjqr
- [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-948m8
- [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-lxmpm
- [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/nginx-ingress-controller-ingress-nginx-controller-784b6497hn8tg
- [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-107] No resource limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
val-system/nginx-ingress-controller-ingress-nginx-controller-784b6497z8xgn
- [POP-110] Memory Current/Request (74Mi/90Mi) reached user 80% threshold (82%)
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-107] No resource limits defined
- [POP-105] Liveness uses a port#, prefer a named port
- [POP-105] Readiness uses a port#, prefer a named port
val-system/scaleway-certmanager-webhook-d965f986f-26wtl
- [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/scaleway-certmanager-webhook-d965f986f-8h92f
- [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-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
val-system/traefik-7bd6bdbf5d-2gj7x
- [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
val-system/traefik-7bd6bdbf5d-87j89
- [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-6747bf9f65-5ptwh
- [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-6747bf9f65-b9s5q
- [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-203] Pod is waiting [0/1] PodInitializing
- [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-6ff554765b-4sq27
- [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-6ff554765b-hk5wg
- [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-6ff554765b-qvvv8
- [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
weblex/weblex-67c8d57f74-n25pn
- [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-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
weblex/weblex-67c8d57f74-s2hgs
- [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-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
weblex/weblex-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
PODDISRUPTIONBUDGETS (6 SCANNED)
0
0
0
6
100%
REPLICASETS (52 SCANNED)
0
0
0
52
100%
ROLES (25 SCANNED)
0
0
0
25
100%
ROLEBINDINGS (27 SCANNED)
0
0
0
27
100%
SECRETS (158 SCANNED)
0
0
119
39
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
-
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/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.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
-
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/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.cnpg.v1
- [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-secrets.v1
- [POP-400] Used? Unable to locate resource reference
-
val-system/sh.helm.release.v1.nginx-ingress-controller.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.traefik.v1
- [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.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/velero-repo-credentials
- [POP-400] Used? Unable to locate resource reference
-
velero/velero-ui-passphrase
- [POP-400] Used? Unable to locate resource reference
-
weblex/sh.helm.release.v1.weblex.v1
- [POP-400] Used? Unable to locate resource reference
-
weblex/weblex-db-cluster-ca
- [POP-400] Used? Unable to locate resource reference
-
weblex/weblex-db-cluster-replication
- [POP-400] Used? Unable to locate resource reference
-
weblex/weblex-db-cluster-server
- [POP-400] Used? Unable to locate resource reference
SERVICES (44 SCANNED)
3
38
1
2
6%
-
botkube/botkube
- [POP-1101] Skip ports check. No explicit ports detected on pod botkube/botkube-9b8db96bc-ccbhw
- [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-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/nginx-ingress-controller-ingress-nginx-controller
- [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"
-
val-system/nginx-ingress-controller-ingress-nginx-controller-admission
- [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
-
weblex/weblex
- [POP-1109] Single endpoint is associated with this service
-
weblex/weblex-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
-
weblex/weblex-db-cluster-ro
- [POP-1100] No pods match service selector
- [POP-1110] Match EP has no subsets
-
weblex/weblex-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
SERVICEACCOUNTS (87 SCANNED)
1
11
0
75
86%
-
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
-
val-system/nginx-ingress-controller-ingress-nginx
- [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%