---
title: "Discussion on \"How Kubernetes Scheduler and API Server Trust Each Other: Inside the mTLS Handshake\" | Hashnode"
description: "Discussion on \"How Kubernetes Scheduler and API Server Trust Each Other: Inside the mTLS Handshake\". 1️⃣ Scheduler–API Server TLS Trust Flow\nThink of it like a secure handshake inside the Kubernetes control plane:\n\nKubernetes CA is created during kubeadm init → stored in /etc/kubernetes/pki/ca.crt (public) and /etc/kubernetes/pki/ca.key (private).\n\n..."
url: "https://hashnode.com/posts/how-kubernetes-scheduler-and-api-server-trust-each-other-inside-the-mtls-handshake/689f25ff3397048a70f9f00f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How Kubernetes Scheduler and API Server Trust Each Other: Inside the mTLS Handshake](https://k8-mtls.hashnode.dev/how-kubernetes-scheduler-and-api-server-trust-each-other-inside-the-mtls-handshake?utm_source=hashnode&utm_medium=feed)

1️⃣ Scheduler–API Server TLS Trust Flow Think of it like a secure handshake inside the Kubernetes control plane: Kubernetes CA is created during kubeadm init → stored in /etc/kubernetes/pki/ca.crt (public) and /etc/kubernetes/pki/ca.key (private). ...

Aug 15, 2025 · 2 min read · k8-mtls.hashnode.dev  
Read the article

## Written by

[Anil kumar](https://hashnode.com/@anil266)

@anil266 · Bengaluru, India

  
[View profile](https://hashnode.com/@anil266)

Devops Engineer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.