You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: import fixes/updates from kubeadm bootstrap provider
This adds new conditions, and some small features, cleaning up failure
conditions.
Some changes:
* tests no longer set up owner refs, they should be set by core CAPI
controllers
* set correctly `BootstrapRef`
* TalosConfig controller no longer fails when requeueing is handled by
watches
* more tests for conditions
With conditions enabled there should be no longer required to look into
the controller logs to see why reconciliation failed.
Signed-off-by: Andrey Smirnov <[email protected]>
release: manifests container release-notes release-manifests ## Create the release YAML. The build result will be ouput to the specified local destination.
101
+
98
102
.PHONY: deploy
99
103
deploy: manifests ## Deploy to a cluster. This is for testing purposes only.
Copy file name to clipboardExpand all lines: README.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,14 @@
2
2
3
3
## Intro
4
4
5
-
The Cluster API Bootstrap Provider Talos (CABPT) is a project by [Talos Systems](https://www.talos-systems.com/) that provides a [Cluster API](https://github.com/kubernetes-sigs/cluster-api)(CAPI) bootstrap provider for use in deploying Talos-based Kubernetes nodes across any environment.
5
+
The Cluster API Bootstrap Provider Talos (CABPT) is a project by [Sidero Labs](https://www.siderolabs.com/) that provides a [Cluster API](https://github.com/kubernetes-sigs/cluster-api)(CAPI) bootstrap provider for use in deploying Talos-based Kubernetes nodes across any environment.
6
6
Given some basic info, this provider will generate bootstrap configurations for a given machine and reconcile the necessary custom resources for CAPI to pick up the generated data.
7
7
8
8
## Corequisites
9
9
10
10
There are a few corequisites and assumptions that go into using this project:
-[Cluster API Provider Metal](https://github.com/talos-systems/cluster-api-provider-metal) (optional)
14
13
15
14
## Building and Installing
16
15
@@ -24,14 +23,14 @@ You will need at least the upstream CAPI components and an infrastructure provid
24
23
25
24
## Usage
26
25
27
-
CAPM supports a single API type, a TalosConfig.
26
+
CABPT supports a single API type, a TalosConfig.
28
27
You can create YAML definitions of a TalosConfig and `kubectl apply` them as part of a larger CAPI cluster deployment.
29
28
Below is a bare-minimum example.
30
29
31
30
A basic config:
32
31
33
32
```yaml
34
-
apiVersion: bootstrap.cluster.x-k8s.io/v1alpha2
33
+
apiVersion: bootstrap.cluster.x-k8s.io/v1alpha3
35
34
kind: TalosConfig
36
35
metadata:
37
36
name: talos-0
@@ -48,13 +47,13 @@ When creating a TalosConfig this way, you can then retrieve the talosconfig file
48
47
49
48
If you wish to do something more complex, we allow for the ability to supply an entire Talos config file to the resource.
50
49
This can be done by setting the generateType to `none` and specifying a `data` field.
51
-
This config file can be generated with `osctl config generate` and the edited to supply the various options you may desire.
50
+
This config file can be generated with `talosctl config generate` and the edited to supply the various options you may desire.
52
51
This full config is blindly copied from the `data` section of the spec and presented under `.status.bootstrapData` so that the upstream CAPI controllers can see it and make use.
53
52
54
53
An example of a more complex config:
55
54
56
55
```yaml
57
-
apiVersion: bootstrap.cluster.x-k8s.io/v1alpha2
56
+
apiVersion: bootstrap.cluster.x-k8s.io/v1alpha3
58
57
kind: TalosConfig
59
58
metadata:
60
59
name: talos-0
@@ -72,5 +71,5 @@ spec:
72
71
...
73
72
```
74
73
75
-
Note that specifying the full config above removes the ability for our bootstrap provider to generate a talosconfig for use.
76
-
As such, you should keep track of the talosconfig that's generated when running `osctl config generate`.
74
+
Note that specifying the full config above removes the ability for our bootstrap provider to generate a machine configuration for use.
75
+
As such, you should keep track of the machine configuration that's generated when running `talosctl config generate`.
0 commit comments