Using this curl install script. https://kubectl.docs.kubernetes.io/installation/kustomize/binaries/. It's recent busted with this failure.

curl -s "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh"  | bash
Error: kustomize binary with the version 0.9.4 does not exist!

Looks like it's incorrectly finding the lastest kyaml build based on the version number.

Find the broken links:

https://github.com/kubernetes-sigs/cli-experimental/search?q=bases_and_variants

I started reading about kustomize today, so I was following this page (https://kubectl.docs.kubernetes.io/guides/introduction/kustomize/). I don't see anything called quickstart on the left menu so I assumed this was the page to follow and run commands alongside to see it in action. Step 1 says "Make a kustomization file" and it shows a file structure:

~/someApp
├── deployment.yaml
├── kustomization.yaml
└── service.yaml

I grabbed the example NGINX deployment from the k8s docs and made my own deployment file. I skipped service.

Below, it says to run kustomize build ~/someApp, without providing an example kustomization.yaml file, so I assumed it would work without that file or with an empty file of that name and have some default behavior, so I ran kustomize build since I was working in the directory for my example already. No output, but no errors. I also tried kustomize build . in case I had to explicitly specify the directory to build (like the command in the docs). Same thing.

I think the docs should be improved. I can't find anywhere to actually get started. The "Examples" page doesn't seem to be somewhere I can go to get the kuztomization.yaml file I need to complete the quickstart because it's just a page displaying two links (Multibase and Inline Patch) and I don't know what those things mean yet. I don't know which one to click.

https://github.com/kubernetes/enhancements/blob/master/keps/sig-cli/1802-kustomize-components.md is dead

The .gitignore file ignores the vendor directory, so some required files were not checked in.

If I try to build with hugo from the site directory I get:

Error: Error building site: TOCSS: failed to transform "scss/main.scss" (text/x-scss): SCSS processing failed: file "stdin", line 6, col 1: File to import not found or unreadable: ../vendor/bootstrap/scss/bootstrap

https://kubectl.docs.kubernetes.io/guides/config_management/namespaces_names/ has a search field. I type "kustomization.yaml" in it, and nothing is found — the results pop-up is empty.

Trying to solve my problem with variables interpolation, I've accidentally noticed that changes from that PR (merged Oct 22, 2020) is not available in the version after migration.

That particular change can be manually cherry-pick here, but as the migration took place around that merge:

there is a chance that there is a time window when documentation changes were not propagated.

There is a small typo in the example doc:

Example

File Input

# deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: the-deployment
spec:
  replicas: 5
  template:
    containers:
      - name: the-container
        image: registry/conatiner:latest

# kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

namePrefix: overlook-

resources:
- deployment.yaml

Build Output

apiVersion: apps/v1
kind: Deployment
metadata:
  name: alices-the-deployment
spec:
  replicas: 5
  template:
    containers:
    - image: registry/conatiner:latest
      name: the-container

Build output should have name overlook-the-deployment, not alices-the-deployment

although they were marked "experimental" several pages covering app configuration management are no longer available. Is this part of a site overhaul and if so will they become again available in the future?

e.g:

https://kubectl.docs.k8s.io/pages/app_composition_and_deployment/structure_multi_tier_apps.html
https://kubectl.docs.kubernetes.io/pages/app_composition_and_deployment/structure_directories.html

cli.sigs
kubectl.sigs
kustomize.sigs

https://github.com/kubernetes/k8s.io/issues/new?assignees=&labels=wg%2Fk8s-infra%2C+area%2Fdns&template=dns-request.md&title=DNS+REQUEST%3A+%3Cyour-dns-record%3E

Looks like all TravisCI PRs are failing: https://travis-ci.org/github/kubernetes-sigs/cli-experimental/pull_requests

build gopkg.in/alecthomas/gometalinter.v2: cannot load github.com/nicksnyder/go-i18n/i18n: cannot find module providing package github.com/nicksnyder/go-i18n/i18n

gometalinter manifest import path is now invalid with go-i18n repo having a v2 directory: https://github.com/alecthomas/gometalinter/blob/master/vendor/manifest#L21

However gometalinter was deprecated 2019-04-07, so it should probably be replaced in this project.

https://kubectl.docs.kubernetes.io/guides/introduction/kustomize/ says to make a kustomization.yaml but doesn't show an example of what that file could contain.

When looking for options of the yaml file, a reference I land on this page. It's not helpful when looking for a referenceo how to write this yaml file.

Howdy. Two of the four links in this section are 404'd:

https://kubectl.docs.kubernetes.io/guides/extending_kustomize/#examples

"helm chart inflator - A generator that inflates a helm chart." Link 404s.
"bashed config map - Super simple configMap generation from bash." Works.
"sed transformer - Define your unstructured edits using a plugin like this one." Works.
"hashicorp go-getter - Download kustomize layes and build it to generate resources" Link 404s.

I've personally used this link checker successfully, but it's just a suggestion. :) https://github.com/linkchecker/linkchecker Cheers!

