Skip to content

Feat/crossplane tuning knobs guide - #113

Open
GenosseOtt wants to merge 8 commits into
mainfrom
feat/crossplane-tuning-knobs-guide
Open

Feat/crossplane tuning knobs guide#113
GenosseOtt wants to merge 8 commits into
mainfrom
feat/crossplane-tuning-knobs-guide

Conversation

@GenosseOtt

@GenosseOtt GenosseOtt commented Jun 10, 2026

Copy link
Copy Markdown
Contributor
image

Covers the two tunable CLI flags (--max-reconcile-rate, --poll-interval)
with landscape-size guidance, contribution opportunities, and provider
defaults for BTP, CF, and HANA. Structured for both end users and
provider contributors.

Signed-off-by: Johannes Ott <johannes.ott@sap.com>
Signed-off-by: Johannes Ott <johannes.ott@sap.com>
…tion"

This reverts commit f2fde45.

Signed-off-by: Johannes Ott <johannes.ott@sap.com>
Signed-off-by: Johannes Ott <johannes.ott@sap.com>
…g guide"

This reverts commit 12c5df6.

Signed-off-by: Johannes Ott <johannes.ott@sap.com>
Covers the two tunable CLI flags (--max-reconcile-rate, --poll-interval)
with landscape-size guidance, contribution opportunities, and provider
defaults for BTP, CF, and HANA. Structured for both end users and
provider contributors.

Signed-off-by: Johannes Ott <johannes.ott@sap.com>
Signed-off-by: Johannes Ott <johannes.ott@sap.com>
@GenosseOtt
GenosseOtt force-pushed the feat/crossplane-tuning-knobs-guide branch from e4dc843 to 3c0a9f4 Compare June 10, 2026 15:01
@GenosseOtt
GenosseOtt requested a review from a team as a code owner June 10, 2026 15:01
Signed-off-by: Johannes Ott <johannes.ott@sap.com>
@MichaelSp

Copy link
Copy Markdown
Member

same question as https://github.com/SAP/crossplane-provider-docs/pull/72/changes#r3645886705: Do we have good reasons to recommend 1m. To me that is WAY to small. Why not use the kubernetes default: ~10h? I know, Kubernetes has watches for most things, so it can be a bit more re-active. But we've been running Hyperspace with 10k namespaces and 25k resources (total of just one kind) since years on kubernetes defaults just fine.

Reasoning: How likely is external drift? Better safe? Better sorry? Kill the external API with requests?

My take: Lets relax a bit 🌞 In case we miss a drift, we can tighten it. But burning all the CPU cycles "just in case", seems a bit too much FMPOV.

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.

2 participants