Merge pull request #175 from rancher/fleet-manager-to-controller

Rename Fleet manager as Fleet controller
This commit is contained in:
Klaus Kämpf 2024-08-21 15:00:12 +02:00 committed by GitHub
commit 0cb59e679e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
14 changed files with 2811 additions and 1998 deletions

View File

@ -1,23 +1,23 @@
# Architecture
Fleet has two primary components. The Fleet manager and the cluster agents. These
components work in a two-stage pull model. The Fleet manager will pull from git and the
cluster agents will pull from the Fleet manager.
Fleet has two primary components. The Fleet controller and the cluster agents. These
components work in a two-stage pull model. The Fleet controller will pull from git and the
cluster agents will pull from the Fleet controller.
## Fleet Manager
## Fleet Controller
The Fleet manager is a set of Kubernetes controllers running in any standard Kubernetes
cluster. The only API exposed by the Fleet manager is the Kubernetes API, there is no
The Fleet controller is a set of Kubernetes controllers running in any standard Kubernetes
cluster. The only API exposed by the Fleet controller is the Kubernetes API, there is no
custom API for the fleet controller.
## Cluster Agents
One cluster agent runs in each cluster and is responsible for talking to the Fleet manager.
The only communication from cluster to Fleet manager is by this agent and all communication
goes from the managed cluster to the Fleet manager. The fleet manager does not initiate
One cluster agent runs in each cluster and is responsible for talking to the Fleet controller.
The only communication from cluster to Fleet controller is by this agent and all communication
goes from the managed cluster to the Fleet controller. The fleet manager does not initiate
connections to downstream clusters. This means managed clusters can run in private networks and behind
NATs. The only requirement is the cluster agent needs to be able to communicate with the
Kubernetes API of the cluster running the Fleet manager. The one exception to this is if you use
Kubernetes API of the cluster running the Fleet controller. The one exception to this is if you use
the [manager initiated](./cluster-registration.md#manager-initiated) cluster registration flow. This is not required, but
an optional pattern.
@ -27,7 +27,7 @@ the agent checks in, as it stands right now they will always attempt to connect.
## Security
The Fleet manager dynamically creates service accounts, manages their RBAC and then gives the
The Fleet controller dynamically creates service accounts, manages their RBAC and then gives the
tokens to the downstream clusters. Clusters are registered by optionally expiring cluster registration tokens.
The cluster registration token is used only during the registration process to generate a credential specific
to that cluster. After the cluster credential is established the cluster "forgets" the cluster registration

View File

@ -1,13 +1,13 @@
---
title: ""
sidebar_label: "fleet-manager"
sidebar_label: "fleetcontroller"
---
## fleet-manager
## fleetcontroller
```
fleet-manager [flags]
fleetcontroller [flags]
```
### Options
@ -17,7 +17,7 @@ fleet-manager [flags]
--debug-level int If debugging is enabled, set klog -v=X
--disable-gitops disable gitops components
--disable-metrics disable metrics
-h, --help help for fleet-manager
-h, --help help for fleetcontroller
--kubeconfig string Paths to a kubeconfig. Only required if out-of-cluster.
--namespace string namespace to watch (default "cattle-fleet-system")
--shard-id string only manage resources labeled with a specific shard ID
@ -30,7 +30,7 @@ fleet-manager [flags]
### SEE ALSO
* [fleet-manager agentmanagement](./fleet-manager_agentmanagement) -
* [fleet-manager cleanup](./fleet-manager_cleanup) -
* [fleet-manager gitjob](./fleet-manager_gitjob) -
* [fleetcontroller agentmanagement](./fleetcontroller_agentmanagement) -
* [fleetcontroller cleanup](./fleetcontroller_cleanup) -
* [fleetcontroller gitjob](./fleetcontroller_gitjob) -

View File

@ -1,13 +1,13 @@
---
title: ""
sidebar_label: "fleet-manager agentmanagement"
sidebar_label: "fleetcontroller agentmanagement"
---
## fleet-manager agentmanagement
## fleetcontroller agentmanagement
```
fleet-manager agentmanagement [flags]
fleetcontroller agentmanagement [flags]
```
### Options
@ -28,5 +28,5 @@ fleet-manager agentmanagement [flags]
### SEE ALSO
* [fleet-manager](./fleet-manager) -
* [fleetcontroller](./fleetcontroller) -

View File

@ -1,13 +1,13 @@
---
title: ""
sidebar_label: "fleet-manager cleanup"
sidebar_label: "fleetcontroller cleanup"
---
## fleet-manager cleanup
## fleetcontroller cleanup
```
fleet-manager cleanup [flags]
fleetcontroller cleanup [flags]
```
### Options
@ -27,5 +27,5 @@ fleet-manager cleanup [flags]
### SEE ALSO
* [fleet-manager](./fleet-manager) -
* [fleetcontroller](./fleetcontroller) -

View File

@ -1,13 +1,13 @@
---
title: ""
sidebar_label: "fleet-manager gitjob"
sidebar_label: "fleetcontroller gitjob"
---
## fleet-manager gitjob
## fleetcontroller gitjob
```
fleet-manager gitjob [flags]
fleetcontroller gitjob [flags]
```
### Options
@ -34,5 +34,5 @@ fleet-manager gitjob [flags]
### SEE ALSO
* [fleet-manager](./fleet-manager) -
* [fleetcontroller](./fleetcontroller) -

View File

@ -14,8 +14,8 @@
"write-heading-ids": "docusaurus write-heading-ids"
},
"dependencies": {
"@docusaurus/core": "^2.3.1",
"@docusaurus/preset-classic": "^2.3.1",
"@docusaurus/core": "^3.5.2",
"@docusaurus/preset-classic": "^3.5.2",
"@mdx-js/react": "^1.6.22",
"clsx": "^1.2.1",
"prism-react-renderer": "^1.3.5",
@ -23,7 +23,7 @@
"react-dom": "^17.0.2"
},
"devDependencies": {
"@docusaurus/module-type-aliases": "^2.3.1"
"@docusaurus/module-type-aliases": "^3.5.2"
},
"browserslist": {
"production": [

View File

@ -64,9 +64,10 @@ module.exports = {
{type: 'doc', id: 'cli/fleet-cli/fleet_deploy'},
{type: 'doc', id: 'cli/fleet-cli/fleet_target'},
{type: 'doc', id: 'cli/fleet-cli/fleet_test'},
{type: 'doc', id: 'cli/fleet-controller/fleet-manager'},
{type: 'doc', id: 'cli/fleet-controller/fleet-manager_agentmanagement'},
{type: 'doc', id: 'cli/fleet-controller/fleet-manager_cleanup'},
{type: 'doc', id: 'cli/fleet-controller/fleetcontroller'},
{type: 'doc', id: 'cli/fleet-controller/fleetcontroller_agentmanagement'},
{type: 'doc', id: 'cli/fleet-controller/fleetcontroller_cleanup'},
{type: 'doc', id: 'cli/fleet-controller/fleetcontroller_gitjob'},
],
},
{type:'doc', id:'ref-status-fields'},

View File

@ -1,23 +1,23 @@
# Architecture
Fleet has two primary components. The Fleet manager and the cluster agents. These
components work in a two-stage pull model. The Fleet manager will pull from git and the
cluster agents will pull from the Fleet manager.
Fleet has two primary components. The Fleet controller and the cluster agents. These
components work in a two-stage pull model. The Fleet controller will pull from git and the
cluster agents will pull from the Fleet controller.
## Fleet Manager
## Fleet Controller
The Fleet manager is a set of Kubernetes controllers running in any standard Kubernetes
cluster. The only API exposed by the Fleet manager is the Kubernetes API, there is no
The Fleet controller is a set of Kubernetes controllers running in any standard Kubernetes
cluster. The only API exposed by the Fleet controller is the Kubernetes API, there is no
custom API for the fleet controller.
## Cluster Agents
One cluster agent runs in each cluster and is responsible for talking to the Fleet manager.
The only communication from cluster to Fleet manager is by this agent and all communication
goes from the managed cluster to the Fleet manager. The fleet manager does not initiate
One cluster agent runs in each cluster and is responsible for talking to the Fleet controller.
The only communication from cluster to Fleet controller is by this agent and all communication
goes from the managed cluster to the Fleet controller. The fleet manager does not initiate
connections to downstream clusters. This means managed clusters can run in private networks and behind
NATs. The only requirement is the cluster agent needs to be able to communicate with the
Kubernetes API of the cluster running the Fleet manager. The one exception to this is if you use
Kubernetes API of the cluster running the Fleet controller. The one exception to this is if you use
the [manager initiated](./cluster-registration.md#manager-initiated) cluster registration flow. This is not required, but
an optional pattern.
@ -27,7 +27,7 @@ the agent checks in, as it stands right now they will always attempt to connect.
## Security
The Fleet manager dynamically creates service accounts, manages their RBAC and then gives the
The Fleet controller dynamically creates service accounts, manages their RBAC and then gives the
tokens to the downstream clusters. Clusters are registered by optionally expiring cluster registration tokens.
The cluster registration token is used only during the registration process to generate a credential specific
to that cluster. After the cluster credential is established the cluster "forgets" the cluster registration

View File

@ -1,13 +1,13 @@
---
title: ""
sidebar_label: "fleet-manager"
sidebar_label: "fleetcontroller"
---
## fleet-manager
## fleetcontroller
```
fleet-manager [flags]
fleetcontroller [flags]
```
### Options
@ -17,7 +17,7 @@ fleet-manager [flags]
--debug-level int If debugging is enabled, set klog -v=X
--disable-gitops disable gitops components
--disable-metrics disable metrics
-h, --help help for fleet-manager
-h, --help help for fleetcontroller
--kubeconfig string Paths to a kubeconfig. Only required if out-of-cluster.
--namespace string namespace to watch (default "cattle-fleet-system")
--shard-id string only manage resources labeled with a specific shard ID
@ -30,7 +30,7 @@ fleet-manager [flags]
### SEE ALSO
* [fleet-manager agentmanagement](./fleet-manager_agentmanagement) -
* [fleet-manager cleanup](./fleet-manager_cleanup) -
* [fleet-manager gitjob](./fleet-manager_gitjob) -
* [fleetcontroller agentmanagement](./fleetcontroller_agentmanagement) -
* [fleetcontroller cleanup](./fleetcontroller_cleanup) -
* [fleetcontroller gitjob](./fleetcontroller_gitjob) -

View File

@ -1,13 +1,13 @@
---
title: ""
sidebar_label: "fleet-manager agentmanagement"
sidebar_label: "fleetcontroller agentmanagement"
---
## fleet-manager agentmanagement
## fleetcontroller agentmanagement
```
fleet-manager agentmanagement [flags]
fleetcontroller agentmanagement [flags]
```
### Options
@ -28,5 +28,5 @@ fleet-manager agentmanagement [flags]
### SEE ALSO
* [fleet-manager](./fleet-manager) -
* [fleetcontroller](./fleetcontroller) -

View File

@ -1,13 +1,13 @@
---
title: ""
sidebar_label: "fleet-manager cleanup"
sidebar_label: "fleetcontroller cleanup"
---
## fleet-manager cleanup
## fleetcontroller cleanup
```
fleet-manager cleanup [flags]
fleetcontroller cleanup [flags]
```
### Options
@ -27,5 +27,5 @@ fleet-manager cleanup [flags]
### SEE ALSO
* [fleet-manager](./fleet-manager) -
* [fleetcontroller](./fleetcontroller) -

View File

@ -1,13 +1,13 @@
---
title: ""
sidebar_label: "fleet-manager gitjob"
sidebar_label: "fleetcontroller gitjob"
---
## fleet-manager gitjob
## fleetcontroller gitjob
```
fleet-manager gitjob [flags]
fleetcontroller gitjob [flags]
```
### Options
@ -34,5 +34,5 @@ fleet-manager gitjob [flags]
### SEE ALSO
* [fleet-manager](./fleet-manager) -
* [fleetcontroller](./fleetcontroller) -

View File

@ -114,15 +114,15 @@
},
{
"type": "doc",
"id": "cli/fleet-controller/fleet-manager"
"id": "cli/fleet-controller/fleetcontroller"
},
{
"type": "doc",
"id": "cli/fleet-controller/fleet-manager_agentmanagement"
"id": "cli/fleet-controller/fleetcontroller_agentmanagement"
},
{
"type": "doc",
"id": "cli/fleet-controller/fleet-manager_cleanup"
"id": "cli/fleet-controller/fleetcontroller_cleanup"
}
]
},

4670
yarn.lock

File diff suppressed because it is too large Load Diff