I'm a big fan of the trend of on-premise deployable software standardizing on Kubernetes/Helm as a deployment method. From my perspective as an external freelancers it provides a nice hand-off point to the internal IT/devops team.
Looking forward to trying this out on future projects!
----
I'm wondering how this relates to the glasskube package manager? Obviously you just launched, and maybe you are still in the discover phase, but is the general idea that this is the enterprisey incarnation of the glasskube ideas, and that it will over time gain similar features as the existing glasskube?
Good question, the Glasskube package manager is an alternative to Helm. As Distr is the management / distribution layer the layer connecting the deployment target to the ISV. On the deployment target the software gets installed via docker-compose, Helm or - in future - with the Glasskube Package Manager. The features don't really overlap they complement each other.
I'm a big fan of the trend of on-premise deployable software standardizing on Kubernetes/Helm as a deployment method. From my perspective as an external freelancers it provides a nice hand-off point to the internal IT/devops team.
Looking forward to trying this out on future projects!
----
I'm wondering how this relates to the glasskube package manager? Obviously you just launched, and maybe you are still in the discover phase, but is the general idea that this is the enterprisey incarnation of the glasskube ideas, and that it will over time gain similar features as the existing glasskube?