Name: coreos-cloudinit
Owner: Rancher
Description: null
Created: 2015-02-19 19:02:22.0
Updated: 2016-07-01 17:36:58.0
Pushed: 2017-02-22 23:01:19.0
Homepage: null
Size: 1966
Language: Go
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
coreos-cloudinit enables a user to customize CoreOS machines by providing either a cloud-config document or an executable script through user-data.
A subset of the official cloud-config spec is implemented by coreos-cloudinit. Additionally, several CoreOS-specific options have been implemented to support interacting with unit files, bootstrapping etcd clusters, and more. All supported cloud-config parameters are documented here.
The following is an example cloud-config document:
ud-config
os:
units:
- name: etcd.service
command: start
s:
name: core
passwd: $1$allJZawX$00S5T756I5PGdQga5qhqv1
e_files:
path: /etc/resolv.conf
content: |
nameserver 192.0.2.2
nameserver 192.0.2.3
coreos-cloudinit supports executing user-data as a script instead of parsing it as a cloud-config document. Make sure the first line of your user-data is a shebang and coreos-cloudinit will attempt to execute it:
in/bash
'Hello, world!'
coreos-cloudinit will replace the following set of tokens in your user-data with system-generated values.
| Token | Description | | ————- | ———– | | $public_ipv4 | Public IPv4 address of machine | | $private_ipv4 | Private IPv4 address of machine |
These values are determined by CoreOS based on the given provider on which your machine is running. Read more about provider-specific functionality in the CoreOS OEM documentation.
For example, submitting the following user-data…
ud-config
os:
etcd:
addr: $public_ipv4:4001
peer-addr: $private_ipv4:7001
…will result in this cloud-config document being executed:
ud-config
os:
etcd:
addr: 203.0.113.29:4001
peer-addr: 192.0.2.13:7001