mirror of
https://github.com/kubernetes-sigs/kustomize.git
synced 2026-05-18 09:22:03 +00:00
54e8a014bc
It is possible to download secrets from web locations, as the command subfield can execute any terminal command specified. This is a useful feature that should be highlighted.
139 lines
4.5 KiB
YAML
139 lines
4.5 KiB
YAML
# Copyright 2018 The Kubernetes Authors.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
#
|
|
# ----------------------------------------------------
|
|
# Example kustomization.yaml content.
|
|
#
|
|
# This file declares the customization provided by
|
|
# the kustomize program.
|
|
#
|
|
# Since customization is, by definition, _custom_,
|
|
# there are no sensible default values for the fields
|
|
# in this file.
|
|
#
|
|
# The field values used below are merely examples, not
|
|
# to be copied literally. The values won't work if
|
|
# they happen to be references to external files that
|
|
# don't exist.
|
|
#
|
|
# In practice, fields with no value should simply be
|
|
# omitted from kustomize.yaml to reduce the content
|
|
# visible in configuration reviews.
|
|
# ----------------------------------------------------
|
|
|
|
# Adds namespace to all resources.
|
|
namespace: my-namespace
|
|
|
|
# Value of this field is prepended to the
|
|
# names of all resources, e.g. a deployment named
|
|
# "wordpress" becomes "alices-wordpress".
|
|
namePrefix: alices-
|
|
|
|
# Labels to add to all resources and selectors.
|
|
commonLabels:
|
|
someName: someValue
|
|
owner: alice
|
|
app: bingo
|
|
|
|
# Annotations (non-identifying metadata)
|
|
# to add to all resources. Like labels,
|
|
# these are key value pairs.
|
|
commonAnnotations:
|
|
oncallPager: 800-555-1212
|
|
|
|
# Each entry in this list must resolve to an existing
|
|
# resource definition in YAML. These are the resource
|
|
# files that kustomize reads, modifies and emits as a
|
|
# YAML string, with resources separated by document
|
|
# markers ("---").
|
|
resources:
|
|
- some-service.yaml
|
|
- ../some-dir/some-deployment.yaml
|
|
|
|
# Each entry in this list results in the creation of
|
|
# one ConfigMap resource (it's a generator of n maps).
|
|
# The example below creates a ConfigMap with the
|
|
# names and contents of the given files.
|
|
configMapGenerator:
|
|
- name: myJavaServerProps
|
|
files:
|
|
- application.properties
|
|
- more.properties
|
|
|
|
# Each entry in this list results in the creation of
|
|
# one Secret resource (it's a generator of n secrets).
|
|
# A command can do anything to get a secret,
|
|
# e.g. prompt the user directly, start a webserver to
|
|
# initate an oauth dance, etc.
|
|
secretGenerator:
|
|
- name: app-tls
|
|
commands:
|
|
tls.crt: "cat secret/tls.cert"
|
|
tls.key: "cat secret/tls.key"
|
|
type: "kubernetes.io/tls"
|
|
- name: downloaded_secret
|
|
commands:
|
|
username: "curl -s https://path/to/secrets/username.yaml"
|
|
password: "curl -s https://path/to/secrets/password.yaml"
|
|
type: Opaque
|
|
|
|
# Each entry in this list should resolve to a directory
|
|
# containing a kustomization file, else the
|
|
# customization fails.
|
|
#
|
|
# The presence of this field means this file (the file
|
|
# you a reading) is an _overlay_ that further
|
|
# customizes information coming from these _bases_.
|
|
#
|
|
# Typical use case: a dev, staging and production
|
|
# environment that are mostly identical but differing
|
|
# crucial ways (image tags, a few server arguments,
|
|
# etc. that differ from the common base).
|
|
bases:
|
|
- ../../base
|
|
|
|
# Each entry in this list should resolve to
|
|
# a partial or complete resource definition file.
|
|
#
|
|
# The names in these (possibly partial) resource files
|
|
# must match names already loaded via the `resources`
|
|
# field or via `resources` loaded transitively via the
|
|
# `bases` entries. These entries are used to _patch_
|
|
# (modify) the known resources.
|
|
#
|
|
# Small patches that do one thing are best, e.g. modify
|
|
# a memory request/limit, change an env var in a
|
|
# ConfigMap, etc. Small patches are easy to review and
|
|
# easy to mix together in overlays.
|
|
patches:
|
|
- service_port_8888.yaml
|
|
- deployment_increase_replicas.yaml
|
|
- deployment_increase_memory.yaml
|
|
|
|
|
|
# Each entry in this list should be a relative path to
|
|
# a file for custom resource definition(CRD).
|
|
#
|
|
# The presence of this field is to allow kustomize be
|
|
# aware of CRDs and apply proper
|
|
# transformation for any objects in those types.
|
|
#
|
|
# Typical use case: A CRD object refers to a ConfigMap object.
|
|
# In kustomization, the ConfigMap object name may change by adding namePrefix or hashing
|
|
# The name reference for this ConfigMap object in CRD object need to be
|
|
# updated with namePrefix or hashing in the same way.
|
|
crds:
|
|
- crds/typeA.yaml
|
|
- crds/typeB.yaml
|