Use without kubetool / dynamically gernerate certs / keys about puppetlabs-kubernetes HOT 3 CLOSED

@nickperry Thanks for opening the issue. I would imagine that in your case at provisioning time you would have a higher level tool that would orchestrate the creation of the certs. This could be something like Jenkins, Then you could request the ip from IPAM.

from puppetlabs-kubernetes.

Thanks @scotty-c. I've taken care of it for the time being by using wildcard certs and using an fqdn (covered by the wildcard) as the bootstrap ip. It's a good enough approach for what I need at the moment.

from puppetlabs-kubernetes.

We workaround this issue by configuring the node at provisioning time to only apply our "base" role on the masters. Once they are built, we have the hostnames and IP addresses to make the SSL certs with kubetool, update hieradata, then change the role to kubernetes.

~tommy

from puppetlabs-kubernetes.