Skip to content

docs: new guide on lb without credentials#1186

Open
lukasmetzner wants to merge 3 commits intomainfrom
docs-robot-lb-without-creds
Open

docs: new guide on lb without credentials#1186
lukasmetzner wants to merge 3 commits intomainfrom
docs-robot-lb-without-creds

Conversation

@lukasmetzner
Copy link
Contributor

No description provided.

@lukasmetzner lukasmetzner requested a review from a team as a code owner March 16, 2026 06:53
@codecov
Copy link

codecov bot commented Mar 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.25%. Comparing base (7878669) to head (a45b29e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1186   +/-   ##
=======================================
  Coverage   69.25%   69.25%           
=======================================
  Files          24       24           
  Lines        2657     2657           
=======================================
  Hits         1840     1840           
  Misses        643      643           
  Partials      174      174           
Flag Coverage Δ
e2e 43.79% <ø> (ø)
unit 65.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

- **Node Lifecycle Controller**: Must be disabled (same flag as above).

This mode is useful when you manage nodes externally (e.g., via Talos or another provisioning tool) and only need the CCM for Load Balancer target management. It avoids exposing account-wide Robot API credentials to the cluster.
> **Running without credentials:** If you manage nodes externally (e.g., via Talos) and only need the Load Balancer IP target integration, you can omit Robot API credentials. The HCCM will derive targets from the Kubernetes Node's `InternalIP` instead. This requires `use-private-ip` and disabling the node controllers. See the [LB-only without credentials guide](../guides/robot/lb-only-without-credentials.md) for setup instructions.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only need the Load Balancer IP target integration

What does integration mean here? Could we use another word?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As an alternative we could say Load Balancer controller, or scraping the IP target part and naming it Load Balancer integration.

Meaning, you only want to use HCCM to manage Load Balancers for you, adding Cloud and Robot nodes as IP targets, but not managing the node lifecycle for example.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Used Load Balancer controller in a45b29e

Co-authored-by: Jonas L. <jooola@users.noreply.github.com>
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