villebro opened a new pull request, #100: URL: https://github.com/apache/superset-kubernetes-operator/pull/100
## Summary A small pre-0.1.0 cleanup pass. The main change loosens the Renovate update schedule so dependency PRs are no longer confined to a daily window. While preparing for the release I also did a sweep of the codebase and docs and fixed a few things that stuck out: a stale Kubernetes minimum-version claim in the docs and two inconsistent log calls in the e2e suite. ## Details **Renovate** (`renovate.json`) - Removed `"schedule": ["before 7am"]` so Renovate can open and update PRs at any time of day. With no `schedule` key, Renovate defaults to "at any time". The 7-day `minimumReleaseAge` safety delay is intentionally left in place. **Kubernetes version docs** (`docs/getting-started.md`, `README.md`, `docs/user-guide/installation.md`) - `getting-started.md` claimed "v1.28+", which didn't match the tested matrix (1.34/1.35) or the actual feature floor. Corrected to "1.25+ (1.34 officially tested; 1.29+ recommended)". - Added a minimum-version paragraph to the README and installation guide explaining *why* 1.25 is the practical floor: the operator's validation layer is entirely CEL (`x-kubernetes-validations`), which is beta-on-by-default from 1.25 and GA in 1.29 — below 1.25 the CRD installs but the rules are silently ignored, so secret-handling and config-safety checks aren't enforced. HPA also requires `autoscaling/v2` (1.23+). - The new prose is placed outside the `make supported-versions` sentinel blocks so the generator won't overwrite it. The getting-started cross-reference points at the in-docs installation page (not README) so it resolves on the docs site. **e2e logging** (`test/e2e/e2e_test.go`) - Replaced two `fmt.Println` calls in the failure-dump block with `fmt.Fprintf(GinkgoWriter, ...)`, matching the surrounding code so the output is captured by Ginkgo in CI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
