Bare-Metal Kubernetes Servers and SUSE Servers

While most instances of Kubernetes today are deployed on virtual machines running in the cloud or on-premises, there is a growing number of instances of Kubernetes being deployed on bare-metal servers.

The two primary reasons for opting to deploy Kubernetes on a bare- metal server over a virtual machine usually are performance and reliance on hardware accelerators. In the first instance, an application deployed at the network edge might be too latency-sensitive to tolerate the overhead created by a virtual machine. AT&T, for example, is working with Mirantis to deploy Kubernetes on bare-metal servers to drive 5G wireless networking services.

"We have had multiple situations with respect to security breaches in the last couple of years, albeit all the open source companies worked together to address the instances. As the source code is freely available even if something goes wrong, SUSE work closely with open source software vendors to mitigate the risk", Ronald de Jong, President of -Sales, SUSE said in an interview with ET CIO.

It has been a while since we published the original image life-cycle guidelines SUSE Image Life Cycle for Public Cloud Deployments. Much has been learned since, technology has progressed, and the life-cycle of products has changed. Therefore, it is time to refresh things, update our guidance, and clarify items that have led to questions over the years. This new document serves as the guideline going forward starting February 15th, 2019 and supersedes the original guideline. Any images with a date stamp later than v20190215 fall under the new guideline. The same basic principal as in the original guideline applies, the image life-cycle is aligned with the product life-cycle of the product in the image. Meaning a SLES image generally aligns with the SUSE Linux Enterprise Server life-cycle and a SUSE Manager image generally aligns with the SUSE Manager life-cycle.