Skip to content

Pin the CRDs-catalog used by kubeconform - #3169

Merged
claytono merged 1 commit into
mainfrom
pin-crds-catalog
Oct 9, 2026
Merged

claytono merged 1 commit into
mainfrom
pin-crds-catalog

Conversation

@claytono

@claytono claytono commented Oct 9, 2026 •

Copy link
Copy Markdown
Owner

kubeconform fetched CRD schemas from datreeio/CRDs-catalog's main branch, so any change upstream applied to every CI run immediately. The catalog's external-secrets.io update (datreeio/CRDs-catalog#988) shipped SecretStore and ClusterSecretStore schemas that kubeconform cannot compile: its converter treats ESO's new field named properties as the schema keyword and writes additionalProperties: false into the field list. kubeconform reports this as "could not find schema", which fails Lint on every branch through kubernetes/external-secrets/clusterstore.yaml.

Pin the catalog to f1e7f6b, the commit just before datreeio/CRDs-catalog#988, in the kubeconform wrapper and in the upgrade playbook's manual check. The upstream report is datreeio/CRDs-catalog#991; return to main once it is fixed, as tracked in #3168.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-09T15:13:24.356217Z 7bdb171 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 28 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 6c45ed43-ee93-4a53-a630-8af09072eda1

📥 Commits

Reviewing files that changed from the base of the PR and between 2db5d25 and 7bdb171.


📒 Files selected for processing (2)
  • docs/kubernetes-upgrade-playbook.md
  • kubernetes/scripts/kubeconform-wrapper


  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

kubeconform fetched CRD schemas from datreeio/CRDs-catalog's main
branch, so any change upstream applied to every CI run immediately. The
catalog's external-secrets.io update (datreeio/CRDs-catalog#988) shipped
SecretStore and ClusterSecretStore schemas that kubeconform cannot
compile: its converter treats ESO's new field named `properties` as the
schema keyword and writes `additionalProperties: false` into the field
list. kubeconform reports this as "could not find schema", which fails
Lint on every branch through
kubernetes/external-secrets/clusterstore.yaml.

Pin the catalog to f1e7f6b, the commit just before
datreeio/CRDs-catalog#988, in the kubeconform wrapper and in the upgrade
playbook's manual check. The upstream report is
datreeio/CRDs-catalog#991; return to main once it is fixed, as tracked
in #3168.
@claytono
claytono merged commit 5e7171b into main Oct 9, 2026
17 checks passed
@claytono
claytono deleted the pin-crds-catalog branch October 9, 2026 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant