Kubernetes
Auto Added by WPeMatico
Suse launches version 2.0 of its Cloud Foundry-based Cloud Application Platform
Suse, the well-known German open-source company that went through more corporate owners than anybody can remember until it finally became independent again in 2019, has long been a champion of Cloud Foundry, the open-source platform-as-a-service project. And while you may think of Suse as a Linux distribution, today’s company also offers a number of other services, including a container platform, DevOps tools and the Suse Cloud Application Platform, based on Cloud Foundry. Today, right in time for the bi-annual (and now virtual) Cloud Foundry Summit, the company announced the launch of version 2.0 of this platform.
The promise of the Application Platform, and indeed Cloud Foundry, is that it allows for one-step application deployments and an enterprise-ready platform to host them.
The marquee feature of version 2.0 is that it now includes a new Kubernetes Operator, a standard way of packaging, deploying and managing container-based applications, which makes deploying and managing Cloud Foundry on Kubernetes infrastructure easier.
Suse President of Engineering and Innovation Thomas Di Giacomo also notes that it’s now easier to “install, operate and maintain on Kubernetes platforms anywhere — on premises and in public clouds,” and that it opens up a new path for existing Cloud Foundry users to move to a modern container-based architecture. Indeed, for the last few years, Suse has been crucial to bringing both Kubernetes support to Cloud Foundry and Cloud Foundry to Kubernetes.
Cloud Foundry, it’s worth noting, long used its home-grown container orchestration tool, which the community developed before anybody had even heard of Kubernetes. Over the course of the last few years, though, Kubernetes became the de facto standard for container management, and today, Cloud Foundry supports both its own Diego tool and Kubernetes.
“Suse Cloud Application Platform 2.0 builds on and advances those efforts, incorporating several upstream technologies recently contributed by Suse to the Cloud Foundry Community,” writes Di Giacomo. “These include KubeCF, a containerized version of the Cloud Foundry Application Runtime designed to run on Kubernetes, and Project Quarks, a Kubernetes operator for automating deployment and management of Cloud Foundry on Kubernetes.”
Powered by WPeMatico
Loodse becomes Kubermatic and open-sources Kubernetes automation platform
Loodse, a German Kubernetes automation platform, announced today that it was rebranding as Kubermatic. While it was at it, the company also announced that it was open-sourcing its Kubermatic Kubernetes Platform as open source under the Apache 2.0 License.
Co-founder Sebastian Scheele says that his company’s Kubernetes solution can provision clusters and applications on any cloud, as well as in a data center running, for example, OpenStack or VMware. What’s more, it can do it much faster by automating much of the operations side of running Kubernetes clusters.
“We wanted to really have a cloud native way to run and manage Kubernetes. And so it’s running the Kubernetes master itself, which is completely containerized on top of Kubernetes, rather than being run on VMs. This helps provide you with better scalability, but also because it’s running on Kubernetes, we get all of the resilience and auto scaling out of Kubernetes itself,” Scheele told TechCrunch.
He says that he and his co-founder Julian Hansert have always had a strong commitment to open source, and offering Kubermatic platform under the Apache 2.0 license is a way to show that to the community. “One of the big [things] we can bring to the table is making Kubermatic completely open source, while following the Open-core model, and having a strong commitment to open source to the world and also to the community,” he said.
Image Credit: Kubermatic
As for why it’s rebranding, he says that the original company name is a German word that means navigation pilot for a ship. The name is a nod to its Hamburg base, which is a hub for container ships. It makes sense to Germans, but not others, so they wanted a name that more broadly reflected what the company does.
“Now that we are open-sourcing Kubermatic, we also thought that people should understand our vision and what’s our DNA. It’s Kubernetes automation, helping our customers to really save money on Kubernetes operations by automating as much as possible on the operation level, so our users can really focus on building new applications,” he explained.
The company launched four years ago and has taken no funding, completely bootstrapping along the way. It’s worth noting it was one of the top five committers to the open-source Kubernetes project in 2019, along with much bigger names including Google, VMware, Red Hat and Microsoft.
Today the company has 50 employees, most of whom are working remotely by choice, rather than due to the pandemic. In fact, the company has employees working in 10 different countries. He says that has allowed him to work with people with a broad set of skills, who don’t necessarily live in Hamburg where he and Hansert are based.
Powered by WPeMatico
OpenStack adds the StarlingX edge computing stack to its top-level projects
The OpenStack Foundation today announced that StarlingX, a container-based system for running edge deployments, is now a top-level project. With this, it joins the main OpenStack private and public cloud infrastructure project, the Airship lifecycle management system, Kata Containers and the Zuul CI/CD platform.
What makes StarlingX a bit different from some of these other projects is that it is a full stack for edge deployments — and in that respect, it’s maybe more akin to OpenStack than the other projects in the foundation’s stable. It uses open-source components from the Ceph storage platform, the KVM virtualization solution, Kubernetes and, of course, OpenStack and Linux. The promise here is that StarlingX can provide users with an easy way to deploy container and VM workloads to the edge, all while being scalable, lightweight and providing low-latency access to the services hosted on the platform.
Early StarlingX adopters include China UnionPay, China Unicom and T-Systems. The original codebase was contributed to the foundation by Intel and Wind River System in 2018. Since then, the project has seen 7,108 commits from 211 authors.
“The StarlingX community has made great progress in the last two years, not only in building great open source software but also in building a productive and diverse community of contributors,” said Ildiko Vancsa, ecosystem technical lead at the OpenStack Foundation. “The core platform for low-latency and high-performance applications has been enhanced with a container-based, distributed cloud architecture, secure booting, TPM device enablement, certificate management and container isolation. StarlingX 4.0, slated for release later this year, will feature enhancements such as support for Kata Containers as a container runtime, integration of the Ussuri version of OpenStack, and containerization of the remaining platform services.”
It’s worth remembering that the OpenStack Foundation has gone through a few changes in recent years. The most important of these is that it is now taking on other open-source infrastructure projects that are not part of the core OpenStack project but are strategically aligned with the organization’s mission. The first of these to graduate out of the pilot project phase and become top-level projects were Kata Containers and Zuul in April 2019, with Airship joining them in October.
Currently, the only pilot project for the OpenStack Foundation is its OpenInfra Labs project, a community of commercial vendors and academic institutions, including the likes of Boston University, Harvard, MIT, Intel and Red Hat, that are looking at how to better test open-source code in production-like environments.
Powered by WPeMatico
Mirantis releases its first major update to Docker Enterprise
In a surprise move, Mirantis acquired Docker’s Enterprise platform business at the end of last year, and while Docker itself is refocusing on developers, Mirantis kept the Docker Enterprise name and product. Today, Mirantis is rolling out its first major update to Docker Enterprise with the release of version 3.1.
For the most part, these updates are in line with what’s been happening in the container ecosystem in recent months. There’s support for Kubernetes 1.17 and improved support for Kubernetes on Windows (something the Kubernetes community has worked on quite a bit in the last year or so). Also new is Nvidia GPU integration in Docker Enterprise through a pre-installed device plugin, as well as support for Istio Ingress for Kubernetes and a new command-line tool for deploying clusters with the Docker Engine.
In addition to the product updates, Mirantis is also launching three new support options for its customers that now give them the option to get 24×7 support for all support cases, for example, as well as enhanced SLAs for remote managed operations, designated customer success managers and proactive monitoring and alerting. With this, Mirantis is clearly building on its experience as a managed service provider.
What’s maybe more interesting, though, is how this acquisition is playing out at Mirantis itself. Mirantis, after all, went through its fair share of ups and downs in recent years, from high-flying OpenStack platform to layoffs and everything in between.
“Why we do this in the first place and why at some point I absolutely felt that I wanted to do this is because I felt that this would be a more compelling and interesting company to build, despite maybe some of the short-term challenges along the way, and that very much turned out to be true. It’s been fantastic,” Mirantis CEO and co-founder Adrian Ionel told me. “What we’ve seen since the acquisition, first of all, is that the customer base has been dramatically more loyal than people had thought, including ourselves.”
Ionel admitted that he thought some users would defect because this is obviously a major change, at least from the customer’s point of view. “Of course we have done everything possible to have something for them that’s really compelling and we put out the new roadmap right away in December after the acquisition — and people bought into it at very large scale,” he said. With that, Mirantis retained more than 90% of the customer base and the vast majority of all of Docker Enterprise’s largest users.
Ionel, who almost seemed a bit surprised by this, noted that this helped the company to turn in two “fantastic” quarters and was profitable in the last quarter, despite COVID-19.
“We wanted to go into this acquisition with a sober assessment of risks because we wanted to make it work, we wanted to make it successful because we were well aware that a lot of acquisitions fail,” he explained. “We didn’t want to go into it with a hyper-optimistic approach in any way — and we didn’t — and maybe that’s one of the reasons why we are positively surprised.”
He argues that the reason for the current success is that enterprises are doubling down on their container journeys and because they actually love the Docker Enterprise platform, like infrastructure independence, its developer focus, security features and ease of use. One thing many large customers asked for was better support for multi-cluster management at scale, which today’s update delivers.
“Where we stand today, we have one product development team. We have one product roadmap. We are shipping a very big new release of Docker Enterprise. […] The field has been completely unified and operates as one salesforce, with record results. So things have been extremely busy, but good and exciting.”
Powered by WPeMatico
Venafi acquires Jetstack, the startup behind the cert-manager Kubernetes certificate controller
It seems that we are in the middle of a mini acquisition spree for Kubernetes startups, specifically those that can help with Kubernetes security. In the latest development, Venafi, a vendor of certificate and key management for machine-to-machine connections, is acquiring Jetstack, a U.K. startup that helps enterprises migrate and work within Kubernetes and cloud-based ecosystems, which has also been behind the development of cert-manager, a popular, open-source native Kubernetes certificate management controller.
Financial terms of the deal, which is expected to close in June of this year, have not been disclosed, but Jetstack has been working with Venafi to integrate its services and had a strategic investment from Venafi’s Machine Identity Protection Development Fund.
Venafi is part of the so-called “Silicon Slopes” cluster of startups in Utah. It has raised about $190 million from investors that include TCV, Silver Lake and Intel Capital and was last valued at $600 million. That was in 2018, when it raised $100 million, so now it’s likely Venafi is worth more, especially considering its customers include the top five U.S. health insurers, the top five U.S. airlines, the top four credit card issuers, three out of the top four accounting and consulting firms, four of the top five U.S., U.K., Australian and South African banks and four of the top five U.S. retailers.
For the time being, the two organizations will continue to operate separately, and cert-manager — which has hundreds of contributors and millions of downloads — will continue on as before, with a public release of version 1 expected in the June-July time frame.
The deal underscores not just how Kubernetes -based containers have quickly gained momentum and critical mass in the enterprise IT landscape, in particular around digital transformation, but specifically the need to provide better security services around that at speed and at scale. The deal comes just one day after VMware announced that it was acquiring Octarine, another Kubernetes security startup, to fold into Carbon Black (an acquisition it made last year).
“Nowadays, business success depends on how quickly you can respond to the market,” said Matt Barker, CEO and co-founder of Jetstack . “This reality led us to re-think how software is built and Kubernetes has given us the ideal platform to work from. However, putting speed before security is risky. By joining Venafi, Jetstack will give our customers a chance to build fast while acting securely.”
To be clear, Venafi had been offering Kubernetes integrations prior to this — and Venafi and Jetstack have worked together for two years. But acquiring Jetstack will give it direct, in-house expertise to speed up development and deployment of better tools to meet the challenges of a rapidly expanding landscape of machines and applications, all of which require unique certificates to connect securely.
“In the race to virtualize everything, businesses need faster application innovation and better security; both are mandatory,” said Jeff Hudson, CEO of Venafi, in a statement. “Most people see these requirements as opposing forces, but we don’t. We see a massive opportunity for innovation. This acquisition brings together two leaders who are already working together to accelerate the development process while simultaneously securing applications against attack, and there’s a lot more to do. Our mutual customers are urgently asking for more help to solve this problem because they know that speed wins, as long as you don’t crash.”
The crux of the issue is the sheer volume of machines that are being used in computing environments, thanks to the growth of Kubernetes clusters, cloud instances, microservices and more, with each machine requiring a unique identity to connect, communicate and execute securely, Venafi notes, with disruptions or misfires in the system leaving holes for security breaches.
Jetstack’s approach to information security came by way of its expertise in Kubernetes, developing cert-mananger specifically so that its developer customers could easily create and maintain certificates for their networks.
“At Jetstack we help customers realize the benefits of Kubernetes and cloud native infrastructure, and we see transformative results to businesses firsthand,” said Matt Bates, CTO and co-founder of Jetstack, in a statement. “We developed cert-manager to make it easy for developers to scale Kubernetes with consistent, secure, and declared-as-code machine identity protection. The project has been a huge hit with the community and has been adopted far beyond our expectations. Our team is thrilled to join Venafi so we can accelerate our plans to bring machine identity protection to the cloud native stack, grow the community and contribute to a wider range of projects across the ecosystem.” Both Bates and Barker will report to Venafi’s Hudson and join the bigger company’s executive team.
Powered by WPeMatico
VMware to acquire Kubernetes security startup Octarine and fold it into Carbon Black
VMware announced today that it intends to buy early-stage Kubernetes security startup Octarine and fold it into Carbon Black, a security company it bought last year for $2.1 billion. The company did not reveal the price of today’s acquisition.
According to a blog post announcing the deal, from Patrick Morley, general manager and senior vice president at VMware’s Security Business Unit, Octarine should fit in with what Carbon Black calls its “intrinsic security strategy” — that is, protecting content and applications wherever they live. In the case of Octarine, that is cloud native containers in Kubernetes environments.
“Acquiring Octarine enables us to advance intrinsic security for containers (and Kubernetes environments), by embedding the Octarine technology into the VMware Carbon Black Cloud, and via deep hooks and integrations with the VMware Tanzu platform,” Morley wrote in a blog post.
This also fits in with VMware’s Kubernetes strategy, having purchased Heptio, an early Kubernetes company started by Craig McLuckie and Joe Beda, two folks who helped develop Kubernetes while at Google before starting their own company,
We covered Octarine last year when it released a couple of open-source tools to help companies define the Kubernetes security parameters. As we quoted head of product Julien Sobrier at the time:
Kubernetes gives a lot of flexibility and a lot of power to developers. There are over 30 security settings, and understanding how they interact with each other, which settings make security worse, which make it better, and the impact of each selection is not something that’s easy to measure or explain.
As for the startup, it now gets folded into VMware’s security business. While the CEO tried to put a happy face on the acquisition in a blog post, it seems its days as an independent entity are over. “VMware’s commitment to cloud native computing and intrinsic security, which have been demonstrated by its product announcements and by recent acquisitions, makes it an ideal home for Octarine,” the company CEO Shemer Schwarz wrote in the post.
Octarine was founded in 2017 and has raised $9 million, according to PitchBook data.
Powered by WPeMatico
Run:AI brings virtualization to GPUs running Kubernetes workloads
In the early 2000s, VMware introduced the world to virtual servers that allowed IT to make more efficient use of idle server capacity. Today, Run:AI is introducing that same concept to GPUs running containerized machine learning projects on Kubernetes.
This should enable data science teams to have access to more resources than they would normally get were they simply allocated a certain number of available GPUs. Company CEO and co-founder Omri Geller says his company believes that part of the issue in getting AI projects to market is due to static resource allocation holding back data science teams.
“There are many times when those important and expensive computer sources are sitting idle, while at the same time, other users that might need more compute power since they need to run more experiments and don’t have access to available resources because they are part of a static assignment,” Geller explained.
To solve that issue of static resource allocation, Run:AI came up with a solution to virtualize those GPU resources, whether on prem or in the cloud, and let IT define by policy how those resources should be divided.
“There is a need for a specific virtualization approaches for AI and actively managed orchestration and scheduling of those GPU resources, while providing the visibility and control over those compute resources to IT organizations and AI administrators,” he said.
Run:AI creates a resource pool, which allocates based on need. Image Credits Run:AI
Run:AI built a solution to bridge this gap between the resources IT is providing to data science teams and what they require to run a given job, while still giving IT some control over defining how that works.
“We really help companies get much more out of their infrastructure, and we do it by really abstracting the hardware from the data science, meaning you can simply run your experiment without thinking about the underlying hardware, and at any moment in time you can consume as much compute power as you need,” he said.
While the company is still in its early stages, and the current economic situation is hitting everyone hard, Geller sees a place for a solution like Run:AI because it gives customers the capacity to make the most out of existing resources, while making data science teams run more efficiently.
He also is taking a realistic long view when it comes to customer acquisition during this time. “These are challenging times for everyone,” he says. “We have plans for longer time partnerships with our customers that are not optimized for short term revenues.”
Run:AI was founded in 2018. It has raised $13 million, according to Geller. The company is based in Israel with offices in the United States. It currently has 25 employees and a few dozen customers.
Powered by WPeMatico
Cloud Foundry Foundation executive director Abby Kearns steps down to pursue a new executive role elsewhere
The Cloud Foundry Foundation (CFF), the home of the Cloud Foundry open-source developer platform, today announced that its executive director Abby Kearns is stepping down from her role to pursue an executive role elsewhere.
If you’ve followed the development of the CFF for a while, it won’t come as a surprise that its current CTO, Chip Childers, is stepping into the executive director role. For the last few years, Kearns and Childers shared duties hosting the foundation’s bi-annual conferences and were essentially the public faces of the organization.
Both Kearns and Childers stepped into their roles in 2016 after CFF founding CEO Sam Ramji departed the organization for a role at Google . Before joining the Cloud Foundry Foundation, Kearns worked on Pivotal Cloud Foundry and spent over eight years as head of product management for integration services at Verizon (which, full disclosure, is also the corporate parent of TechCrunch).
Today, according to its own data, the Linux Foundation-based Cloud Foundry project is used by more than half the Fortune 500 enterprises. And while some use the open-source code to run and manage their own Cloud Foundry platforms, most work with a partner like the now VMware-owned Pivotal.
“I am tremendously proud of Cloud Foundry and of the Foundation we have all built together,” said Kearns in today’s announcement. “Cloud Foundry offers the premier developer experience for the cloud native landscape and has seen massive adoption in the enterprise. It also has one of the strongest, kindest, most diverse communities (and staff) in open source. I leave the organization in the best hands possible. Chip was the first Foundation staff member and has served as CTO for more than four years. There is literally nobody else in the world more qualified for this job.”
During her role as executive director, Kearns helped shepherd the project through a number of changes. The most important of those was surely the rise of Kubernetes and containers in general, which quickly changed the DevOps landscape. Unlike other organizations, the CFF adapted to these changing times and started integrating these new technologies. Over the course of the last two years, the Cloud Foundry community started to deeply integrate these cloud-native technologies into its own platform, despite the fact that the community had already built its own container orchestration system in the past.
As Childers told me last year, though, the point of Cloud Foundry isn’t any specific technology, though. Instead, it’s about the developer experience. Ideally, the developers who use it don’t have to care about the underlying infrastructure and can simply integrate it into their DevOps workflow. With a lot of the recent technical changes behind it,
“We as a Foundation are turning the page to a new chapter; raising the profiles of our technical contributors, highlighting the community’s accomplishments and redefining the Cloud Foundry platform as the best Kubernetes experience for enterprise developers,” said Childers today. “Abby has done a tremendous job leading the Foundation through a period of massive growth and upheaval in the cloud native world. Her leadership was instrumental in building Cloud Foundry as a leading cloud development tool.”
As the CFF also today announced, Paul Fazzone, SVP Tanzu R&D at VMware, has been named Chairman of the Board of Directors, where he replaces Dell EMC global CTO John Roese.
“This next chapter for Cloud Foundry will be a shift forward in focusing on evolving the technology to a Kubernetes-based platform and supporting the diverse set of contributors who will make that outcome possible,” said Fazzone. “In my new role as Chairman of the Board, I look forward to helping guide the Foundation toward its goal of expanding and bolstering the ecosystem, its community and its core of users.”
Powered by WPeMatico
DataStax launches Kubernetes operator for open source Cassandra database
Today, DataStax, the commercial company behind the open source Apache Cassandra project, announced an open source Kubernetes operator developed by the company to run a cloud native version of the database.
When Sam Ramji, chief strategy officer at DataStax, came over from Google last year, the first thing he did was take the pulse of customers, partners and community members around Kubernetes and Cassandra, and they found there was surprisingly limited support.
While some companies had built Kubernetes support themselves, DataStax lacked one to call its own. Given that Kubernetes was born inside Google, and the company has widely embraced the notion of containerization in general, Ramji wanted there to be an operator specifically designed by the company to give customers a general starting point with Kubernetes.
“What’s special about the Kube operator that we’re offering to the community as an option — one of many — is that we have done the work to generalize the operator to Cassandra wherever it might be implemented,” Ramji told TechCrunch.
Ramji says that most companies that have created their own Kubernetes operators tend to specialize for their own particular requirements, which is fine, but as the company built on top of Cassandra, they wanted to come up with a general version that could appeal broader range of use cases.
In Kubernetes, the operator is how the DevOps team packages, manages and deploys an application, giving it the instructions it needs to run correctly. DataStax has created this operator specifically to run Cassandra with a broad set of assumptions.
Cassandra is a powerful database because it stays running when many others fall down. As such it is used by companies as varied as Apple, eBay and Netflix to run their key services. This new Kubernetes implementation will enable anyone who wishes to run Cassandra as a containerized application, helping push it into a modern development realm.
The company also announced a free help service for engineers trying to cope with increased usage on their databases due to COVID-19. They are calling the program, “Keep calm and Cassandra on.” The engineers charged with keeping systems like Cassandra running are called Site Reliability Engineers or SREs.
“The new service is completely free SRE-to-SRE support calls. So our SREs are taking calls from Apache Cassandra users anywhere in the world, no matter what version they’re using if they’re trying to figure out how to keep it up to stand up to the increased demand,” Ramji explained.
DataStax was founded in 2010 and has raised over $190 million, according to PitchBook data.
Powered by WPeMatico
Google Cloud launches Game Servers, a managed cloud backend for games
Google Cloud today announced the beta launch of Game Servers, a managed service that provides game developers with the usual backend services for running their games, including multi-player games, in the company’s cloud. It’s worth stressing that these are not game streaming servers but solely meant to make it easier for game developers to build, scale and manage the backend services for their games.
The service sits on top of the Agones open-source game server, a project Google and Ubisoft first announced in 2018, and the Kubernetes container orchestration platform. As Google Cloud product manager Scott Van Woudenberg told me, the team is also reusing some parts of Anthos, Google’s service for managing multi-cloud Kubernetes clusters. And while Game Servers can currently only run on the Google Kubernetes Engine, the plan is to allow for hybrid and multi-cloud support later this year.
Quite a few gaming companies have already built their own on-premises server fleets, so just like in the enterprise, having hybrid-cloud capabilities is a must-have for a tool like this. Google will also make it easy for developers who already use Agones outside of Game Servers today to bring those servers into the same managed Game Servers ecosystem by registering them with the Game Servers API.
As Van Woudenberg noted, virtually every game now needs some kind of cloud backend, be that for multi-player features, match-making or keeping persistent game stats, for example. That’s true for indie developers and major game studios. Game Servers, ideally, will make it easier for these companies to scale their clusters up and down as needed. Game Servers also provides for A/B testing and canary tests, and, in future updates, it will include integrations with the Open Match matchmaking framework.
To get started, developers still have to containerize their game servers. For those companies that already use Agones, that’s a pretty straightforward exercise, Van Woudenberg said. Others, though, need a bit more help with that, and Google is working with partners to walk them through this.
Powered by WPeMatico