kubernetes-sigs/kustomize
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/kustomize.git synced 2026-06-12 01:14:22 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Migrate site content: overview and installation

Browse Source
This commit is contained in:
Cory Jacobsen
2022-04-24 13:21:56 +00:00
parent 1cf5b00af8
commit 2e036c24c2
7 changed files with 80 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
site/content/en/docs/Overview/_index.md
View File

@@ -2,15 +2,27 @@
title: "Overview"
linkTitle: "Overview"
weight: 1
type: docs
description: >
Introduction to Kustomize.
Introduction to Kustomize
---
{{< alert color="success" title="TL;DR" >}}
- Kustomize helps customizing config files in a template free way.
- Kustomize provides a number of handy methods like generators to make customization easier.
- Kustomize uses patches to introduce environment specific changes on an already existing standard config file without disturbing it.
{{< /alert >}}
Kustomize provides a solution for customizing Kubernetes resource configuration free from templates and DSLs.
Kustomize lets you customize raw, template-free YAML files for multiple purposes, leaving the original YAML untouched and usable as is.
Kustomize lets you customize raw, template-free YAML
files for multiple purposes, leaving the original YAML
untouched and usable as is.
Kustomize targets kubernetes; it understands and can patch kubernetes style API objects. It’s like make, in that what it does is declared in a file, and it’s like sed, in that it emits edited text.
Kustomize targets kubernetes; it understands and can
patch `kubernetes style` API objects. It's like
[make](https://www.gnu.org/software/make), in that what it does is declared in a file,
and it's like [sed](https://www.gnu.org/software/sed), in that it emits edited text.
## Usage
@@ -104,10 +116,3 @@ The YAML can be directly `applied` to a cluster:
kustomize build ~/someApp/overlays/production | kubectl apply -f -
```
## Where should I go next?
Give your users next steps from the Overview. For example:
* [Getting Started](/docs/getting-started/): Get started with $project
* [Examples](/docs/examples/): Check out some example code!