3 ms·
While I appreciate the effort, as a Kubernetes user I can't really recommend this tool. As a migration tool, it might save some time building your YAML files,
by lobster_johnson 10y ago
While I appreciate the effort, as a Kubernetes user I can't really recommend this tool.
As a migration tool, it might save some time building your YAML files, but the differences between Compose and Kubernetes are large enough (secret management, for example) that the mapping will be incomplete. But more importantly, the tool itself doesn't lead to a great understanding of Kubernetes itself. In my opinion, the better approach is to learn Kubernetes, then put together your YAML files piece by piece until it all works. Learn by doing.
And it's not useful as a general-purpose tool that abstracts Kubernetes; you need all of the stuff you put in the YAML files. The only way to abstract it is to move one layer up, into a PaaS.
- mst 10y agoSome people learn better by putting everything together from the ground up. Some people learn better by starting with a working example and going from there. I suspect you and I are both in the first group, but for the second group, this seems like a nice way to get started.
- lobster_johnson 10y agoOf course. I personally prefer learning by copying from examples rather than reasoning through reference documentation. But that doesn't mean you need a tool to generate examples. All you need is a small list of "this is how Docker Compose declares X, this is how K8s does it". Compose's surface area is much smaller than K8s, so it doesn't require a lot of examples.