Popeye K8s Sanitizer Report
Scanned
kubernetes
C
75
CLUSTER (1 SCANNED)
0
0
0
1
100%
-
Version
- [POP-406] K8s version OK
CLUSTERROLES (83 SCANNED)
0
0
22
61
100%
-
admin
- [POP-400] Used? Unable to locate resource reference
-
argocd-application-controller
-
argocd-server
-
cattle-admin
-
cluster-admin
-
cluster-member
- [POP-400] Used? Unable to locate resource reference
-
cluster-owner
-
create-ns
-
edit
- [POP-400] Used? Unable to locate resource reference
-
flannel
-
ingress-nginx
-
ingress-nginx-v
-
ingress-nginx-v2
-
ingress-nginx-v3
-
kube-state-metrics
-
kubeadm:get-nodes
-
nfs-client-provisioner-runner
-
p-2v45m-namespaces-edit
-
p-2v45m-namespaces-readonly
- [POP-400] Used? Unable to locate resource reference
-
p-79kvg-namespaces-edit
-
p-79kvg-namespaces-readonly
- [POP-400] Used? Unable to locate resource reference
-
project-member
- [POP-400] Used? Unable to locate resource reference
-
project-member-promoted
-
project-owner
- [POP-400] Used? Unable to locate resource reference
-
project-owner-promoted
-
projects-view
- [POP-400] Used? Unable to locate resource reference
-
proxy-clusterrole-kubeapiserver
-
system:aggregate-to-admin
- [POP-400] Used? Unable to locate resource reference
-
system:aggregate-to-edit
- [POP-400] Used? Unable to locate resource reference
-
system:aggregate-to-view
- [POP-400] Used? Unable to locate resource reference
-
system:auth-delegator
-
system:basic-user
-
system:certificates.k8s.io:certificatesigningrequests:nodeclient
-
system:certificates.k8s.io:certificatesigningrequests:selfnodeclient
-
system:certificates.k8s.io:kube-apiserver-client-approver
- [POP-400] Used? Unable to locate resource reference
-
system:certificates.k8s.io:kube-apiserver-client-kubelet-approver
- [POP-400] Used? Unable to locate resource reference
-
system:certificates.k8s.io:kubelet-serving-approver
- [POP-400] Used? Unable to locate resource reference
-
system:certificates.k8s.io:legacy-unknown-approver
- [POP-400] Used? Unable to locate resource reference
-
system:controller:attachdetach-controller
-
system:controller:certificate-controller
-
system:controller:clusterrole-aggregation-controller
-
system:controller:cronjob-controller
-
system:controller:daemon-set-controller
-
system:controller:deployment-controller
-
system:controller:disruption-controller
-
system:controller:endpoint-controller
-
system:controller:endpointslice-controller
-
system:controller:expand-controller
-
system:controller:generic-garbage-collector
-
system:controller:horizontal-pod-autoscaler
-
system:controller:job-controller
-
system:controller:namespace-controller
-
system:controller:node-controller
-
system:controller:persistent-volume-binder
-
system:controller:pod-garbage-collector
-
system:controller:pv-protection-controller
-
system:controller:pvc-protection-controller
-
system:controller:replicaset-controller
-
system:controller:replication-controller
-
system:controller:resourcequota-controller
-
system:controller:route-controller
-
system:controller:service-account-controller
-
system:controller:service-controller
-
system:controller:statefulset-controller
-
system:controller:ttl-controller
-
system:coredns
-
system:discovery
-
system:heapster
- [POP-400] Used? Unable to locate resource reference
-
system:kube-aggregator
- [POP-400] Used? Unable to locate resource reference
-
system:kube-controller-manager
-
system:kube-dns
-
system:kube-scheduler
-
system:kubelet-api-admin
- [POP-400] Used? Unable to locate resource reference
-
system:metrics-server
-
system:metrics-server-aggregated-reader
- [POP-400] Used? Unable to locate resource reference
-
system:node
-
system:node-bootstrapper
-
system:node-problem-detector
- [POP-400] Used? Unable to locate resource reference
-
system:node-proxier
-
system:persistent-volume-provisioner
- [POP-400] Used? Unable to locate resource reference
-
system:public-info-viewer
-
system:volume-scheduler
-
view
- [POP-400] Used? Unable to locate resource reference
CLUSTERROLEBINDINGS (71 SCANNED)
0
0
0
71
100%
-
argocd-application-controller
-
argocd-server
-
cattle-admin-binding
-
cluster-admin
-
clusterrolebinding-5rbpn
-
clusterrolebinding-9dcmg
-
clusterrolebinding-9s7vr
-
clusterrolebinding-chxpw
-
clusterrolebinding-dwdbv
-
clusterrolebinding-f4qsv
-
clusterrolebinding-fhjpx
-
clusterrolebinding-h9zqg
-
clusterrolebinding-mnvw6
-
clusterrolebinding-rv6db
-
clusterrolebinding-sf4qd
-
clusterrolebinding-tr9b4
-
clusterrolebinding-xvx8s
-
flannel
-
globaladmin-user-mx8z2
-
ingress-nginx
-
ingress-nginx-v
-
ingress-nginx-v2
-
ingress-nginx-v3
-
kube-state-metrics
-
kubeadm:get-nodes
-
kubeadm:kubelet-bootstrap
-
kubeadm:node-autoapprove-bootstrap
-
kubeadm:node-autoapprove-certificate-rotation
-
kubeadm:node-proxier
-
kubeapps-operator
-
metrics-server:system:auth-delegator
-
proxy-role-binding-kubernetes-master
-
run-nfs-client-provisioner
-
system:basic-user
-
system:controller:attachdetach-controller
-
system:controller:certificate-controller
-
system:controller:clusterrole-aggregation-controller
-
system:controller:cronjob-controller
-
system:controller:daemon-set-controller
-
system:controller:deployment-controller
-
system:controller:disruption-controller
-
system:controller:endpoint-controller
-
system:controller:endpointslice-controller
-
system:controller:expand-controller
-
system:controller:generic-garbage-collector
-
system:controller:horizontal-pod-autoscaler
-
system:controller:job-controller
-
system:controller:namespace-controller
-
system:controller:node-controller
-
system:controller:persistent-volume-binder
-
system:controller:pod-garbage-collector
-
system:controller:pv-protection-controller
-
system:controller:pvc-protection-controller
-
system:controller:replicaset-controller
-
system:controller:replication-controller
-
system:controller:resourcequota-controller
-
system:controller:route-controller
-
system:controller:service-account-controller
-
system:controller:service-controller
-
system:controller:statefulset-controller
-
system:controller:ttl-controller
-
system:coredns
-
system:discovery
-
system:kube-controller-manager
-
system:kube-dns
-
system:kube-scheduler
-
system:metrics-server
-
system:node
-
system:node-proxier
-
system:public-info-viewer
-
system:volume-scheduler
CONFIGMAPS (15 SCANNED)
0
0
11
4
100%
-
default/argocd-cm
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-gpg-keys-cm
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-rbac-cm
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-ssh-known-hosts-cm
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-tls-certs-cm
- [POP-400] Used? Unable to locate resource reference
-
default/mysql
-
ingress-nginx/ingress-controller-leader-nginx
- [POP-400] Used? Unable to locate resource reference
-
ingress-nginx/ingress-nginx-controller
- [POP-400] Used? Unable to locate resource reference
-
kube-public/cluster-info
- [POP-400] Used? Unable to locate resource reference
-
kube-system/coredns
-
kube-system/extension-apiserver-authentication
- [POP-400] Used? Unable to locate resource reference
-
kube-system/kube-flannel-cfg
-
kube-system/kube-proxy
-
kube-system/kubeadm-config
- [POP-400] Used? Unable to locate resource reference
-
kube-system/kubelet-config-1.18
- [POP-400] Used? Unable to locate resource reference
DAEMONSETS (8 SCANNED)
0
8
0
0
0%
-
cattle-system/cattle-node-agent
- agent
- [POP-106] No resources requests/limits defined
-
kube-prometheus/node-exporter
- node-exporter
- [POP-107] No resource limits defined
- [POP-108] Unnamed port 9100
-
kube-system/kube-flannel-ds-amd64
- install-cni
- [POP-106] No resources requests/limits defined
-
kube-system/kube-flannel-ds-arm
- install-cni
- [POP-106] No resources requests/limits defined
-
kube-system/kube-flannel-ds-arm64
- install-cni
- [POP-106] No resources requests/limits defined
-
kube-system/kube-flannel-ds-ppc64le
- install-cni
- [POP-106] No resources requests/limits defined
-
kube-system/kube-flannel-ds-s390x
- install-cni
- [POP-106] No resources requests/limits defined
-
kube-system/kube-proxy
- kube-proxy
- [POP-106] No resources requests/limits defined
DEPLOYMENTS (22 SCANNED)
4
14
0
4
18%
-
baobao/baobao-central
- baobao-central
- [POP-101] Image tagged "latest" in use
- [POP-106] No resources requests/limits defined
-
cattle-system/cattle-cluster-agent
- cluster-register
- [POP-106] No resources requests/limits defined
-
cms/hoolai-activity
- hoolai-activity
- [POP-106] No resources requests/limits defined
-
cms/hoolai-actvity-web
- hoolai-actvity-web
- [POP-106] No resources requests/limits defined
-
cms/hoolai-portal
- hoolai-portal
- [POP-106] No resources requests/limits defined
-
cms/hoolai-portal-upload
- hoolai-portal-upload
- [POP-106] No resources requests/limits defined
-
default/alpine
- alpine
- [POP-100] Untagged docker image in use
- [POP-106] No resources requests/limits defined
-
default/alpine-nfs
- alpine-nfs
- [POP-100] Untagged docker image in use
- [POP-106] No resources requests/limits defined
-
default/busybox
- busybox
- [POP-100] Untagged docker image in use
- [POP-106] No resources requests/limits defined
-
default/jenkins
- jenkins
- [POP-107] No resource limits defined
- metrics
- [POP-106] No resources requests/limits defined
-
default/nfs-client-provisioner
- nfs-client-provisioner
- [POP-101] Image tagged "latest" in use
- [POP-106] No resources requests/limits defined
-
default/nginx
- nginx
- [POP-106] No resources requests/limits defined
-
demo/nginx
- nginx
- [POP-106] No resources requests/limits defined
-
demo/yii-demo-debug
-
demo/yii-demo-feature-login
-
demo/yii-demo-test-v3
-
devops/nav-mocaapp
- nav-mocaapp
- [POP-106] No resources requests/limits defined
-
devops/smartping
- smartping
- [POP-101] Image tagged "latest" in use
- [POP-106] No resources requests/limits defined
-
ingress-nginx/ingress-nginx-controller
- [POP-501] Unhealthy 11 desired but have 3 available
- controller
- [POP-107] No resource limits defined
-
kube-system/coredns
-
kube-system/kube-state-metrics
- kube-state-metrics
- [POP-106] No resources requests/limits defined
-
kube-system/metrics-server
- metrics-server
- [POP-106] No resources requests/limits defined
HORIZONTALPODAUTOSCALERS (1 SCANNED)
0
0
0
1
100%
-
ingress-nginx/ingress-nginx-controller
INGRESSES (15 SCANNED)
0
15
0
0
0%
-
baobao/bbcs-global.hulai.com
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
cms/hoolai-activity
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
cms/hoolai-actvity-web
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
cms/hoolai-portal
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
cms/hoolai-portal-upload
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
default/jenkins
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
default/mysql.hulai.com
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
default/nginx
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
default/postgresql.hulai.com
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
demo/demo.hulai.com
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
demo/yii-demo-debug
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
demo/yii-demo-feature-login
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
demo/yii-demo-test-v3
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
devops/nav.mocaapp.cn
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
-
devops/smartping.hulai.com
- [POP-403] Deprecated Ingress API group "extensions/v1beta1". Use "networking.k8s.io/v1beta1" instead
NAMESPACES (11 SCANNED)
0
0
2
9
100%
-
baobao
-
cattle-system
-
cms
-
default
-
demo
-
devops
-
ingress-nginx
-
kube-node-lease
- [POP-400] Used? Unable to locate resource reference
-
kube-prometheus
-
kube-public
- [POP-400] Used? Unable to locate resource reference
-
kube-system
NETWORKPOLICIES (0 SCANNED)
0
0
0
0
100%
NODES (4 SCANNED)
0
0
1
3
100%
-
master-05
- [POP-712] Found only one master node
-
master-06
-
master-07
-
master-08
PERSISTENTVOLUMES (13 SCANNED)
0
0
1
12
100%
-
pv001
- [POP-1000] Available
-
pvc-01b6f864-4d17-4cad-8309-be4ed6925b30
-
pvc-1183b2b5-e8da-4c5f-83fd-55f13f447c34
-
pvc-1d72b2c5-7ca5-44a3-8f73-67736df594cc
-
pvc-3013addf-5363-4d5a-88a0-58efe252436a
-
pvc-5d3f0896-7dca-44bd-9f65-63079d9d9c32
-
pvc-8951e684-9af9-4ef7-af93-e928a54809da
-
pvc-974422d7-b418-48a7-a4de-58ecf750e6be
-
pvc-a32d90b4-cf04-4f05-ab05-4ec8a69724e8
-
pvc-b2d46977-91c8-499e-a1c5-15a9881fd578
-
pvc-d03354a1-34e5-40e9-909d-49b70026ae97
-
pvc-d3f30316-4c1b-4ea6-b5fd-635b12f46472
-
pvc-dc48f7ce-a82b-47a3-9424-ec3f39694003
PERSISTENTVOLUMECLAIMS (12 SCANNED)
0
0
8
4
100%
-
default/apline-nfs
-
default/data-etcd-0
- [POP-400] Used? Unable to locate resource reference
-
default/data-kubeapps-postgresql-primary-0
- [POP-400] Used? Unable to locate resource reference
-
default/data-kubeapps-postgresql-read-0
- [POP-400] Used? Unable to locate resource reference
-
default/data-mysql-0
-
default/data-phabricator-mariadb-0
- [POP-400] Used? Unable to locate resource reference
-
default/data-postgresql-postgresql-0
-
default/data-rabbitmq-0
- [POP-400] Used? Unable to locate resource reference
-
default/data-zookeeper-0
- [POP-400] Used? Unable to locate resource reference
-
default/data-zookeeper-1
- [POP-400] Used? Unable to locate resource reference
-
default/data-zookeeper-2
- [POP-400] Used? Unable to locate resource reference
-
default/jenkins
PODS (60 SCANNED)
15
45
0
0
0%
-
baobao/baobao-central-54f8cd8754-ncwn8
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- baobao-central
- [POP-101] Image tagged "latest" in use
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cattle-system/cattle-cluster-agent-74fd55df94-9vqqv
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- cluster-register
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cattle-system/cattle-node-agent-4cr7d
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- agent
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cattle-system/cattle-node-agent-669sk
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- agent
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cattle-system/cattle-node-agent-f6xlg
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- agent
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cattle-system/cattle-node-agent-mqkg5
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- agent
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cms/hoolai-activity-7ffdcd6fb4-99qkb
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- hoolai-activity
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cms/hoolai-actvity-web-5cc75c544f-rg8tr
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- hoolai-actvity-web
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cms/hoolai-actvity-web-5cc75c544f-shzqs
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- hoolai-actvity-web
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cms/hoolai-portal-657449b854-5gknv
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- hoolai-portal
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cms/hoolai-portal-657449b854-79gcx
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- hoolai-portal
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cms/hoolai-portal-upload-656595f487-rjxpj
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- hoolai-portal-upload
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
cms/hoolai-portal-upload-656595f487-zcvvp
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- hoolai-portal-upload
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
default/alpine-5f6cdf96fb-t5hsk
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- alpine
- [POP-100] Untagged docker image in use
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
default/alpine-nfs-7667d4c9d7-svrs4
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- alpine-nfs
- [POP-100] Untagged docker image in use
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
default/busybox-7b45749458-xjxjv
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- busybox
- [POP-100] Untagged docker image in use
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
default/jenkins-66b6f548bd-2llt9
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- jenkins
- [POP-107] No resource limits defined
- metrics
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
default/mysql-0
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- metrics
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- mysql
- [POP-106] No resources requests/limits defined
-
default/nfs-client-provisioner-669685b4c7-nfmfb
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- nfs-client-provisioner
- [POP-101] Image tagged "latest" in use
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
default/nginx-65f4988446-kjvgc
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "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
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
default/postgresql-postgresql-0
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- metrics
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- postgresql
- [POP-107] No resource limits defined
-
demo/nginx-865d686b4c-8vchx
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "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
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
demo/yii-demo-debug-58847f69f9-kfg7c
- [POP-112] Memory Current/Limit (110Mi/128Mi) reached user 80% threshold (85%)
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- yii-demo
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
demo/yii-demo-feature-login-6b686976f6-hdfkm
- [POP-112] Memory Current/Limit (107Mi/128Mi) reached user 80% threshold (83%)
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- yii-demo
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
demo/yii-demo-test-v3-cb66f88c9-7z95f
- [POP-112] Memory Current/Limit (108Mi/128Mi) reached user 80% threshold (84%)
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- yii-demo
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
devops/nav-mocaapp-668646f4c9-clhjl
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- nav-mocaapp
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
devops/smartping-6f5658788-c7tp7
- [POP-112] Memory Current/Limit (109Mi/128Mi) reached user 80% threshold (85%)
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- smartping
- [POP-101] Image tagged "latest" in use
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-62s5j
- [POP-110] Memory Current/Request (94Mi/90Mi) reached user 80% threshold (104%)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-67h8c
- [POP-207] Pod is in an unhappy phase (Pending)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-94zjw
- [POP-110] Memory Current/Request (102Mi/90Mi) reached user 80% threshold (113%)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-gs54c
- [POP-207] Pod is in an unhappy phase (Pending)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-mlps5
- [POP-207] Pod is in an unhappy phase (Pending)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-rn5ng
- [POP-207] Pod is in an unhappy phase (Pending)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-sgcft
- [POP-110] Memory Current/Request (112Mi/90Mi) reached user 80% threshold (124%)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-v29h5
- [POP-207] Pod is in an unhappy phase (Pending)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-wskd7
- [POP-207] Pod is in an unhappy phase (Pending)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-x5hrw
- [POP-207] Pod is in an unhappy phase (Pending)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7-xtv9x
- [POP-207] Pod is in an unhappy phase (Pending)
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- controller
- [POP-107] No resource limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
kube-prometheus/node-exporter-4kt68
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- node-exporter
- [POP-107] No resource limits defined
- [POP-102] No probes defined
- [POP-108] Unnamed port 9100
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-prometheus/node-exporter-bjpns
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- node-exporter
- [POP-107] No resource limits defined
- [POP-102] No probes defined
- [POP-108] Unnamed port 9100
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-prometheus/node-exporter-f9qwk
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- node-exporter
- [POP-107] No resource limits defined
- [POP-102] No probes defined
- [POP-108] Unnamed port 9100
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-prometheus/node-exporter-z5rnd
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- node-exporter
- [POP-107] No resource limits defined
- [POP-102] No probes defined
- [POP-108] Unnamed port 9100
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-system/coredns-985f7cb96-j6xcr
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- coredns
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-system/coredns-985f7cb96-sf6w2
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- coredns
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-system/etcd-master-05
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- etcd
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness probe 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/kube-apiserver-master-05
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- kube-apiserver
- [POP-107] No resource limits defined
- [POP-105] Liveness probe 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/kube-controller-manager-master-05
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- kube-controller-manager
- [POP-205] Pod was restarted (6) times
- [POP-107] No resource limits defined
- [POP-105] Liveness probe 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/kube-flannel-ds-amd64-5j2xj
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- install-cni
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- kube-flannel
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-system/kube-flannel-ds-amd64-5x6mj
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- install-cni
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- kube-flannel
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-system/kube-flannel-ds-amd64-fx676
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- install-cni
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- kube-flannel
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-system/kube-flannel-ds-amd64-gxrb9
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- install-cni
- [POP-106] No resources requests/limits defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
- kube-flannel
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
-
kube-system/kube-proxy-6b7g9
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- kube-proxy
- [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/kube-proxy-7qp8q
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- kube-proxy
- [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/kube-proxy-j96m6
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- kube-proxy
- [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/kube-proxy-zttf5
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- kube-proxy
- [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/kube-scheduler-master-05
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- kube-scheduler
- [POP-205] Pod was restarted (7) times
- [POP-107] No resource limits defined
- [POP-105] Liveness probe 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/kube-state-metrics-6c477d9b5c-2tv4d
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- kube-state-metrics
- [POP-106] No resources requests/limits defined
- [POP-105] Liveness probe uses a port#, prefer a named port
- [POP-105] Readiness probe uses a port#, prefer a named port
-
kube-system/metrics-server-b5f66b4fc-wp4n5
- [POP-206] No PodDisruptionBudget defined
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- metrics-server
- [POP-106] No resources requests/limits defined
-
kube-system/node-shell-478c7f38-f80d-4f85-9fd2-6ea9966d5f95
- [POP-208] Unmanaged pod detected. Best to use a controller
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- shell
- [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/node-shell-bc713621-a073-46f9-a533-5a9e96efd2ae
- [POP-208] Unmanaged pod detected. Best to use a controller
- [POP-206] No PodDisruptionBudget defined
- [POP-300] Using "default" ServiceAccount
- [POP-301] Connects to API Server? ServiceAccount token is mounted
- [POP-302] Pod could be running as root user. Check SecurityContext/Image
- shell
- [POP-106] No resources requests/limits defined
- [POP-102] No probes defined
- [POP-306] Container could be running as root user. Check SecurityContext/Image
PODDISRUPTIONBUDGETS (0 SCANNED)
0
0
0
0
100%
PODSECURITYPOLICIES (1 SCANNED)
0
0
0
1
100%
-
psp.flannel.unprivileged
REPLICASETS (74 SCANNED)
1
0
0
73
98%
-
baobao/baobao-central-54f8cd8754
-
cattle-system/cattle-cluster-agent-698d769669
-
cattle-system/cattle-cluster-agent-74fd55df94
-
cms/hoolai-activity-5459b67485
-
cms/hoolai-activity-56cf88c64b
-
cms/hoolai-activity-58586dc566
-
cms/hoolai-activity-59db4df8d6
-
cms/hoolai-activity-59f749f596
-
cms/hoolai-activity-5c84fd9c59
-
cms/hoolai-activity-74b4c58fbd
-
cms/hoolai-activity-7c67ddb67f
-
cms/hoolai-activity-7ffdcd6fb4
-
cms/hoolai-activity-847cd756cd
-
cms/hoolai-activity-b8fccc7dd
-
cms/hoolai-actvity-web-5bbdd5dbdb
-
cms/hoolai-actvity-web-5cc75c544f
-
cms/hoolai-actvity-web-5d5ccc889f
-
cms/hoolai-actvity-web-5f4c8cc964
-
cms/hoolai-actvity-web-65755f997
-
cms/hoolai-actvity-web-67b7f888d8
-
cms/hoolai-actvity-web-67b96496c9
-
cms/hoolai-actvity-web-6d4f546b97
-
cms/hoolai-actvity-web-798847b7bd
-
cms/hoolai-actvity-web-7d467c46cf
-
cms/hoolai-actvity-web-86c944d577
-
cms/hoolai-portal-57c7b9d5f7
-
cms/hoolai-portal-59b5cd64d5
-
cms/hoolai-portal-657449b854
-
cms/hoolai-portal-668549c99d
-
cms/hoolai-portal-6cff45c855
-
cms/hoolai-portal-6d9dfbb59b
-
cms/hoolai-portal-755cbf789f
-
cms/hoolai-portal-7657d4575b
-
cms/hoolai-portal-846c44886d
-
cms/hoolai-portal-upload-5976696c55
-
cms/hoolai-portal-upload-656595f487
-
cms/hoolai-portal-upload-67ffb5b9b4
-
cms/hoolai-portal-upload-6cb6b5c5f
-
cms/hoolai-portal-upload-6d77b86c54
-
default/alpine-5f6cdf96fb
-
default/alpine-nfs-7667d4c9d7
-
default/busybox-7b45749458
-
default/jenkins-66b6f548bd
-
default/jenkins-7d7949c589
-
default/jenkins-9b787f4b5
-
default/nfs-client-provisioner-669685b4c7
-
default/nfs-client-provisioner-69f9f5fd64
-
default/nfs-client-provisioner-6d864c9df8
-
default/nfs-client-provisioner-6db99d58c5
-
default/nfs-client-provisioner-7449769997
-
default/nginx-65f4988446
-
default/nginx-665fc4768f
-
demo/nginx-865d686b4c
-
demo/yii-demo-debug-58847f69f9
-
demo/yii-demo-feature-login-6b686976f6
-
demo/yii-demo-test-v3-58bd688494
-
demo/yii-demo-test-v3-5c9c47865
-
demo/yii-demo-test-v3-69744b6c69
-
demo/yii-demo-test-v3-779b4b6554
-
demo/yii-demo-test-v3-7d75f9df69
-
demo/yii-demo-test-v3-cb66f88c9
-
devops/nav-mocaapp-5cb9d959d4
-
devops/nav-mocaapp-668646f4c9
-
devops/nav-mocaapp-754b48c84f
-
devops/nav-mocaapp-76cb9b8977
-
devops/smartping-5459dc7b6c
-
devops/smartping-64cbd9bb75
-
devops/smartping-6f5658788
-
devops/smartping-6f784d77c6
-
devops/smartping-77864d59dc
-
ingress-nginx/ingress-nginx-controller-64b4cc87b7
- [POP-1120] Unhealthy ReplicaSet 11 desired but have 3 ready
-
kube-system/coredns-985f7cb96
-
kube-system/kube-state-metrics-6c477d9b5c
-
kube-system/metrics-server-b5f66b4fc
ROLES (15 SCANNED)
0
0
0
15
100%
-
default/argocd-application-controller
-
default/argocd-dex-server
-
default/argocd-server
-
ingress-nginx/ingress-nginx
-
kube-public/kubeadm:bootstrap-signer-clusterinfo
-
kube-public/system:controller:bootstrap-signer
-
kube-system/extension-apiserver-authentication-reader
-
kube-system/kube-proxy
-
kube-system/kubeadm:kubelet-config-1.18
-
kube-system/kubeadm:nodes-kubeadm-config
-
kube-system/system::leader-locking-kube-controller-manager
-
kube-system/system::leader-locking-kube-scheduler
-
kube-system/system:controller:bootstrap-signer
-
kube-system/system:controller:cloud-provider
-
kube-system/system:controller:token-cleaner
ROLEBINDINGS (60 SCANNED)
0
0
0
60
100%
-
baobao/clusterrolebinding-5qt9d
-
baobao/clusterrolebinding-s4skp
-
baobao/clusterrolebinding-x49nk
-
baobao/clusterrolebinding-zh86t
-
cattle-system/clusterrolebinding-5xzcm
-
cattle-system/clusterrolebinding-8kqs8
-
cattle-system/clusterrolebinding-9tqqg
-
cattle-system/clusterrolebinding-jg2c6
-
cms/clusterrolebinding-6wd5r
-
cms/clusterrolebinding-8sqkk
-
cms/clusterrolebinding-gzktb
-
cms/clusterrolebinding-nxwgs
-
default/argocd-application-controller
-
default/argocd-dex-server
-
default/argocd-server
-
default/clusterrolebinding-92tc8
-
default/clusterrolebinding-d85k2
-
default/clusterrolebinding-hz2qj
-
default/clusterrolebinding-jsqwj
-
demo/clusterrolebinding-js87b
-
demo/clusterrolebinding-m5tw7
-
demo/clusterrolebinding-sw9gf
-
demo/clusterrolebinding-w7tpv
-
devops/clusterrolebinding-2zcxh
-
devops/clusterrolebinding-7bjwx
-
devops/clusterrolebinding-9jqbc
-
devops/clusterrolebinding-hxkc4
-
ingress-nginx/clusterrolebinding-6sqst
-
ingress-nginx/clusterrolebinding-n68gn
-
ingress-nginx/clusterrolebinding-nkbwc
-
ingress-nginx/clusterrolebinding-xk6mk
-
ingress-nginx/ingress-nginx
-
kube-node-lease/clusterrolebinding-j5gm8
-
kube-node-lease/clusterrolebinding-ktrj4
-
kube-node-lease/clusterrolebinding-pk7n8
-
kube-node-lease/clusterrolebinding-qtrfw
-
kube-prometheus/clusterrolebinding-9hdxz
-
kube-prometheus/clusterrolebinding-bbl6w
-
kube-prometheus/clusterrolebinding-hcsxg
-
kube-prometheus/clusterrolebinding-pfsl2
-
kube-public/clusterrolebinding-dzl5b
-
kube-public/clusterrolebinding-gq8r8
-
kube-public/clusterrolebinding-kcqm6
-
kube-public/clusterrolebinding-w64rd
-
kube-public/kubeadm:bootstrap-signer-clusterinfo
-
kube-public/system:controller:bootstrap-signer
-
kube-system/clusterrolebinding-2qk8p
-
kube-system/clusterrolebinding-dbp8v
-
kube-system/clusterrolebinding-dwpkf
-
kube-system/clusterrolebinding-ggwjf
-
kube-system/kube-proxy
-
kube-system/kubeadm:kubelet-config-1.18
-
kube-system/kubeadm:nodes-kubeadm-config
-
kube-system/metrics-server-auth-reader
-
kube-system/system::extension-apiserver-authentication-reader
-
kube-system/system::leader-locking-kube-controller-manager
-
kube-system/system::leader-locking-kube-scheduler
-
kube-system/system:controller:bootstrap-signer
-
kube-system/system:controller:cloud-provider
-
kube-system/system:controller:token-cleaner
SECRETS (143 SCANNED)
0
0
115
28
100%
-
baobao/default-token-zdlwk
-
baobao/hulai-com
-
baobao/mocaapp-cn
- [POP-400] Used? Unable to locate resource reference
-
baobao/mocaapp-register
- [POP-400] Used? Unable to locate resource reference
-
cattle-system/cattle-credentials-7cabea5
-
cattle-system/cattle-credentials-9924e76
- [POP-400] Used? Unable to locate resource reference
-
cattle-system/cattle-token-5bjpp
-
cattle-system/default-token-s9bjc
- [POP-400] Used? Unable to locate resource reference
-
cms/apprepo-huai-repo
- [POP-400] Used? Unable to locate resource reference
-
cms/default-token-pc9g9
- [POP-400] Used? Unable to locate resource reference
-
cms/hoolai-activity-token-9rchl
-
cms/hoolai-actvity-web-token-tb9nf
-
cms/hoolai-portal-token-s8t9p
-
cms/hoolai-portal-upload-token-nbk7g
-
cms/hulai-com
-
cms/mocaapp-cn
- [POP-400] Used? Unable to locate resource reference
-
cms/mocaapp-register
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v28
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v29
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v30
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v31
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v32
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v33
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v34
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v35
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v36
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-activity.v37
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v17
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v18
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v19
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v20
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v21
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v22
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v23
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v24
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v25
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-actvity-web.v26
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal-upload.v1
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal-upload.v2
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal-upload.v3
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal-upload.v4
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal-upload.v5
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal-upload.v6
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v10
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v11
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v12
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v3
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v4
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v5
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v6
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v7
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v8
- [POP-400] Used? Unable to locate resource reference
-
cms/sh.helm.release.v1.hoolai-portal.v9
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-application-controller-token-7lgxh
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-dex-server-token-bfhzp
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-secret
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-server-token-w4xlb
- [POP-400] Used? Unable to locate resource reference
-
default/cms-apprepo-huai-repo
- [POP-400] Used? Unable to locate resource reference
-
default/default-token-99v7n
-
default/hulai-com
- [POP-400] Used? Unable to locate resource reference
-
default/jenkins
-
default/kubeapps-operator-token-94f7x
- [POP-400] Used? Unable to locate resource reference
-
default/mocaapp-cn
- [POP-400] Used? Unable to locate resource reference
-
default/mocaapp-register
- [POP-400] Used? Unable to locate resource reference
-
default/mysql
- [POP-401] Key "mysql-password" used? Unable to locate key reference
-
default/mysql-token-crmmf
-
default/nfs-client-provisioner-token-rtb78
-
default/nfs-client-provisioner-token-vwd8z
- [POP-400] Used? Unable to locate resource reference
-
default/postgresql
- [POP-401] Key "postgresql-postgres-password" used? Unable to locate key reference
-
default/sh.helm.release.v1.jenkins.v1
- [POP-400] Used? Unable to locate resource reference
-
default/sh.helm.release.v1.jenkins.v2
- [POP-400] Used? Unable to locate resource reference
-
default/sh.helm.release.v1.jenkins.v3
- [POP-400] Used? Unable to locate resource reference
-
default/sh.helm.release.v1.jenkins.v4
- [POP-400] Used? Unable to locate resource reference
-
default/sh.helm.release.v1.mysql.v1
- [POP-400] Used? Unable to locate resource reference
-
default/sh.helm.release.v1.postgresql.v1
- [POP-400] Used? Unable to locate resource reference
-
demo/default-token-6xbs8
-
demo/hulai-com
- [POP-400] Used? Unable to locate resource reference
-
demo/mocaapp-cn
- [POP-400] Used? Unable to locate resource reference
-
demo/mocaapp-register
-
demo/sh.helm.release.v1.yii-demo-debug.v1
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-feature-login.v1
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v10
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v11
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v12
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v13
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v4
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v5
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v6
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v7
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v8
- [POP-400] Used? Unable to locate resource reference
-
demo/sh.helm.release.v1.yii-demo-test-v3.v9
- [POP-400] Used? Unable to locate resource reference
-
devops/default-token-8ng58
-
devops/hulai-com
-
devops/mocaapp-cn
-
devops/mocaapp-register
-
ingress-nginx/default-token-2fxss
- [POP-400] Used? Unable to locate resource reference
-
ingress-nginx/ingress-nginx-admission
-
ingress-nginx/ingress-nginx-nginx-admission
- [POP-400] Used? Unable to locate resource reference
-
ingress-nginx/ingress-nginx-token-pvrp6
-
ingress-nginx/sh.helm.release.v1.ingress-nginx.v1
- [POP-400] Used? Unable to locate resource reference
-
kube-node-lease/default-token-6gqnh
- [POP-400] Used? Unable to locate resource reference
-
kube-prometheus/default-token-hgl5w
-
kube-prometheus/hulai-com
- [POP-400] Used? Unable to locate resource reference
-
kube-prometheus/mocaapp-cn
- [POP-400] Used? Unable to locate resource reference
-
kube-prometheus/mocaapp-register
- [POP-400] Used? Unable to locate resource reference
-
kube-public/default-token-7dbrb
- [POP-400] Used? Unable to locate resource reference
-
kube-system/attachdetach-controller-token-8nks9
- [POP-400] Used? Unable to locate resource reference
-
kube-system/bootstrap-signer-token-lx92f
- [POP-400] Used? Unable to locate resource reference
-
kube-system/certificate-controller-token-wbkz7
- [POP-400] Used? Unable to locate resource reference
-
kube-system/clusterrole-aggregation-controller-token-xbrlz
- [POP-400] Used? Unable to locate resource reference
-
kube-system/coredns-token-w5hrc
-
kube-system/cronjob-controller-token-mvw5h
- [POP-400] Used? Unable to locate resource reference
-
kube-system/daemon-set-controller-token-wr46z
- [POP-400] Used? Unable to locate resource reference
-
kube-system/default-token-k2r8d
-
kube-system/deployment-controller-token-pvbpw
- [POP-400] Used? Unable to locate resource reference
-
kube-system/disruption-controller-token-qrrxg
- [POP-400] Used? Unable to locate resource reference
-
kube-system/endpoint-controller-token-4b4wt
- [POP-400] Used? Unable to locate resource reference
-
kube-system/endpointslice-controller-token-jm68r
- [POP-400] Used? Unable to locate resource reference
-
kube-system/expand-controller-token-wcnxb
- [POP-400] Used? Unable to locate resource reference
-
kube-system/flannel-token-mjst5
-
kube-system/generic-garbage-collector-token-6r2zb
- [POP-400] Used? Unable to locate resource reference
-
kube-system/horizontal-pod-autoscaler-token-8fjpb
- [POP-400] Used? Unable to locate resource reference
-
kube-system/job-controller-token-6chs7
- [POP-400] Used? Unable to locate resource reference
-
kube-system/kube-proxy-token-27nsr
-
kube-system/kube-state-metrics-token-zsq2n
-
kube-system/metrics-server-token-4xfq2
-
kube-system/namespace-controller-token-nx2k7
- [POP-400] Used? Unable to locate resource reference
-
kube-system/node-controller-token-b9bc4
- [POP-400] Used? Unable to locate resource reference
-
kube-system/persistent-volume-binder-token-9lcv8
- [POP-400] Used? Unable to locate resource reference
-
kube-system/pod-garbage-collector-token-2tcnf
- [POP-400] Used? Unable to locate resource reference
-
kube-system/pv-protection-controller-token-562nm
- [POP-400] Used? Unable to locate resource reference
-
kube-system/pvc-protection-controller-token-rqg7n
- [POP-400] Used? Unable to locate resource reference
-
kube-system/replicaset-controller-token-xqxtg
- [POP-400] Used? Unable to locate resource reference
-
kube-system/replication-controller-token-fws6h
- [POP-400] Used? Unable to locate resource reference
-
kube-system/resourcequota-controller-token-v5cbc
- [POP-400] Used? Unable to locate resource reference
-
kube-system/service-account-controller-token-pngvz
- [POP-400] Used? Unable to locate resource reference
-
kube-system/service-controller-token-sn4z6
- [POP-400] Used? Unable to locate resource reference
-
kube-system/serving-ca
- [POP-400] Used? Unable to locate resource reference
-
kube-system/serving-cert
- [POP-400] Used? Unable to locate resource reference
-
kube-system/sh.helm.release.v1.metrics-server.v1
- [POP-400] Used? Unable to locate resource reference
-
kube-system/statefulset-controller-token-rbr7d
- [POP-400] Used? Unable to locate resource reference
-
kube-system/token-cleaner-token-nfzqr
- [POP-400] Used? Unable to locate resource reference
-
kube-system/ttl-controller-token-j9fth
- [POP-400] Used? Unable to locate resource reference
SERVICES (35 SCANNED)
0
27
2
6
22%
-
baobao/baobao-central
- [POP-1101] Skip ports check. No explicit ports detected on pod baobao/baobao-central-54f8cd8754-ncwn8
- [POP-1109] Only one associated endpoint
-
baobao/ingress-b1b5caac80465cd30ccabfe125408fe8
- [POP-1101] Skip ports check. No explicit ports detected on pod baobao/baobao-central-54f8cd8754-ncwn8
- [POP-1109] Only one associated endpoint
-
cms/hoolai-activity
- [POP-1109] Only one associated endpoint
-
cms/hoolai-actvity-web
-
cms/hoolai-portal
-
cms/hoolai-portal-upload
-
default/alpine
- [POP-1101] Skip ports check. No explicit ports detected on pod default/alpine-5f6cdf96fb-t5hsk
- [POP-1109] Only one associated endpoint
-
default/alpine-nfs
- [POP-1101] Skip ports check. No explicit ports detected on pod default/alpine-nfs-7667d4c9d7-svrs4
- [POP-1109] Only one associated endpoint
-
default/busybox
- [POP-1101] Skip ports check. No explicit ports detected on pod default/busybox-7b45749458-xjxjv
- [POP-1109] Only one associated endpoint
-
default/ingress-5b4812de2db4e02094da217e31ed3ca3
- [POP-1101] Skip ports check. No explicit ports detected on pod default/nginx-65f4988446-kjvgc
- [POP-1109] Only one associated endpoint
-
default/jenkins
- [POP-1109] Only one associated endpoint
- [POP-1103] Type Loadbalancer detected. Could be expensive
- [POP-1107] LoadBalancer detected but service sets externalTrafficPolicy to "Cluster"
-
default/jenkins-metrics
- [POP-1109] Only one associated endpoint
-
default/kubernetes
-
default/mysql
- [POP-1109] Only one associated endpoint
-
default/mysql-headless
- [POP-1109] Only one associated endpoint
-
default/mysql-metrics
- [POP-1109] Only one associated endpoint
-
default/nginx
- [POP-1101] Skip ports check. No explicit ports detected on pod default/nginx-65f4988446-kjvgc
- [POP-1109] Only one associated endpoint
-
default/postgresql
- [POP-1109] Only one associated endpoint
-
default/postgresql-headless
- [POP-1109] Only one associated endpoint
-
default/postgresql-metrics
- [POP-1109] Only one associated endpoint
-
demo/ingress-dfdda186a9867e7ac4a9731c8a48cac6
- [POP-1101] Skip ports check. No explicit ports detected on pod demo/nginx-865d686b4c-8vchx
- [POP-1109] Only one associated endpoint
-
demo/nginx
- [POP-1101] Skip ports check. No explicit ports detected on pod demo/nginx-865d686b4c-8vchx
- [POP-1109] Only one associated endpoint
-
demo/yii-demo-debug
- [POP-1109] Only one associated endpoint
-
demo/yii-demo-feature-login
- [POP-1109] Only one associated endpoint
-
demo/yii-demo-test-v3
- [POP-1109] Only one associated endpoint
-
devops/ingress-497b4a3102b97a55a31e7e6edf98d42c
- [POP-1101] Skip ports check. No explicit ports detected on pod devops/smartping-6f5658788-c7tp7
- [POP-1109] Only one associated endpoint
-
devops/ingress-9f565ff24478bae1920ac8266b50a027
- [POP-1101] Skip ports check. No explicit ports detected on pod devops/nav-mocaapp-668646f4c9-clhjl
- [POP-1109] Only one associated endpoint
-
devops/nav-mocaapp
- [POP-1101] Skip ports check. No explicit ports detected on pod devops/nav-mocaapp-668646f4c9-clhjl
- [POP-1109] Only one associated endpoint
-
devops/smartping
- [POP-1101] Skip ports check. No explicit ports detected on pod devops/smartping-6f5658788-c7tp7
- [POP-1109] Only one associated endpoint
-
ingress-nginx/ingress-nginx-controller
- [POP-1103] Type Loadbalancer detected. Could be expensive
- [POP-1107] LoadBalancer detected but service sets externalTrafficPolicy to "Cluster"
-
ingress-nginx/ingress-nginx-controller-admission
-
ingress-nginx/ingress-nginx-controller-metrics
-
kube-system/kube-dns
- [POP-1102] Use of target port%!(EXTRA string=53, string=UDP:dns:53)
- [POP-1102] Use of target port%!(EXTRA string=53, string=TCP:dns-tcp:53)
- [POP-1102] Use of target port%!(EXTRA string=9153, string=TCP:metrics:9153)
-
kube-system/kube-state-metrics
- [POP-1102] Use of target port%!(EXTRA string=8080, string=TCP:30080-8080:30080)
- [POP-1109] Only one associated endpoint
- [POP-1104] Do you mean it? Type NodePort detected
-
kube-system/metrics-server
- [POP-1109] Only one associated endpoint
SERVICEACCOUNTS (56 SCANNED)
0
0
8
48
100%
-
baobao/default
-
cattle-system/cattle
-
cattle-system/default
- [POP-400] Used? Unable to locate resource reference
-
cms/default
- [POP-400] Used? Unable to locate resource reference
-
cms/hoolai-activity
-
cms/hoolai-actvity-web
-
cms/hoolai-portal
-
cms/hoolai-portal-upload
-
default/argocd-application-controller
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-dex-server
- [POP-400] Used? Unable to locate resource reference
-
default/argocd-server
- [POP-400] Used? Unable to locate resource reference
-
default/default
-
default/kubeapps-operator
-
default/mysql
-
default/nfs-client-provisioner
-
demo/default
-
devops/default
-
ingress-nginx/default
- [POP-400] Used? Unable to locate resource reference
-
ingress-nginx/ingress-nginx
-
kube-node-lease/default
- [POP-400] Used? Unable to locate resource reference
-
kube-prometheus/default
-
kube-public/default
- [POP-400] Used? Unable to locate resource reference
-
kube-system/attachdetach-controller
-
kube-system/bootstrap-signer
-
kube-system/certificate-controller
-
kube-system/clusterrole-aggregation-controller
-
kube-system/coredns
-
kube-system/cronjob-controller
-
kube-system/daemon-set-controller
-
kube-system/default
-
kube-system/deployment-controller
-
kube-system/disruption-controller
-
kube-system/endpoint-controller
-
kube-system/endpointslice-controller
-
kube-system/expand-controller
-
kube-system/flannel
-
kube-system/generic-garbage-collector
-
kube-system/horizontal-pod-autoscaler
-
kube-system/job-controller
-
kube-system/kube-proxy
-
kube-system/kube-state-metrics
-
kube-system/metrics-server
-
kube-system/namespace-controller
-
kube-system/node-controller
-
kube-system/persistent-volume-binder
-
kube-system/pod-garbage-collector
-
kube-system/pv-protection-controller
-
kube-system/pvc-protection-controller
-
kube-system/replicaset-controller
-
kube-system/replication-controller
-
kube-system/resourcequota-controller
-
kube-system/service-account-controller
-
kube-system/service-controller
-
kube-system/statefulset-controller
-
kube-system/token-cleaner
-
kube-system/ttl-controller
STATEFULSETS (2 SCANNED)
0
2
0
0
0%
-
default/mysql
- metrics
- [POP-106] No resources requests/limits defined
- mysql
- [POP-106] No resources requests/limits defined
-
default/postgresql-postgresql
- metrics
- [POP-106] No resources requests/limits defined
- postgresql
- [POP-107] No resource limits defined