docs: new guide on lb without credentials#1186
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 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
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
docs/explanation/robot-support.md
Outdated
| - **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. |
There was a problem hiding this comment.
only need the Load Balancer IP target integration
What does integration mean here? Could we use another word?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Used Load Balancer controller in a45b29e
Co-authored-by: Jonas L. <jooola@users.noreply.github.com>
No description provided.