Despite attempts to educate the market, we still believe the word “serverless” connotes many different things, especially for the 79 percent of organizations that plan to adopt serverless architecture but have not planned to use FaaS in the next 18 months.
Oh boy.
Original source: Add It Up: FaaS ≠ Serverless
A laundry list of new feature and services in the software I market around. There’s a lot of .Net expansion, adding some standard platform services (like a task scheduler), and Morlock stuff like multi-install (would you say “zone”?) OpenStack, and Kubernetes and embedded OS update:
Original source: Pivotal Cloud Foundry 2.3
“The developer shouldn’t have to know how to program NSX, or know what the security isolation boundaries are,” continued Fazzone. “But they should know that their organization has taken steps to unify the networking approach between the containerized applications and the traditional applications running in VMs, and take advantage of that ‘service’ offered by IT to extend the NSX-T support up into their container platform, versus just defaulting to the Layer 2 default that’s available in the open source community — so that their organization can realize that complete connectivity model in a consistent way.”
Original source: VMworld 2018: VMware Wants to Re-Architect Your Containers for NSX – The New Stack
“Harbor is a privately hosted registry, which allows running either on-premises or in any of the major cloud vendors, making it a possibility for organizations that cannot use a public container registry or want to implement a multi-cloud strategy. Harbor started as an internal VMware project and became open source in 2016. Multiple partners, including companies like Pivotal and Rancher, either use Harbor for their container-based environment or work together with Harbor to give the possibility of running the project on their infrastructure. For instance, the Pivotal Container Service includes Harbor as its built-in container registry. For Rancher, Harbor is one of the packages you can deploy to provide a container registry. Moreover, Harbor gives the option to set up multiple instances of these registries on several of these platforms simultaneously and allows replication between them. Through the signing and vulnerability scanning capabilities provided by the project, it turns these into trusted resources.”
Original source: Cloud Native Computing Foundation Accepts Harbor Into CNCF Sandbox
“CNCF has reason to be magnanimous beyond the Chocolate Factory prize money – cloud-oriented enterprise software is all the rage. According to CNCF stats published on Wednesday, production usage of CNCF projects has increased more than 200 per cent on average since December 2017 and evaluation – companies testing said code – has risen 372 per cent…. Among CNCF survey respondents – 2,400 IT-types mostly from the US and Europe – 40 per cent of those from enterprise companies (5,000+ employees) report running Kubernetes in production. Over the whole set of people answering the survey, 58 per cent said they are using Kubernetes in production, with 42 per cent considering it for future deployment.”
Original source: Google sets Kubernetes free with $9m in its pocket for expenses
“Knative is using the market momentum behind Kubernetes to provide an established platform on which to support serverless deployments that can run across different public clouds.”
Original source: What Will Be the Real Impact From Knative?
“Knative is using the market momentum behind Kubernetes to provide an established platform on which to support serverless deployments that can run across different public clouds.”
Original source: What Will Be the Real Impact From Knative?
Networking considered hard: “The amusing thing is that they wanted to connect a GKE On-Prem install running on VSphere for the demo. They could not get a public IP, so they just used MiniKube. Frankly, I think the demo at #GoogleNext2018 was far more amazing connecting MiniKube.”
Original source: GKE On-Prem
“The latter piece can be the tricky one when using containers to develop microservices. How do you link up all the component parts when they may be spread across a cluster of server nodes, and instances of them are continually popping up and later being retired as they are replaced by updated versions? In a service-oriented architecture (SOA), which microservices can be seen as the evolutionary heir to, this kind of task is analogous to that taken care of by an enterprise service bus (ESB). So what is needed is a kind of cloud-native version of an ESB…. This is the job that Istio, a relatively new open source project, aims to fill. It is officially described as a service mesh, because parts of it are distributed across the infrastructure alongside the containers it manages, and it sets out to meet the requirements of service discovery, load balancing, message routing, telemetry, and monitoring – and, of course, security.”
Original source: Istio Aims To Be The Mesh Plumbing For Containerized Microservices
“Kubernetes was created to bring the idea of dynamic, container-centric, managed, scheduled-cluster thinking outside of Google… But what is a container and what does a containerized application mean in this context?”
Original source: Kubernetes for the Kubernewbie – The Journey
