Tag: Kubernetes
Problems related to Kubernetes, such as pod failures, API errors, or scheduling issues
| ID | Title | Description | Category | Technology | Tags |
|---|---|---|---|---|---|
| CRE-2025-0032 Low Impact: 2/10 Mitigation: 4/10 | Loki generates excessive logs when memcached service port name is incorrect | Loki instances using memcached for caching may emit excessive warning or error logs when the configured`memcached_client` service port name does not match the actual Kubernetes service port. This does not cause a crash or failure, but it results in noisy logs and ineffective caching behavior. | Observability Problems | loki | LokiMemcachedConfigurationServiceCacheKnown IssueKubernetesPublic |
| CRE-2025-0048 Low Impact: 5/10 Mitigation: 3/10 | Kubelet node not ready due to a DNS hostname resolution failure | A Kubernetes worker node has entered the **NotReady** state. | Kubernetes Problems | kubelet | KubeletKubernetesDNSPublic |
| CRE-2025-0069 Medium Impact: 6/10 Mitigation: 4/10 | Kubernetes fsGroup ignored on NFS volumes | Pods that mount NFS volumes and set `securityContext.fsGroup` still have the directory owned by `root:root`. The kubelet does not chown the share, so non-root containers fail with "Permission denied". | Kubernetes Storage Problems | manifest | KubernetesNFSsecurityContext |
| CRE-2025-0071 High Impact: 9/10 Mitigation: 8/10 | CoreDNS unavailable | CoreDNS deployment is unavailable or has no ready endpoints, indicating an imminent cluster-wide DNS outage. | Kubernetes Problems | kubernetes | KubernetesNetworkingDNSHigh Availability |