3 ms·

Hi kelsey, this is pretty nice ! Is there any way to bribe you into slowing down on the awesome sauce delivery pipeline so people can catch up !? asking for a f

Hi kelsey, this is pretty nice ! Is there any way to bribe you into slowing down on the awesome sauce delivery pipeline so people can catch up !? asking for a friend. If you find the time can you elaborate on why you elected to use ConfigMaps for the templates too instead of building a 3rd party ressource ? This way you wouldn't have to use annotations and the definition might be a little more terse (or not) Is there something about configmaps that make implementation easier ? or provides additional behavior wrt to pod lifecycle or something like that ?

kelseyhightower 10y ago
ConfigMaps offer everything I need for a tool like konfd, and ConfigMaps work with the majority of clusters deployed today. While I could have used a ThirdPartyResource, that would require me to design a custom scheme and write a little more code up front. Also, there are a few issues [1] with ThirdPartyResource objects including the lack of validation and inconsistencies when interacting with ThirdPartyResource objects through the Kubernetes API [2]. That's not to say ThirdPartyResource's should not be used, but it's not a decision take lightly. Now, if konfd were to grow or add more features, then I think a ThirdPartyResource would be the way to go -- mainly because ConfigMaps require the use of "reserved" keys and annotations to configure behavior. [1] https://github.com/kubernetes/kubernetes/issues/22768 https://github.com/kubernetes/kubernetes/issues/22768 [2] https://github.com/kubernetes/kubernetes/issues/29542 https://github.com/kubernetes/kubernetes/issues/29542
- fcantournet 10y ago
  That answers my question. Thank you for taking the time. :)