https://kubectl.docs.kubernetes.io/blog/

The last entry is in 2019 for kustomize version 3.3.0. But https://kubectl.docs.kubernetes.io/guides/config_management/components/ shows that there is are 3.x releases to at least 3.7, and the current release is 4.0. I haven't been able to find anything via google either.

How am I supposed to evaluate if kustomize will work for me if all the documentation is out of date or broken, and there's not even anything saying what has changed in releases? Is kustomize even something I should be looking at using?

Links at https://kubectl.docs.kubernetes.io/references/kustomize/bases/ are broken

In build output alices-the-deployment should be overlook-the-deployment

cannot do brew install kustomize on Mac Catalina 10.15.7 pro 16inch 2019

` brew install kustomize
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> New Formulae
cadence-workflow dua-cli epr minisat net-tools pcp systemd zinit
crackpkcs enkits kickstart mx organize-tool six xplr zsh-vi-mode
==> Updated Formulae
Updated 1003 formulae.
==> Renamed Formulae
fcct -> butane

==> Downloading https://homebrew.bintray.com/kustomize-4.1.1.catalina.bottle.tar.gz
#=#=#
curl: (22) The requested URL returned error: 404 Not Found
Trying a mirror...
==> Downloading https://ghcr.io/v2/homebrew/core/kustomize-4.1.1.catalina.bottle.tar.gz
==> Downloading from https://github.com/-/v2/packages/container/package/homebrew%2Fcore%2Fkustomize-4.1.1.catalina.bottle.tar.gz
#=#=#
curl: (22) The requested URL returned error: 404
Error: Failed to download resource "kustomize"
Download failed: https://ghcr.io/v2/homebrew/core/kustomize-4.1.1.catalina.bottle.tar.gz`

The example for OTS says "Find and fork an OTS config"

Would it be possible to provide a link to an actual example of an OTS config that could be used as a tutorial as part of the page ?

This is regarding, https://kubectl.docs.kubernetes.io/guides/config_management/offtheshelf/

• How update Kubernetes DNS
• How to update netlify DNS
• How to push the site
• How to build the site locally
• Why kustomize redirects to cli-experimental

The introduction at [1] shows some possible directory structures for using kustomize. It contains the steps "Make a kustomization file" and "Create variants using overlays" but does not explain how to do these. There are no links to other docs indicating what my next steps should be to figure out how to accomplish these tasks.

[1] - https://kubectl.docs.kubernetes.io/guides/introduction/kustomize/#1-make-a-kustomization-file

It would be helpful to provide a link to where the binaries are so that the appropriate curl command could be constructed based on seeing which ones are available and what their download path is

The used namePrefix: overlook- does not actually appear in the build output. Instead the name of the deployment becomes name: alices-the-deployment. There is also a spelling mistake: conatiner instead of container.

The envs block that is supported by configMapGenerator and secretGenerator has undocumented support for OS environment variables, as discussed here:
https://rm3l.org/using-system-envvars-with-kustomize/

Please document the feature.

Click link with arrow to reproduce 404

Naughty link at bottom of this page here:
https://kubectl.docs.kubernetes.io/guides/example/multi_base/

Doc: https://kubectl.docs.kubernetes.io/guides/introduction/resources_controllers/

Title Error：Last paragraph “Configuration and Secrets”, Blockquotes title is "Internal vs External Services", Should be corrected to “Configuration and Secrets”.

The information is abstract. Please provide examples.

Field namespace not documented.

Hi,
it' the first time writing something on GitHub, I'm learning. I hope is the right place.
I was trying to install kustomize on my RPI OS lite, I'm aim to install Metallb. I was thinging that maybe I could use this instructions: https://kubectl.docs.kubernetes.io/installation/kustomize/binaries/

I read the message:
This script doesn’t work for ARM architecture. If you want to install ARM binaries, please go to the release page to find the URL.

Questions:

1. Am I followwing the right instructions? If not where I can find them?
2. If yes where I can find the ARM URL release in the github? I searched for a while and I cannot find it.

As I said I'm begineer in this things so thank you in advance,

This process documented does not work. I have tried on both MacOS and Fedora.

kustomize does not accept the parameter flag as described, and does not work without it.

