Skip to content

generate operator manifests yaml without kubectl directly - #628

Open
TLINDEN wants to merge 1 commit into
mainfrom
fix-operator-yaml-generation
Open

generate operator manifests yaml without kubectl directly#628
TLINDEN wants to merge 1 commit into
mainfrom
fix-operator-yaml-generation

Conversation

@TLINDEN

@TLINDEN TLINDEN commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

Currently external/svc-postgres-operator.yaml is being generated by downloading the manifests, applying them to a k8s cluster in dry-run mode and then redirecting it to the yaml file.

For one, this leads to last configuration annotation artifacts in the yaml file and it requires the need of a k8s cluster (kind or whatever).

This modification adds a script to do this without k8s. It needs to be a script, because the downloads contain multiple manifests (separated by ---) which cannot easily concatenated into a new Kind: List manifest. So we download the files, split'em up into separate files per manifest, generate the yq load statements (because yq doesn't support wildcards in its load() function) and finally generate the List manifest with each manifest as a list item.

@TLINDEN TLINDEN self-assigned this Aug 18, 2026
@TLINDEN TLINDEN added the enhancement New feature or request label Aug 18, 2026
@TLINDEN
TLINDEN requested a review from l0wl3vel August 18, 2026 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant