There has been so much discussion about the increase of volume in CVEs. I love that it's super apparent from looking at that graph of CVEs by year, there is a noticeable bend in the slope upward in the 2026 plot. It's not just hype, the rate of CVEs is changing faster than prior years.
HashiCorp employee here. Nomad has an open source core which is very capable. There is an Enterprise edition for those that want support and access to several Enterprise features. Does the open source edition address your non commercial criteria?
Hi, we are not intentionally hiding how Waypoint works. We attempted to make the Entrypoint functionality very clear in the documentation with explicit instructions for how you can turn off Entrypoint injection either during build time (it's never put into the artifact) or at deploy time (a configurable on-off switch). If you turn it off you lose features like the URL Service, logs and exec, but the build, deploy and release workflow is still there.
Yes, the plugin architecture is an essential part of Waypoint and we hope to see a large ecosystem of plugins. Rather than focuses exclusively on k8s, Waypoint is designed to center on the build, deploy, release workflow to any platform via plugins. There's a lot of plugins already built-in [1] and the Plugin SDK [2] makes it pretty straight-forward to build new ones.
We do hope to have Waypoint as a HashiCorp Cloud offering in the future. Yet we expect the have the core workflows available in open source. There may someday be features in a paid Enterprise edition, similar the approach we've used well with Vault.
I work at Product Mgmt at HashiCorp. There is a Java Spring example here that uses buildpacks from either Heroku, Cloud Foundry Paketo (VMware Tanzu team that works closely with Spring), and GCP Buildpacks.
i work on pcf at pivotal. i'd love to hear how we can improve. spring boot should work great with "cf push" and when it doesn't we would love to know why and make it better. while pks and k8s are able to run stateless workloads, if pas isn't offering a lot of additional productivity with routing, logging, and multi-tenancy features then we've missed the mark. pivotal-cf-feedback at pivotal dot io will reach the product managers that work on different parts. i saw your note further below about having to login, the "email" prompt instead of username, you had to ask to get the redis tile, and that you find the cf cli confusing compared to other platform clis you are familiar with. we definitely want to know let us know if there are other major issues.
it's a very exciting time for Linux Containers. it's been a fun to watch the evolution from BSD jails to lxc to docker, but the rate of innovation and usefulness is certainly accelerating. it sure seems like rocket's approach will be much less of a black box than docker images/registry, which should make it much more approachable to people trying to understand what linux containers are all about.
AWS Beanstalk for docker does work, but has some weaker points of relative comparison:
* inefficient - 1 docker image per AWS instance, which is expensive to run scaled up compared to running many containers per host
* slow - requires starting a VM which typically takes several minutes
* feature-bare - compared with PaaS platforms like heroku, cloud foundry, openshift, etc. for example, both heroku and cloud foundry have built-in aggregated logging and health management.
there is going to be a large spectrum of ways to run docker images, and you'll be able to choose bare bones to full-service.
here is a 4min video of cloud foundry next generation runtime diego showing spinning up 300 docker images in under a minute, providing load balancing, health management and aggregated logging: http://www.youtube.com/watch?v=e76a50ZgzxM
yes, cloud foundry has been using warden for PaaS isolation between hosted apps for awhile. it was originally authored by redis and cloud foundry contributor pieter noorduis currently working for vmware [1]. the ongoing work has been continued by the cloud foundry team at pivotal.
warden has a c server core [2] wrapping cgroups and other features currently on the lmctfy roadmap like network and file system isolation [3]. the current file system isolation uses either aufs or overlayfs depending on the distro/linux version you are using [4]. the network uses namespaces and additional features.
warden also has early/experimental support for centos in addition to ubuntu, although some of the capabilities are degraded. for example, disk isolation uses a less efficient, but still workable copy file system approach.
the client orchestration of warden is currently written in ruby, but there was also a branch started to move that to go [5] that has not been hardened and moved into master.
recently cloudfoundry started using bosh-lite [2] leveraging warden to do full dev environments using linux containers instead of separate linux hosts on many virtual machines from an IaaS provider, which has dramatically reduced the resources and time required to create, develop and use the full system.