Re:Show HN: konfd – Manage Kubernetes secrets and configmaps...
by kelseyhightower on Monday December 05, 2016 @04:10PM
(#13109617)
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.
Re:Show HN: konfd – Manage Kubernetes secrets and configmaps...
by fcantournet on Monday December 05, 2016 @04:12PM
(#13109643)
That answers my question.
Thank you for taking the time. :)
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 ?