---
title: "Discussion on \"Why valid Kubernetes YAML still breaks in prod, and how to catch it before deploy\" | Hashnode"
description: "Discussion on \"Why valid Kubernetes YAML still breaks in prod, and how to catch it before deploy\". In short. Linting a manifest checks the file, not the cluster it's going to. To catch deploy-time failures you also need the cluster's context (quotas, node sizes, LimitRanges, the Secrets and CRDs it"
url: "https://hashnode.com/posts/why-valid-kubernetes-yaml-still-breaks-in-prod-and-how-to-catch-it-before-deploy/6afc99e7e054e48bafc88d22"
---

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

Discussion

# [Why valid Kubernetes YAML still breaks in prod, and how to catch it before deploy](https://zhukovskyi.hashnode.dev/why-valid-kubernetes-yaml-still-breaks-in-prod-and-how-to-catch-it-before-deploy?utm_source=hashnode&utm_medium=feed)

In short. Linting a manifest checks the file, not the cluster it's going to. To catch deploy-time failures you also need the cluster's context (quotas, node sizes, LimitRanges, the Secrets and CRDs it

3h ago · 5 min read · zhukovskyi.hashnode.dev  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#devops](https://hashnode.com/tag/devops)
-   [#helm](https://hashnode.com/tag/helm)
-   [#opensource](https://hashnode.com/tag/opensource)

## Written by

[Andrii Zhukovskyi](https://hashnode.com/@zhukovskyi)

@zhukovskyi · Barcelona, Spain

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

Platform engineer: Kubernetes, AWS, AI tooling. I write about bugs I hit in production and the open-source tools I build.

Platform engineer working with Kubernetes, AWS and AI tooling. I write about production bugs and the open-source tools I build: jvm-fit, FileForge and Health OS. More at https://zhukovskyi.space

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
