> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Kustomize ApiVersion Kind
> This article discusses the importance of specifying `apiVersion` and `kind` in `kustomization.yaml` for stability and compatibility in Kustomize.
## Kustomize: Specifying `apiVersion` and `kind`
When authoring your `kustomization.yaml`, explicitly declaring the `apiVersion` and `kind` fields is a recommended best practice. Although Kustomize infers sensible defaults when they’re omitted, specifying them ensures compatibility with future Kustomize releases and helps prevent unexpected breaking changes.
### Example `kustomization.yaml`
```yaml theme={null}
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
# List of Kubernetes manifests managed by Kustomize
resources:
- nginx-depl.yaml
- nginx-service.yaml
# Apply these labels to every resource
commonLabels:
company: KodeKloud
```
Defining `apiVersion` and `kind` in your `kustomization.yaml` locks in the schema and ensures that Kustomize processes your resources exactly as intended, even after upgrades.
## Why Declare `apiVersion` and `kind`?
| Benefit | Description |
| ------------- | ---------------------------------------------------------------------------- |
| Stability | Prevents defaults from shifting in newer Kustomize versions |
| Clarity | Makes the file self-descriptive and easier to review |
| Compatibility | Ensures tools and CI/CD pipelines that parse your manifest won’t break later |
## Further Reading
* [Kustomize Official Documentation](https://kubectl.docs.kubernetes.io/references/kustomize/)
* [Understanding `kustomization.yaml`](https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/)