Skip to content
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

Add machineset.yaml.template to vsphere example #318

Merged
merged 2 commits into from
Jun 11, 2018
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions clusterctl/examples/vsphere/.gitignore
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
machines.yaml
cluster.yaml
provider-components.yaml
machineset.yaml
vsphere_tmp
vsphere_tmp.pub
34 changes: 34 additions & 0 deletions clusterctl/examples/vsphere/machineset.yaml.template
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
apiVersion: "cluster.k8s.io/v1alpha1"
kind: MachineSet
metadata:
name: karangoel-ms-1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove karangoel from here: something like test-machineset-1 or vsphere-nodes or something would make more sense.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

spec:
replicas: 1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we default to 2 so that it's clear how this is different than individual machines?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

selector:
matchLabels:
node-type: worker-node
template:
metadata:
labels:
node-type: worker-node
spec:
providerConfig:
value:
apiVersion: "vsphereproviderconfig/v1alpha1"
kind: "VsphereMachineProviderConfig"
vsphereMachine: "standard-node"
machineVariables:
datacenter: ""
datastore: ""
resource_pool: ""
network: ""
num_cpus: "2"
memory: "2048"
vm_template: "ubuntu-xenial-16.04-cloudimg-20180504"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

disk_label: ""
disk_size: "10"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

virtual_machine_domain: ""
versions:
kubelet: 1.10.1
roles:
- Node