Popeye Scan Report

Scanned n/a/n/a

2026-05-12T14:11:59Z

C 77

CILIUMCLUSTERWIDENETWORKPOLICIES (0 SCANNED)

0 0 0 0 100%

CILIUMENDPOINTS (54 SCANNED)

0 0 0 54 100%

CILIUMIDENTITIES (74 SCANNED)

0 21 0 53 71%

gitlab/10104
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/1319
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/19215
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/19689
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/22302
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/31298
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/35005
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/4188
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/42150
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/46056
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/47808
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/52788
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/53190
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/56109
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/60377
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/62892
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/6684
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/7971
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/9185
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
gitlab/9651
- [POP-1600] Stale? unable to locate matching Cilium Endpoint
monitoring/16288
- [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 (72 SCANNED)

0 0 22 50 100%

bcdc/cnpg-default-monitoring
- [POP-400] Used? Unable to locate resource reference
botkube/botkube-system
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-certmanager-issuer-certmanager
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-gitlab-chart-info
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-gitlab-upgrade-check
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-migrations
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-minio-config-cm
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-nginx-ingress-tcp
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-webservice-tests
- [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
outils/cnpg-default-monitoring
- [POP-400] Used? Unable to locate resource reference
pilotage/cnpg-default-monitoring
- [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
val-system/nginx-ingress-controller-ingress-nginx-tcp
- [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 3 1 1 40%

bcdc/bcdc
- [POP-1501] No active jobs detected
- bcdc
gitlab/gitlab-toolbox-backup
- [POP-1501] No active jobs detected
- certificates
- configure
- toolbox-backup
kube-system/hubble-generate-certs
- [POP-1501] No active jobs detected
- certgen
pilotage/pilotage-etl
- [POP-1501] No active jobs detected

DAEMONSETS (5 SCANNED)

1 4 0 0 0%

kube-system/cilium
- [POP-505] At current load, Memory under allocated. Current:1089Mi vs Requested:440Mi (247.50%)
- apply-sysctl-overwrites
- cilium-agent
- clean-cilium-state
- config
- install-cni-binaries
- mount-bpf-fs
- mount-cgroup
kube-system/csi-node
- csi-node-driver-registrar
- csi-plugin
kube-system/konnectivity-agent
- konnectivity-agent
kube-system/kube-proxy
- [POP-508] No pods match controller selector: app=kube-proxy
- kube-proxy
monitoring/alloy
- [POP-503] At current load, CPU under allocated. Current:134m vs Requested:20m (670.00%)
- [POP-505] At current load, Memory under allocated. Current:639Mi vs Requested:100Mi (639.00%)
- alloy
- config-reloader

DEPLOYMENTS (42 SCANNED)

1 34 0 7 16%

bcdc/bcdc-back
- bcdc-back
bcdc/bcdc-front
- bcdc-front
bcdc/bcdc-superset
- superset
- wait-for-postgres
bcdc/bcdc-superset-worker
- superset
- wait-for-postgres-redis
botkube/botkube
- botkube
gitlab/gitlab-gitlab-exporter
- certificates
- configure
- gitlab-exporter
gitlab/gitlab-gitlab-pages
- certificates
- configure
- gitlab-pages
gitlab/gitlab-gitlab-runner
- gitlab-gitlab-runner
gitlab/gitlab-gitlab-shell
- [POP-503] At current load, CPU under allocated. Current:286m vs Requested:100m (286.00%)
- [POP-505] At current load, Memory under allocated. Current:45Mi vs Requested:5Mi (900.00%)
- certificates
- configure
- gitlab-shell
gitlab/gitlab-sidekiq-all-in-1-v2
- certificates
- configure
- dependencies
gitlab/gitlab-toolbox
- certificates
- configure
- toolbox
gitlab/gitlab-webservice-default
- certificates
- configure
- dependencies
- gitlab-workhorse
kube-system/cilium-operator
- cilium-operator
kube-system/metrics-server
- metrics-server
monitoring/oauth2-proxy
- oauth2-proxy
monitoring/popeye-nginx
- nginx
outils/glpi
- wait-for-db
pilotage/pilotage-superset
- wait-for-postgres
pilotage/pilotage-superset-worker
- superset
- wait-for-postgres-redis
streamlit/streamlit
- [POP-500] Zero scale detected
- [POP-508] No pods match controller selector: app.kubernetes.io/instance=streamlit,app.kubernetes.io/name=streamlit
val-system/cert-manager
- cert-manager-controller
val-system/cert-manager-cainjector
- cert-manager-cainjector
val-system/cert-manager-webhook
- cert-manager-webhook
val-system/cnpg-cloudnative-pg
- manager
val-system/external-secrets
- external-secrets
val-system/external-secrets-cert-controller
- cert-controller
val-system/external-secrets-webhook
- webhook
val-system/nginx-ingress-controller-ingress-nginx-controller
- controller
val-system/scaleway-certmanager-webhook
- scaleway-certmanager-webhook
val-system/traefik
- traefik
velero/velero
- velero
- velero-plugin-for-aws
velero/velero-ui
- velero-ui
whoz-sync-middleware/redis-explorer
- redis-commander
whoz-sync-middleware/whoz-sync-middleware-app
- [POP-505] At current load, Memory under allocated. Current:298Mi vs Requested:128Mi (232.81%)
- app
- db-explorer
- migrations
whoz-sync-middleware/whoz-sync-middleware-redis
- init-redis
- redis

GATEWAYS (0 SCANNED)

0 0 0 0 100%

GATEWAYCLASSES (0 SCANNED)

0 0 0 0 100%

HORIZONTALPODAUTOSCALERS (4 SCANNED)

0 0 0 4 100%

HTTPROUTES (0 SCANNED)

0 0 0 0 100%

INGRESSES (16 SCANNED)

2 0 10 4 87%

bcdc/bcdc
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
bcdc/bcdc-phoenix
- [POP-1403] Ingress backend uses a port#, prefer a named port: 443
gitlab/gitlab-gitlab-pages
- [POP-1403] Ingress backend uses a port#, prefer a named port: 8090
gitlab/gitlab-webservice-default
- [POP-1403] Ingress backend uses a port#, prefer a named port: 8181
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
outils/outils-wiki
- [POP-1403] Ingress backend uses a port#, prefer a named port: 80
streamlit/cm-acme-http-solver-h5gx5
- [POP-1403] Ingress backend uses a port#, prefer a named port: 8089
streamlit/streamlit
- [POP-1402] Ingress references a service port which is not defined: :8501
- [POP-1403] Ingress backend uses a port#, prefer a named port: 8501
trombinoscope/trombinoscope
- [POP-1402] Ingress references a service port which is not defined: :5000
- [POP-1403] Ingress backend uses a port#, prefer a named port: 5000
velero/velero-ui
- [POP-1403] Ingress backend uses a port#, prefer a named port: 3000

JOBS (23 SCANNED)

0 10 0 13 56%

bcdc/bcdc-superset-init-db
- superset-init-db
- wait-for-postgres
gitlab/gitlab-migrations-3a920a5
- certificates
- configure
- migrations
gitlab/gitlab-migrations-3eed7f9
- certificates
- configure
- migrations
gitlab/gitlab-migrations-4c19501
- certificates
- configure
- migrations
gitlab/gitlab-migrations-57fde49
- certificates
- configure
- migrations
gitlab/gitlab-migrations-603b6ef
- certificates
- configure
- migrations
gitlab/gitlab-migrations-a649578
- certificates
- configure
- migrations
gitlab/gitlab-toolbox-backup-29640240
- certificates
- configure
- toolbox-backup
gitlab/gitlab-toolbox-backup-29641680
- certificates
- configure
- toolbox-backup
gitlab/gitlab-toolbox-backup-29643120
- certificates
- configure
- toolbox-backup

NAMESPACES (19 SCANNED)

0 0 0 19 100%

NETWORKPOLICIES (2 SCANNED)

0 0 0 2 100%

NODES (4 SCANNED)

0 2 0 2 50%

scw-tf-k8s-crit-tf-pool-noshutdown-fr-p-61e92f
- [POP-710] Memory threshold (80%) reached 96%
scw-tf-k8s-critiq-tf-pool-fr-par-1-dev1-8bb732
- [POP-710] Memory threshold (80%) reached 88%

PERSISTENTVOLUMES (25 SCANNED)

0 0 0 25 100%

PERSISTENTVOLUMECLAIMS (21 SCANNED)

0 0 4 17 100%

outils/data-outils-elasticsearch-master-0
- [POP-400] Used? Unable to locate resource reference
outils/data-outils-redis-0
- [POP-400] Used? Unable to locate resource reference
outils/glpi-plugins
- [POP-400] Used? Unable to locate resource reference
pilotage/data-pilotage-postgresql-0
- [POP-400] Used? Unable to locate resource reference

PODS (123 SCANNED)

50 73 0 0 0%

bcdc/bcdc-back-5498fc5fc8-hjcj6
- [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
- bcdc-back
bcdc/bcdc-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
- bootstrap-controller
- postgres
bcdc/bcdc-front-cf7876d4d-85rvg
- [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
- bcdc-front
bcdc/bcdc-phoenix-0
- [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
- bcdc-phoenix
bcdc/bcdc-redis-master-0
- [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
- redis
bcdc/bcdc-superset-5ddbc6fff7-6bm46
- [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
- superset
- wait-for-postgres
bcdc/bcdc-superset-worker-57bb4889bc-vsjl9
- [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
- superset
- wait-for-postgres-redis
botkube/botkube-9d98ddc6f-27spb
- [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
gitlab/garage-0
- [POP-206] Pod has no associated PodDisruptionBudget
- garage
gitlab/gitlab-gitaly-0
- [POP-110] Memory Current/Request (207Mi/200Mi) reached user 80% threshold (103%)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- gitaly
gitlab/gitlab-gitlab-exporter-854f784584-5f2kp
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- gitlab-exporter
gitlab/gitlab-gitlab-pages-7cc475b56c-k6w7p
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- gitlab-pages
gitlab/gitlab-gitlab-runner-9c55b7486-chllg
- [POP-206] Pod has no associated PodDisruptionBudget
- gitlab-gitlab-runner
gitlab/gitlab-gitlab-shell-7856f6b6b5-lv76q
- [POP-110] Memory Current/Request (45Mi/5Mi) reached user 80% threshold (900%)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- gitlab-shell
gitlab/gitlab-postgresql-0
- [POP-110] Memory Current/Request (477Mi/256Mi) reached user 80% threshold (186%)
- [POP-206] Pod has no associated PodDisruptionBudget
- metrics
- postgresql
gitlab/gitlab-redis-master-0
- [POP-109] CPU Current/Request (26m/10m) reached user 80% threshold (260%)
- [POP-206] Pod has no associated PodDisruptionBudget
- metrics
- redis
gitlab/gitlab-sidekiq-all-in-1-v2-87d4945ff-654kr
- [POP-109] CPU Current/Request (210m/50m) reached user 80% threshold (420%)
- [POP-110] Memory Current/Request (1116Mi/596Mi) reached user 80% threshold (187%)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- sidekiq
gitlab/gitlab-toolbox-5c58c485cc-4vlqc
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- toolbox
gitlab/gitlab-toolbox-backup-29640240-nr79t
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- toolbox-backup
gitlab/gitlab-toolbox-backup-29641680-w2vn5
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- toolbox-backup
gitlab/gitlab-toolbox-backup-29643120-hbfqn
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- toolbox-backup
gitlab/gitlab-webservice-default-8568bf8965-65fvv
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-6b72r
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-74wst
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-92f72
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-9jbzh
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-9v76r
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-bq92k
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-c8s6d
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-clgj2
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-cqcfj
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-d87tq
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-gbbgr
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-gjqng
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-jk99t
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-jsf2d
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-mdgvj
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-mh2sz
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-nwgfp
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-rhj2f
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-rhs29
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-s7vjk
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-sch8r
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-thfch
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-v6zxh
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-v8n4k
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-vm2dw
- [POP-109] CPU Current/Request (246m/100m) reached user 80% threshold (246%)
- [POP-110] Memory Current/Request (2364Mi/858Mi) reached user 80% threshold (275%)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-vwdbp
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-wxvc8
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-xkp4j
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-zc5b9
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
gitlab/gitlab-webservice-default-8568bf8965-ztlfn
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-300] Uses "default" ServiceAccount
- certificates
- configure
- dependencies
- gitlab-workhorse
- webservice
kube-system/cilium-hxbn2
- [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
- apply-sysctl-overwrites
- cilium-agent
- clean-cilium-state
- config
- install-cni-binaries
- mount-bpf-fs
- mount-cgroup
kube-system/cilium-jvf68
- [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
- apply-sysctl-overwrites
- cilium-agent
- clean-cilium-state
- config
- install-cni-binaries
- mount-bpf-fs
- mount-cgroup
kube-system/cilium-l27xp
- [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
- apply-sysctl-overwrites
- cilium-agent
- clean-cilium-state
- config
- install-cni-binaries
- mount-bpf-fs
- mount-cgroup
kube-system/cilium-n6psr
- [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
- apply-sysctl-overwrites
- cilium-agent
- clean-cilium-state
- config
- install-cni-binaries
- mount-bpf-fs
- mount-cgroup
kube-system/cilium-operator-d4fc759dc-csq29
- [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
- cilium-operator
kube-system/coredns-7f7dd78795-64sct
- [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
- coredns
kube-system/csi-node-8fjw5
- [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
- csi-node-driver-registrar
- csi-plugin
kube-system/csi-node-rg7wk
- [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
- csi-node-driver-registrar
- csi-plugin
kube-system/csi-node-xblz2
- [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
- csi-node-driver-registrar
- csi-plugin
kube-system/csi-node-xr6gf
- [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
- csi-node-driver-registrar
- csi-plugin
kube-system/konnectivity-agent-6ddq7
- [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
- konnectivity-agent
kube-system/konnectivity-agent-fpr5d
- [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
- konnectivity-agent
kube-system/konnectivity-agent-hhpzd
- [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
- konnectivity-agent
kube-system/konnectivity-agent-n24dt
- [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
- konnectivity-agent
kube-system/metrics-server-7c4f55784d-vpfvk
- [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
- metrics-server
monitoring/alloy-2dk2j
- [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
- alloy
- config-reloader
monitoring/alloy-s4xxg
- [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
- alloy
- config-reloader
monitoring/oauth2-proxy-9d6644bc-bdn9s
- [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
- oauth2-proxy
monitoring/popeye-29643000-b92lf
- [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
- popeye
monitoring/popeye-29643000-m57rc
- [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
- popeye
monitoring/popeye-29643000-nszl5
- [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
- popeye
monitoring/popeye-29643060-4vlf2
- [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
- popeye
monitoring/popeye-29643060-5xr9g
- [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
- popeye
monitoring/popeye-29643060-8frdf
- [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
- popeye
monitoring/popeye-29643060-bfzpq
- [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
- popeye
monitoring/popeye-29643060-hq7bv
- [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
- popeye
monitoring/popeye-29643060-k4296
- [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
- popeye
monitoring/popeye-29643060-z8cxj
- [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
- popeye
monitoring/popeye-29643120-cxp4j
- [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
- popeye
monitoring/popeye-29643180-77fgg
- [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
- popeye
monitoring/popeye-29643180-hc8d2
- [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
- popeye
monitoring/popeye-29643180-shzcz
- [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
- popeye
monitoring/popeye-29643240-2g5dd
- [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
- popeye
monitoring/popeye-29643240-gzqhh
- [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
- popeye
monitoring/popeye-29643240-h2v5w
- [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
- popeye
monitoring/popeye-29643240-l7gk4
- [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
- popeye
monitoring/popeye-29643240-r6mmr
- [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
- popeye
monitoring/popeye-29643240-rn79s
- [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
- popeye
monitoring/popeye-29643240-rwmkf
- [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
- popeye
monitoring/popeye-nginx-5f97d756d-p9hsf
- [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
- nginx
monitoring/pushgateway-prometheus-pushgateway-554fb89dfd-zspck
- [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
- pushgateway
n8n/n8n-65745fb8d7-mwjjc
- [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
outils/glpi-55885fdd87-r595q
- [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
- glpi
- wait-for-db
outils/glpi-mysql-5987f74fb7-nbwwr
- [POP-110] Memory Current/Request (568Mi/512Mi) reached user 80% threshold (110%)
- [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
- mysql
outils/outils-wiki-5b4b97898-bv5w2
- [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
- wiki
outils/outils-wiki-5b4b97898-p4nkr
- [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
- wiki
outils/wikijs-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
- bootstrap-controller
- postgres
pilotage/pilotage-db-1
- [POP-1204] Pod ingress is not secured by a network policy
- [POP-1204] Pod egress is not secured by a network policy
- bootstrap-controller
- postgres
pilotage/pilotage-redis-master-0
- [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
- redis
pilotage/pilotage-superset-768476fc4b-ljz6r
- [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
- superset
- wait-for-postgres
pilotage/pilotage-superset-worker-66db748774-nrtkf
- [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
- superset
- wait-for-postgres-redis
streamlit/cm-acme-http-solver-sh2gl
- [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
- acmesolver
trombinoscope/trombinoscope-69cd6c6d76-ph6kt
- [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
- trombinoscope
val-system/cert-manager-cainjector-655bb66698-srs8m
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- cert-manager-cainjector
val-system/cert-manager-f97bfdc8c-r4fg6
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- cert-manager-controller
val-system/cert-manager-webhook-586666dcd7-zzhkg
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- cert-manager-webhook
val-system/cnpg-cloudnative-pg-67d4577fcb-4qjx6
- [POP-206] Pod has no associated PodDisruptionBudget
- manager
val-system/cnpg-cloudnative-pg-67d4577fcb-nx9nz
- [POP-207] Pod is in an unhappy phase (Failed)
- [POP-206] Pod has no associated PodDisruptionBudget
- manager
val-system/external-dns-67f7f7f7b5-d2ltb
- [POP-301] Connects to API Server? ServiceAccount token is mounted
val-system/external-secrets-685fb8b7d6-kbgzf
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- external-secrets
val-system/external-secrets-cert-controller-5c44687f97-nrljd
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- cert-controller
val-system/external-secrets-webhook-64d9476d79-2svbt
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- webhook
val-system/nginx-ingress-controller-ingress-nginx-controller-6d669d75qgbfj
- [POP-110] Memory Current/Request (83Mi/90Mi) reached user 80% threshold (92%)
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
val-system/scaleway-certmanager-webhook-8c97d5557-wvjq7
- [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
- scaleway-certmanager-webhook
val-system/scaleway-certmanager-webhook-8c97d5557-x5wjp
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- scaleway-certmanager-webhook
val-system/traefik-688957bc9d-db8bg
- [POP-206] Pod has no associated PodDisruptionBudget
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- traefik
velero/velero-6747bf9f65-c9fm4
- [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
- velero
- velero-plugin-for-aws
velero/velero-ui-68c7c958b9-fmgjq
- [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
- velero-ui
whoz-sync-middleware/redis-explorer-b764b9bf-2j9q4
- [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
- redis-commander
whoz-sync-middleware/whoz-sync-middleware-app-55bdf5bf56-45bpj
- [POP-110] Memory Current/Request (260Mi/128Mi) reached user 80% threshold (203%)
- [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
- app
- db-explorer
- migrations
whoz-sync-middleware/whoz-sync-middleware-redis-57d7768845-vg9dl
- [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
- init-redis
- redis

PODDISRUPTIONBUDGETS (11 SCANNED)

0 1 0 10 90%

gitlab/gitlab-minio-v1
- [POP-900] No pods match pdb selector: component=app,release=gitlab,app=minio

REPLICASETS (161 SCANNED)

0 0 0 161 100%

ROLES (27 SCANNED)

0 0 0 27 100%

ROLEBINDINGS (29 SCANNED)

0 0 0 29 100%

SECRETS (195 SCANNED)

0 0 135 60 100%

bcdc/bcdc-db-cluster-ca
- [POP-400] Used? Unable to locate resource reference
bcdc/bcdc-db-cluster-replication
- [POP-400] Used? Unable to locate resource reference
bcdc/bcdc-db-cluster-server
- [POP-400] Used? Unable to locate resource reference
bcdc/boondmanager-creds
- [POP-400] Used? Unable to locate resource reference
bcdc/db
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v10
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v11
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v2
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v3
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v4
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v5
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v6
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v7
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v8
- [POP-400] Used? Unable to locate resource reference
bcdc/sh.helm.release.v1.bcdc.v9
- [POP-400] Used? Unable to locate resource reference
bcdc/showcase-api-keys
- [POP-400] Used? Unable to locate resource reference
botkube/sh.helm.release.v1.botkube.v1
- [POP-400] Used? Unable to locate resource reference
gitlab/garage-configure-script
- [POP-400] Used? Unable to locate resource reference
gitlab/garage-trivy-s3
- [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-tls
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-minio-secret
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-minio-tls
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-registry-httpsecret
- [POP-400] Used? Unable to locate resource reference
gitlab/gitlab-registry-secret
- [POP-401] Key "registry-auth.crt" used? Unable to locate key reference
gitlab/gitlab-wildcard-tls-chain
- [POP-400] Used? Unable to locate resource reference
gitlab/registry
- [POP-400] Used? Unable to locate resource reference
gitlab/runner-jwtyuxktq-project-463-concurrent-0-gmz4x2cy
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.garage.v1
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v47
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v48
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v49
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v50
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v51
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v52
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v53
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v54
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v55
- [POP-400] Used? Unable to locate resource reference
gitlab/sh.helm.release.v1.gitlab.v56
- [POP-400] Used? Unable to locate resource reference
kube-system/cilium-ca
- [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.local-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
n8n/sh.helm.release.v1.n8n.v3
- [POP-400] Used? Unable to locate resource reference
n8n/sh.helm.release.v1.n8n.v4
- [POP-400] Used? Unable to locate resource reference
n8n/sh.helm.release.v1.n8n.v5
- [POP-400] Used? Unable to locate resource reference
n8n/sh.helm.release.v1.n8n.v6
- [POP-400] Used? Unable to locate resource reference
n8n/sh.helm.release.v1.n8n.v7
- [POP-400] Used? Unable to locate resource reference
n8n/sh.helm.release.v1.n8n.v8
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v16
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v17
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v18
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v19
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v20
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v21
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v22
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v23
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v24
- [POP-400] Used? Unable to locate resource reference
outils/sh.helm.release.v1.outils.v25
- [POP-400] Used? Unable to locate resource reference
outils/wikijs-db-cluster-ca
- [POP-400] Used? Unable to locate resource reference
outils/wikijs-db-cluster-replication
- [POP-400] Used? Unable to locate resource reference
outils/wikijs-db-cluster-server
- [POP-400] Used? Unable to locate resource reference
outils/wikijs-db-credentials
- [POP-401] Key "username" used? Unable to locate key reference
outils/zammad-tls
- [POP-400] Used? Unable to locate resource reference
pilotage/pilotage-db-ca
- [POP-400] Used? Unable to locate resource reference
pilotage/pilotage-db-replication
- [POP-400] Used? Unable to locate resource reference
pilotage/pilotage-db-server
- [POP-400] Used? Unable to locate resource reference
pilotage/registry
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v15
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v16
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v17
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v18
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v19
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v20
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v21
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v22
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v23
- [POP-400] Used? Unable to locate resource reference
pilotage/sh.helm.release.v1.pilotage.v24
- [POP-400] Used? Unable to locate resource reference
streamlit/credentials
- [POP-400] Used? Unable to locate resource reference
streamlit/registry
- [POP-400] Used? Unable to locate resource reference
streamlit/sh.helm.release.v1.streamlit.v1
- [POP-400] Used? Unable to locate resource reference
streamlit/streamlit.local-tls-fbwkl
- [POP-400] Used? Unable to locate resource reference
trombinoscope/sh.helm.release.v1.trombinoscope.v1
- [POP-400] Used? Unable to locate resource reference
trombinoscope/sh.helm.release.v1.trombinoscope.v2
- [POP-400] Used? Unable to locate resource reference
trombinoscope/sh.helm.release.v1.trombinoscope.v3
- [POP-400] Used? Unable to locate resource reference
trombinoscope/sh.helm.release.v1.trombinoscope.v4
- [POP-400] Used? Unable to locate resource reference
trombinoscope/sh.helm.release.v1.trombinoscope.v5
- [POP-400] Used? Unable to locate resource reference
trombinoscope/sh.helm.release.v1.trombinoscope.v6
- [POP-400] Used? Unable to locate resource reference
trombinoscope/sh.helm.release.v1.trombinoscope.v7
- [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/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.cert-manager.v2
- [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.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.external-secrets.v2
- [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.nginx-ingress-controller.v2
- [POP-400] Used? Unable to locate resource reference
val-system/sh.helm.release.v1.nginx-ingress-controller.v3
- [POP-400] Used? Unable to locate resource reference
val-system/sh.helm.release.v1.nginx-ingress-controller.v4
- [POP-400] Used? Unable to locate resource reference
val-system/sh.helm.release.v1.nginx-ingress-controller.v5
- [POP-400] Used? Unable to locate resource reference
val-system/sh.helm.release.v1.nginx-ingress-controller.v6
- [POP-400] Used? Unable to locate resource reference
val-system/sh.helm.release.v1.nginx-ingress-controller.v7
- [POP-400] Used? Unable to locate resource reference
val-system/sh.helm.release.v1.nginx-ingress-controller.v8
- [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
val-system/sh.helm.release.v1.traefik.v2
- [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/velero-repo-credentials
- [POP-400] Used? Unable to locate resource reference
velero/velero-ui-passphrase
- [POP-400] Used? Unable to locate resource reference
whoz-sync-middleware/sh.helm.release.v1.whoz-sync-middleware.v1
- [POP-400] Used? Unable to locate resource reference
whoz-sync-middleware/sh.helm.release.v1.whoz-sync-middleware.v2
- [POP-400] Used? Unable to locate resource reference
whoz-sync-middleware/sh.helm.release.v1.whoz-sync-middleware.v3
- [POP-400] Used? Unable to locate resource reference
whoz-sync-middleware/sh.helm.release.v1.whoz-sync-middleware.v4
- [POP-400] Used? Unable to locate resource reference
whoz-sync-middleware/sh.helm.release.v1.whoz-sync-middleware.v5
- [POP-400] Used? Unable to locate resource reference
whoz-sync-middleware/sh.helm.release.v1.whoz-sync-middleware.v6
- [POP-400] Used? Unable to locate resource reference
whoz-sync-middleware/sh.helm.release.v1.whoz-sync-middleware.v7
- [POP-400] Used? Unable to locate resource reference
whoz-sync-middleware/sh.helm.release.v1.whoz-sync-middleware.v8
- [POP-400] Used? Unable to locate resource reference

SERVICES (64 SCANNED)

5 56 1 2 4%

bcdc/bcdc-back
- [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
bcdc/bcdc-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
bcdc/bcdc-db-cluster-ro
- [POP-1100] No pods match service selector
- [POP-1110] Match EP has no subsets
bcdc/bcdc-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
bcdc/bcdc-front
- [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
bcdc/bcdc-phoenix
- [POP-1102] Use of target port #6006 for service port TCP::443. Prefer named port
- [POP-1109] Single endpoint is associated with this service
bcdc/bcdc-redis-headless
- [POP-1109] Single endpoint is associated with this service
bcdc/bcdc-redis-master
- [POP-1109] Single endpoint is associated with this service
bcdc/bcdc-superset
- [POP-1109] Single endpoint is associated with this service
botkube/botkube
- [POP-1101] Skip ports check. No explicit ports detected on pod botkube/botkube-9d98ddc6f-27spb
- [POP-1109] Single endpoint is associated with this service
gitlab/garage
- [POP-1109] Single endpoint is associated with this service
gitlab/garage-headless
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-gitaly
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-gitlab-exporter
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-gitlab-pages
- [POP-1106] No target ports match service port TCP:http-gitlab-pages-proxy:8090
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-gitlab-pages-metrics
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-gitlab-shell
- [POP-1102] Use of target port #2222 for service port TCP:ssh:22. Prefer named port
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-postgresql
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-postgresql-hl
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-postgresql-metrics
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-redis-headless
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-redis-master
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-redis-metrics
- [POP-1109] Single endpoint is associated with this service
gitlab/gitlab-webservice-default
- [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
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
outils/glpi
- [POP-1109] Single endpoint is associated with this service
outils/glpi-mysql
- [POP-1102] Use of target port #3306 for service port TCP:mysql:3306. Prefer named port
- [POP-1109] Single endpoint is associated with this service
outils/outils-wiki
- [POP-1109] Single endpoint is associated with this service
outils/wikijs-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
outils/wikijs-db-cluster-ro
- [POP-1100] No pods match service selector
- [POP-1110] Match EP has no subsets
outils/wikijs-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
pilotage/pilotage-db-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
pilotage/pilotage-db-ro
- [POP-1100] No pods match service selector
- [POP-1110] Match EP has no subsets
pilotage/pilotage-db-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
pilotage/pilotage-redis-headless
- [POP-1109] Single endpoint is associated with this service
pilotage/pilotage-redis-master
- [POP-1109] Single endpoint is associated with this service
pilotage/pilotage-superset
- [POP-1109] Single endpoint is associated with this service
streamlit/cm-acme-http-solver-j5s54
- [POP-1102] Use of target port #8089 for service port TCP:http:8089. Prefer named port
- [POP-1109] Single endpoint is associated with this service
- [POP-1104] Do you mean it? Type NodePort detected
streamlit/streamlit
- [POP-1100] No pods match service selector
- [POP-1110] Match EP has no subsets
trombinoscope/trombinoscope
- [POP-1102] Use of target port #5000 for service port TCP:https:443. Prefer named port
- [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
velero/velero
- [POP-1109] Single endpoint is associated with this service
velero/velero-ui
- [POP-1109] Single endpoint is associated with this service
whoz-sync-middleware/redis-explorer-svc
- [POP-1102] Use of target port #8081 for service port TCP::80. Prefer named port
- [POP-1109] Single endpoint is associated with this service
whoz-sync-middleware/whoz-sync-middleware
- [POP-1102] Use of target port #3333 for service port TCP:http:80. Prefer named port
- [POP-1109] Single endpoint is associated with this service
whoz-sync-middleware/whoz-sync-middleware-db-explorer
- [POP-1102] Use of target port #8001 for service port TCP:http-explorer:80. Prefer named port
- [POP-1109] Single endpoint is associated with this service
whoz-sync-middleware/whoz-sync-middleware-redis
- [POP-1102] Use of target port #6379 for service port TCP::6379. Prefer named port
- [POP-1109] Single endpoint is associated with this service

SERVICEACCOUNTS (92 SCANNED)

0 13 1 78 85%

bcdc/bcdc-redis
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
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
pilotage/pilotage-redis
- [POP-303] Do you mean it? ServiceAccount is automounting APIServer credentials
streamlit/streamlit
- [POP-400] Used? Unable to locate resource reference
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 (7 SCANNED)

0 7 0 0 0%

bcdc/bcdc-phoenix
- bcdc-phoenix
bcdc/bcdc-redis-master
- redis
gitlab/garage
- garage
gitlab/gitlab-gitaly
- certificates
- configure
- gitaly
gitlab/gitlab-postgresql
- metrics
- postgresql
gitlab/gitlab-redis-master
- [POP-503] At current load, CPU under allocated. Current:26m vs Requested:10m (260.00%)
- metrics
- redis
pilotage/pilotage-redis-master
- redis