-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add docs about SLI Prober with split control plane
- Loading branch information
Showing
3 changed files
with
40 additions
and
2 deletions.
There are no files selected for viewing
2 changes: 1 addition & 1 deletion
2
...reference/control-plane-architecture.adoc → ...ges/reference/control-plane-pitfalls.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
36 changes: 36 additions & 0 deletions
36
docs/modules/ROOT/pages/reference/sli-prober-architecture.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
= SLI Prober | ||
|
||
The SLI-Prober connects to each instance and will report on its SLI. | ||
For that it needs to reconcile the composites of each instance, to get the connection details. | ||
This way we ensure that the prober probes exactly what the customer gets. | ||
|
||
To avoid issues with potentially checking thousands of instances with a single prober, we deploy the prober to each service cluster. | ||
|
||
In order for the prober to work correctly it needs to reconcile two types of resources: | ||
|
||
* The composites | ||
* `UpgradeJobs` | ||
The composites are reconciled to detect all the actual instances and their connection details. | ||
They are matched against the local service cluster and if the instnace namespace exists, then it will start to probe the given instance. | ||
`UpgradeJobs` on the other hand will track the state of maintenance on the service cluster where the prober and thus the instances run. | ||
|
||
By default, it assumes that it's running in converged mode | ||
To enable the split configuration a `KUBECONFIG` environment variable has to be set on the prober pod. | ||
With that all reconcilers that check the composites will connect to that cluster. | ||
An exception is the reconciler for the `UpgradeJobs` it will connect to the local cluster in either way. | ||
It's possible to override the kubeconfig for the `UpgradeJob` reconciler for debug purposes. | ||
|
||
[mermaid,diagram,png] | ||
.... | ||
architecture-beta | ||
group cp(cloud)[Control Plane] | ||
group sc(cloud)[Service Cluster] | ||
service sli(server)[SLI Prober] in sc | ||
service cr(disk)[Composites] in cp | ||
service uj(disk)[UpgradeJobs] in sc | ||
sli:B --> T:cr | ||
sli:L --> R:uj | ||
.... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters