# Page Not Found

The URL `blogs/medium-articles/kubernetes-series-2025/understanding-kubernetes-part-37-container-runtime-interface-cri` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Understanding Kubernetes: Part 37 Container Runtime Interface (CRI)](https://blog.techwithpatil.com/blogs/kubernetes-series-2025/understanding-kubernetes-part-37-container-runtime-interface-cri.md)
- [Understanding Kubernetes: Part 38 Container Storage Interface (CSI)](https://blog.techwithpatil.com/blogs/kubernetes-series-2025/understanding-kubernetes-part-38-container-storage-interface-csi.md)
- [Understanding Kubernetes: Part 36 Container Network Interface (CNI)](https://blog.techwithpatil.com/blogs/kubernetes-series-2025/understanding-kubernetes-part-36-container-network-interface-cni.md)
- [Understanding Kubernetes: Part 24 Taints and Tolerations](https://blog.techwithpatil.com/blogs/kubernetes-series-2025/understanding-kubernetes-part-24-taints-and-tolerations.md)
- [Understanding Kubernetes: Part 14 -ClusterIP Service](https://blog.techwithpatil.com/blogs/kubernetes-series-2025/understanding-kubernetes-part-14-clusterip-service.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://blog.techwithpatil.com/blogs/kubernetes-series-2025/understanding-kubernetes-part-37-container-runtime-interface-cri.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://blog.techwithpatil.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://blog.techwithpatil.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/blogs/kubernetes-series-2025/understanding-kubernetes-part-37-container-runtime-interface-cri.md`).

You may also use `Accept: text/markdown` header for content negotiation.