[mstudd@mstudd renovate]$ XDG_CONFIG_HOME=$DEMO $DEMO/bin/kustomize build --enable_alpha_plugins $MYAPP
Error: unknown flag: --enable_alpha_plugins
[mstudd@mstudd renovate]$ XDG_CONFIG_HOME=$DEMO $DEMO/bin/kustomize build $MYAPP
Error: loading generator plugins: external plugins disabled; unable to load external plugin 'SillyConfigMapGenerator'
[mstudd@mstudd renovate]$ XDG_CONFIG_HOME=$DEMO $DEMO/bin/kustomize version
{Version:kustomize/v4.0.5 GitCommit:9e8e7a7fe99ec9fbf801463e8607928322fc5245 BuildDate:2021-03-08T20:53:03Z GoOs:linux GoArch:amd64}

Link "Kustomize Components KEP." is broken. Github 404 page.

that Build Output The right answer might be metadata.name: overlook-the-deployment rather than metadata.name: alices-the-deployment

The link to strategic merge page is broken. It leads to a 404 error page.

In kustomize documentation I cannot find anywhere an example on how to use kustomize with kubectl's apply -k command.
That is, I don't want to install kustomize standalone and use kubectl instead, but cannot find how to do that, especially because link in https://kustomize.io/ homepage is broken: link in screenshot is pointing to https://kubectl.docs.kubernetes.io/pages/app_management/introduction.html

On this page: https://kubectl.docs.kubernetes.io/references/kustomize/secretgenerator/

The link in "This works like the configMapGenerator." points to the secretGenerator, and not configMapGenerator.

I clicked the "Edit this page" button to submit a fix, but that lead me to a 404 page, so here I am :)

The current link: https://kubectl.docs.kubernetes.io/references/kustomize/secretgenerator/
The expected link: https://kubectl.docs.kubernetes.io/references/kustomize/configmapgenerator/

There is a lot of feature description happening in this glossary that belongs in features' subpages but isn't found there. The glossary should have a one-sentence description of the word or shouldn't exist at all. I favor the latter. The glossary should be replaced with a table of contents that lets you navigate to the page where the feature is described in detail.

Homebrew installs are supported on macOS and Linux. We should maybe separate the homebrew and macports install sections and let people running linux know that homebrew work there too.

This applies to kubectl and kustomize

Not sure if we can or should change anything

Doc: https://kubectl.docs.kubernetes.io/guides/config_management/components/

Broken link: Under For more details regarding this feature you can read the Kustomize Components KEP. -- links to https://github.com/kubernetes/enhancements/blob/master/keps/sig-cli/1802-kustomize-components.md

I tried editing a page by clicking "Edit this page" from the rendered website and it brought me to

https://github.com/kubernetes-sigs/cli-experimental/edit/master/content/en/installation/krew/bash_zsh.md

But the real path is

https://github.com/kubernetes-sigs/cli-experimental/blob/master/site/content/en/installation/krew/bash_zsh.md

I didn't track down where that button is in the template so I wanted to open a quick issue to track it.

Currently sends to cli-docs for some reason...

Should redirect to kustomize.sigs.k8s.io

If you click "edit this page" it 400's

https://cli-experimental.netlify.app/references/architecture/field_merge_semantics/

https://github.com/kubernetes-sigs/cli-experimental/edit/master/content/en/references/architecture/field_merge_semantics.md

On the document :https://kubectl.docs.kubernetes.io/contributing/docs/

Please update the git clone url from
[email protected]:kubernetes-sigs/cli-experimental
to
https://github.com/kubernetes-sigs/cli-experimental.git

As to clone the existing URL users are required public key from github , if we can change to https , no user can face issue to clone the repository .

Referring to this page:

https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/

The page needs to be rewritten in a methodical and sequential way so that the kustomization program can be understood by people other than the authors of the program.

Some people are now using kustomize on YAML that has nothing whatsoever to do with K8s. Which makes the above even harder to comprehend.

Thanks.

Shouldn't there be hyperlinks whenever 'kustomization.yaml' is mentioned in the docs?

I was reading through the documentation here and it says that in order to use a configMapGenerator to specify an environment from a file, you do something like:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
configMapGenerator:
- name: tracing-options
  env: tracing.env

When I tried to do that, I got an error: Error: json: unknown field "env". After doing some googling, I found that the correct configuration was actually:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
configMapGenerator:
- name: tracing-options
  envs:
  - tracing.env

The reference documentation for the Kustomize tool is for Kustomize 3.0, which is not supported in any production version of kubectl to date, and neither the Kustomize reference nor the kubectl reference for kubectl kustomize make any reference to this divergence, what version was included in kubectl, or which versions several directives were added in.