Docs: kustomize does not include an install directory

[howardjones]

Please ensure you do the following when reporting a bug:

• Provide a concise description of what the bug is.
• Provide information about your environment.
• Provide clear steps to reproduce the bug.
• Attach applicable logs. Please do not attach screenshots showing logs unless you are unable to copy and paste the log data.
• Ensure any code / output examples are properly formatted for legibility.

I was planning to install PGO in a local KIND (0.31.0/ k8s 1.35) cluster for some testing, but the getting starting instructions don't align with reality. I've forked the postgres-operator-examples repo (actually, I refreshed my previous fork) and cloned it. The first kustomize command: kubectl apply -k kustomize/install/namespace fails because there is no kustomize/install directory. Checking the source repo, I can see that it doesn't exist there either, so I don't think it's me, but this seems like something that would be noticed quite quickly!

Overview

Add a concise description of what the bug is.

Environment

Please provide the following details:

• Platform: Kubernetes 1.35 on KIND 0.31.0 on Ubuntu 24.04
• Platform Version: 1.35
• PGO Image Tag: I have not got that far!
• Postgres Version: same
• Storage: same

Steps to Reproduce

REPRO

Following instructions at https://access.crunchydata.com/documentation/postgres-operator/v5/quickstart/

git clone --depth 1 https://github.com/howardjones/postgres-operator-examples.git

cd postgres-operator-examples

kubectl apply -k kustomize/install/namespace

error: must build at directory: not a valid directory: evalsymlink failure on 'kustomize/install/namespace' : lstat /home/howardwork/Work/postgres-operator-examples/kustomize/install: no such file or directory

Same thing with cloning https://github.com/CrunchyData/postgres-operator-examples/ directly

EXPECTED

1. Provide the behavior that you expected.

I guess it was supposed to create the namespace for the operator.

ACTUAL

1. Describe what actually happens

Logs

error: must build at directory: not a valid directory: evalsymlink failure on 'kustomize/install/namespace' : lstat /home/howardwork/Work/postgres-operator-examples/kustomize/install: no such file or directory

Additional Information

Please provide any additional information that may be helpful.

[howardjones]

I guess it's something to do with this? (but the README in postgres-operator still says to clone postgres-operator-examples, right now)

CrunchyData/postgres-operator-examples#319

[howardjones]

And kubectl apply -k config/default/ from postgres-operator which appears to be the intended replacement, also fails:

kubectl apply -k default/                   
customresourcedefinition.apiextensions.k8s.io/pgadmins.postgres-operator.crunchydata.com created
customresourcedefinition.apiextensions.k8s.io/pgupgrades.postgres-operator.crunchydata.com created
clusterrole.rbac.authorization.k8s.io/postgres-operator created
clusterrolebinding.rbac.authorization.k8s.io/postgres-operator created
Error from server (Invalid): error when creating "default/": CustomResourceDefinition.apiextensions.k8s.io "postgresclusters.postgres-operator.crunchydata.com" is invalid: metadata.annotations: Too long: may not be more than 262144 bytes
Error from server (NotFound): error when creating "default/": namespaces "postgres-operator" not found
Error from server (NotFound): error when creating "default/": namespaces "postgres-operator" not found

[howardjones]

I noticed that 6.0.0 was released, and there is a 6.0.0 manual with the correct deployment commands. But the README links twice to the old v5 manual and includes a summary of the older (now not working) deployment instructions.

Edit: actually, now it fails with an ImagePullBackOff for the 6.0.1-0 image, but at least the commands exist.

[howardjones]

And the v6 manual still has the wrong steps in places:

https://access.crunchydata.com/documentation/postgres-operator/latest/tutorials/basic-setup