fix(ingestion): read airbyte-auth-secrets from the Airbyte namespace - #1913
fix(ingestion): read airbyte-auth-secrets from the Airbyte namespace#1913cyberdima wants to merge 2 commits into
Conversation
|
Warning Review limit reached
Next review available in: 54 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
415528e to
6eb4a8d
Compare
6eb4a8d to
95b315c
Compare
ab_get_token read airbyte-auth-secrets from $INSIGHT_NAMESPACE, assuming
Airbyte shares the app namespace. When Airbyte runs in its own namespace
the Secret is absent there, the token fetch fails, and the whole reconcile
run aborts before any connector is created or synced.
- airbyte.sh: new AIRBYTE_NAMESPACE env (defaults to INSIGHT_NAMESPACE, so
single-namespace installs are unaffected); ab_get_token reads the Secret
from it.
- chart: new airbyte.namespace value ("" = .Release.Namespace),
insight.airbyte.namespace helper, AIRBYTE_NAMESPACE rendered on the
reconcile CronWorkflow, and a conditional Role/RoleBinding granting the
reconcile ServiceAccount `get` on the Secret in the Airbyte namespace —
rendered only when it differs from the release namespace.
Refs #1906
Signed-off-by: Dmitry.Saukh <cyberdima@gmail.com>
Signed-off-by: Dmitry Saukh <38005371+cyberdima@users.noreply.github.com>
95b315c to
63a553c
Compare
|
My earlier conflict resolution left unresolved merge markers (broken bash) and duplicated logic that #1935 already merged to main under the same issue (#1885/#1906). Restoring these 5 files to main's content leaves no diff — PR #1913 is superseded, closing it. Signed-off-by: Dmitry Saukh <38005371+cyberdima@users.noreply.github.com>
|
Closing as superseded by #1935, which already merged the same fix (cross-namespace Rebased this branch onto |
Pull request was closed
What
ab_get_tokenreadairbyte-auth-secretsfrom$INSIGHT_NAMESPACE, assuming Airbyte shares the app namespace. When Airbyte runs in its own namespace the Secret is absent there, the token fetch fails, and the whole reconcile run aborts before any connector is created or synced.Change
AIRBYTE_NAMESPACEenv (defaults toINSIGHT_NAMESPACE, so single-namespace installs are unaffected);ab_get_tokenreads the Secret from it.airbyte.namespacevalue (""=.Release.Namespace),insight.airbyte.namespacehelper,AIRBYTE_NAMESPACErendered on the reconcile CronWorkflow, and a conditional Role/RoleBinding granting the reconcile ServiceAccountgeton the Secret in the Airbyte namespace — rendered only when it differs from the release namespace (single-namespace installs render nothing extra).Scope
bash -nclean;helm lintpasses.Refs #1906