low severityKubernetes scheduler, Pinecone serverless

Pods pending with "node(s) didn't match pod anti-affinity rules". Pinecone queries with high initial latency (300-400ms) labeled as cold.

Root cause

No specific root cause found for combined issue. Kubernetes affinity conflicts occur when no nodes satisfy hard podAntiAffinity/nodeAffinity rules during scheduling. Pinecone serverless warm-up latency is due to cold namespace caching (~300ms first queries), unrelated to Kubernetes pods as it's managed service.

kubernetesschedulingaffinitypineconeserverlesslatencywarm-upcold-start