Kubernetes vs. Octopus Deploy

K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.

Incentivized

Octopus Deploy is well suited for our requirements of deploying across multiple environments with one consistent release. We are saving a lot of time by not having to package and move release files around. Our release process is more efficient and consistent with automation. There are some parts that we could probably perform with existing tools such as DevOps and there are one or two features we have to workaround to fit for our setup such as the step templates to install websites. These are minor in our opinion.

Incentivized

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

Incentivized

• Octopus integrates nicely with TeamCity, our build server.
• Octopus uses the same deployment packages across environments and makes it easy to track their progress across those environments.
• Octopus makes it easy to handle configuration across environments which is usually a particularly difficult task.

Incentivized

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

Incentivized

• In the past has been somewhat .net focused but that has been changing in recent times
• Would be great if community licenses for NFP organizations were perpetual - but in saying that I appreciate that Octopus does provide my organization with a community [license]. Not all organisations do
• I can’t think of any other

Incentivized

The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.

Would be a 10 except for the retirement of the free Community Edition.

Incentivized

It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself

Incentivized

Octopus Deploy has greatly helped us to improve our reliability and frequency of our deployments and given us the confidence to deploy much more often, with a direct benefit to customers. Cross-platform support and release to Cloud require more focus on the product side.

Incentivized

Octopus Deploy is a software that runs very effectively, is easy to use, does not require such a high learning curve, provides the necessary tools to carry out the functions it offers, making it a very flexible software, it also allows that can be configured according to the needs of the user and provides integrations with other very advantageous tools since they are carried out in a very favorable way.

Incentivized

Octopus Deploy support has always been there for us, even when using the free tier, we get responsive hands-on help. We haven't needed to use that level of support since the documentation is clearly written, and help is readily available within the interface itself. Using Octopus Deploy is a truly joyful experience.

Incentivized

Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.

Incentivized

There aren't really any competitors in the land of ASP.NET. Deployment is too ad-hoc. Other tools exist that have massive downsides, like Web Deploy. Most aren't even supported anymore. You could argue that containers (Docker) are a competitor, but containers cannot be used for everything and solve a somewhat different problem. Octopus Deploy is even able to help with containers. To us, Octopus Deploy was really the only really polished solution.

Incentivized

Great support from professional services.

Incentivized

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Incentivized

• Allows us to deploy to our fleet quickly and without interruption to service
• Can roll back to previous releases quickly, allowing us to back out of breaking changes in the worst-case scenarios.
• Integration with several targets has allowed us to explore new platforms for our products, such as Docker in AWS ECS.

Incentivized