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
Copy file name to clipboardExpand all lines: docs/src/reference/out.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -638,7 +638,7 @@ _Appears in:_
638
638
| --- | --- | --- | --- |
639
639
|`ready`_boolean_| Ready is true when the provider resource is ready. | false ||
640
640
|`addresses`_MachineAddress array_| Addresses contains the Linode instance associated addresses. |||
641
-
|`cloudinitMetadataSupport`_boolean_| CloudinitMetadataSupport determines whether to use cloud-init or not. | true ||
641
+
|`cloudinitMetadataSupport`_boolean_| CloudinitMetadataSupport determines whether to use cloud-init or not.<br />Deprecated: Stackscript no longer in use, so this field is not used.| true ||
642
642
|`instanceState`_[InstanceStatus](#instancestatus)_| InstanceState is the state of the Linode instance for this machine. |||
643
643
|`failureReason`_string_| FailureReason will be set in the event that there is a terminal problem<br />reconciling the Machine and will contain a succinct value suitable<br />for machine interpretation.<br /><br />This field should not be set for transitive errors that a controller<br />faces that are expected to be fixed automatically over<br />time (like service outages), but instead indicate that something is<br />fundamentally wrong with the Machine's spec or the configuration of<br />the controller, and that manual intervention is required. Examples<br />of terminal errors would be invalid combinations of settings in the<br />spec, values that are unsupported by the controller, or the<br />responsible controller itself being critically misconfigured.<br /><br />Any transient errors that occur during the reconciliation of Machines<br />can be added as events to the Machine object and/or logged in the<br />controller's output. |||
644
644
|`failureMessage`_string_| FailureMessage will be set in the event that there is a terminal problem<br />reconciling the Machine and will contain a more verbose string suitable<br />for logging and human consumption.<br /><br />This field should not be set for transitive errors that a controller<br />faces that are expected to be fixed automatically over<br />time (like service outages), but instead indicate that something is<br />fundamentally wrong with the Machine's spec or the configuration of<br />the controller, and that manual intervention is required. Examples<br />of terminal errors would be invalid combinations of settings in the<br />spec, values that are unsupported by the controller, or the<br />responsible controller itself being critically misconfigured.<br /><br />Any transient errors that occur during the reconciliation of Machines<br />can be added as events to the Machine object and/or logged in the<br />controller's output. |||
Copy file name to clipboardExpand all lines: docs/src/topics/getting-started.md
-6
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,6 @@ Make sure to create the token with at least the following read/write permissions
12
12
- VPCs
13
13
- IPs
14
14
- Object Storage
15
-
- Stackscripts
16
15
- Firewalls
17
16
- clusterctl is [installed](https://cluster-api.sigs.k8s.io/user/quick-start#installation)
18
17
- Cluster API [management cluster](https://cluster-api.sigs.k8s.io/user/quick-start#install-andor-configure-a-kubernetes-cluster) is created
@@ -40,11 +39,6 @@ This project uses [linodego](https://github.com/linode/linodego) for Linode API
40
39
Please refer to it for more details on environment variables used for client configuration.
41
40
```
42
41
43
-
```admonish warning
44
-
For Regions and Images that do not yet support Akamai's cloud-init datasource CAPL will automatically use a stackscript shim
45
-
to provision the node. If you are using a custom image ensure the [cloud_init](https://www.linode.com/docs/api/images/#image-create) flag is set correctly on it
46
-
```
47
-
48
42
## Setup management cluster
49
43
A clusterAPI management cluster is a kubernetes cluster that is responsible for managing the lifecycle of other child k8s clusters provisioned using Cluster API (CAPI). It serves as a control plane for provisioning, scaling, upgrading and deleting child kubernetes clusters.
0 commit comments