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
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
I read rancher cloud-config document "http://docs.rancher.com/os/cloud-config/" and It just said that I can set the ec2 as datasource but it does not said about what the benefit of it (How to use the mapped metadata).
Is my understanding correct that when I map the ec2 datasource to cloud-init, I could use the data from mapped metadata from environment variable or function or any technicals that give me the data ?
The text was updated successfully, but these errors were encountered:
RancherOS Version: (ros os version)
ros -v = ros version v0.5.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
AWS
Here is my cloud-config
As you see I used $private_ipv4 to assign value to CATTLE_AGENT_IP and It was not work.
The problem is I found this technical from https://forums.rancher.com/t/ec2-metadata-and-cloud-init/2975 that was CoreOS technical long time ago and I'm not sure where are the others technical to use on RancherOS.
I read rancher cloud-config document "http://docs.rancher.com/os/cloud-config/" and It just said that I can set the ec2 as datasource but it does not said about what the benefit of it (How to use the mapped metadata).
I read cloud-init config document "http://cloudinit.readthedocs.io/en/latest/topics/datasources.html" but it didn't help me at all
Is my understanding correct that when I map the ec2 datasource to cloud-init, I could use the data from mapped metadata from environment variable or function or any technicals that give me the data ?
The text was updated successfully, but these errors were encountered: