-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supplemental update for v1alpha2 #896
Changes from all commits
d082b20
f5de5d4
a5ca9d5
59ab908
6d2c47f
795a8ee
b031db8
1026799
5c4d210
ec7fb9b
d0e1047
5adf1de
ad4d143
13412e6
1f34d42
a3809ee
46f5fe9
74188ec
5783669
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -447,34 +447,6 @@ spec: | |
are additive. The actuator will ensure these tags are present, but | ||
will not remove any other tags that may exist on the instance. | ||
type: object | ||
additionalUserDataFiles: | ||
description: AdditionalUserDataFiles specifies extra files to be passed | ||
to user_data upon creation. | ||
items: | ||
description: Files defines the input for generating write_files in | ||
cloud-init. | ||
properties: | ||
content: | ||
description: Content is the actual content of the file. | ||
type: string | ||
owner: | ||
description: Owner specifies the ownership of the file, e.g. "root:root". | ||
type: string | ||
path: | ||
description: Path specifies the full path on disk where to store | ||
the file. | ||
type: string | ||
permissions: | ||
description: Permissions specifies the permissions to assign to | ||
the file, e.g. "0640". | ||
type: string | ||
required: | ||
- content | ||
- owner | ||
- path | ||
- permissions | ||
type: object | ||
type: array | ||
ami: | ||
description: AMI is the reference to the AMI from which to create the | ||
machine instance. | ||
|
@@ -527,6 +499,10 @@ spec: | |
keyName: | ||
description: KeyName is the name of the SSH key to install on the instance. | ||
type: string | ||
providerID: | ||
description: ProviderID is the unique identifier as specified by the | ||
cloud provider. | ||
type: string | ||
publicIP: | ||
description: 'PublicIP specifies whether the instance should get a public | ||
IP. Precedence for this setting is as follows: 1. This field if set | ||
|
@@ -572,48 +548,64 @@ spec: | |
status: | ||
description: AWSMachineStatus defines the observed state of AWSMachine | ||
properties: | ||
conditions: | ||
description: Conditions is a set of conditions associated with the Machine | ||
to indicate errors or other status | ||
addresses: | ||
description: Addresses contains the AWS instance associated addresses. | ||
items: | ||
description: AWSMachineProviderCondition is a condition in a AWSMachineProviderStatus | ||
description: NodeAddress contains information for the node's address. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. s/NodeAddress/MachineAddresses or InstanceAddresses since we said that these do not need to align with the reported NodeAddresses from the Cloud Provider integration. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we need to fork/copy the NodeAddress struct? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm thinking it wouldn't hurt to create our own with inspiration from the NodeAddress struct, since we could very well end up with different requirements down the line. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll open a PR to CAPI to fork the type, so other providers can use it as well. I can follow-up in a new PR to fixup the CRD/dependency or fix it here, which do you prefer? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. followup is good |
||
properties: | ||
lastProbeTime: | ||
description: LastProbeTime is the last time we probed the condition. | ||
format: date-time | ||
type: string | ||
lastTransitionTime: | ||
description: LastTransitionTime is the last time the condition | ||
transitioned from one status to another. | ||
format: date-time | ||
type: string | ||
message: | ||
description: Message is a human-readable message indicating details | ||
about last transition. | ||
type: string | ||
reason: | ||
description: Reason is a unique, one-word, CamelCase reason for | ||
the condition's last transition. | ||
type: string | ||
status: | ||
description: Status is the status of the condition. | ||
address: | ||
description: The node address. | ||
type: string | ||
type: | ||
description: Type is the type of the condition. | ||
description: Node address type, one of Hostname, ExternalIP or | ||
InternalIP. | ||
type: string | ||
required: | ||
- status | ||
- address | ||
- type | ||
type: object | ||
type: array | ||
errorMessage: | ||
description: "ErrorMessage will be set in the event that there is a | ||
terminal problem reconciling the Machine and will contain a more verbose | ||
string suitable for logging and human consumption. \n This field should | ||
not be set for transitive errors that a controller faces that are | ||
expected to be fixed automatically over time (like service outages), | ||
but instead indicate that something is fundamentally wrong with the | ||
Machine's spec or the configuration of the controller, and that manual | ||
intervention is required. Examples of terminal errors would be invalid | ||
combinations of settings in the spec, values that are unsupported | ||
by the controller, or the responsible controller itself being critically | ||
misconfigured. \n Any transient errors that occur during the reconciliation | ||
of Machines can be added as events to the Machine object and/or logged | ||
in the controller's output." | ||
type: string | ||
errorReason: | ||
description: "ErrorReason will be set in the event that there is a terminal | ||
problem reconciling the Machine and will contain a succinct value | ||
suitable for machine interpretation. \n This field should not be set | ||
for transitive errors that a controller faces that are expected to | ||
be fixed automatically over time (like service outages), but instead | ||
indicate that something is fundamentally wrong with the Machine's | ||
spec or the configuration of the controller, and that manual intervention | ||
is required. Examples of terminal errors would be invalid combinations | ||
of settings in the spec, values that are unsupported by the controller, | ||
or the responsible controller itself being critically misconfigured. | ||
\n Any transient errors that occur during the reconciliation of Machines | ||
can be added as events to the Machine object and/or logged in the | ||
controller's output." | ||
type: string | ||
instanceID: | ||
description: InstanceID is the instance ID of the machine created in | ||
AWS | ||
AWS. | ||
type: string | ||
instanceState: | ||
description: InstanceState is the state of the AWS instance for this | ||
machine | ||
machine. | ||
type: string | ||
ready: | ||
description: Ready is true when the provider resource is ready. | ||
type: boolean | ||
type: object | ||
type: object | ||
versions: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not needed currently, but as we continue to refine for v1alpha2, since we have access to the manager client, we should probably remove the typed clients.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally agree, once the Cluster actuator is also out, we might be able to get rid of them easily