Kubernetes

Kubernetes allows to create a unified compute and scheduling substrate across many potentially disparate providers and vendors. Even more importantly, this substrate can then be used to provide developers an abstracted platform to use. That, of course, requires layers of automations and services, but that's where the unified approach of using standardized Kubernetes-based APIs and concepts pays off. Everything else is just side effects and depends on how well you execute.

• The primary impact in appropriate use cases is streamlining and unifying your computing substrate
• If leveraged properly, it *can* lead to cost savings and resourse usage efficiencies, however, it is very important to emphasize that Kubernetes by itself does NOT guarantee any of those. Use wisely!

HashiCorp Nomad

Kubernetes is widely used in the organization as the main workload for all microservices and applications, including infrastructure and dev/sec/ops deployments throughout the stack. Our Kubernetes software uses all of the orchestration's capabilities. As a tool for Kubernetes we use VMWare Tanzu.

• Big overall impact on the business throughout containerizing apps on Kubernetes.
• Solid infrastructure for all sorts of services.
• No downtime or hiccups.

Red Hat OpenShift

Red Hat OpenShift, Rook, Grafana Loki

We use Kubernetes to deploy our microservices on different servers automatically. The addressed business problems are deployment and lifecycle management of our microservices as well as checking the current state and command line output for troubleshooting if necessary. It's a very central software in our organization because it saves much time and helps to keep an stable environment

• Efficient and reliable lifecycle management of containers
• More time to focus on application than on the deployment
• Efficient management of multiple deployments and namespaces

Docker

ChatGPT, Microsoft 365, Jira Work Management, GitLab, JFrog Artifactory

We use Kubernetes in a big bare metal cluster, and we are here at the Red Hat summit to talk about a migration directly to OpenShift to create an hybrid infrastructure that can help us to achieve a more resilient services for our clients, actually we got a lot of problem with the limits of k8s, especially with the calico service middleware, when our transactions are with high demand calico gets crazy and reset connections, for example, also we got and issue with the middleware limits, we are running 160 pods for worker, and we got 6 mega hardware workers, that we cant use it fully hardware for the middleware limits, thats the reason we are leaving k8s and working in a migration to OpenShift en AWS

• this is what we came to do here in Boston, to talk about a ROI for migrate our products to OpenShift

Red Hat Ansible Automation Platform

I deploy & manage telco workloads on top of Kubernetes. These are called CNFs (Containerized network functions) which are legacy telco applications converted into K8s objects & connected via a networking & storage solution of your choice, managed by K8s. Just like every other industry, Telcos are no exception converting all their legacy applications sitting on proprietary hardware & boxes to COTS hardware & software architectures adapted toward cloud technologies. Kubernetes helps us to manage the CNFs efficiently & gives a better uptime as compared to VM-based architecture. I see the scope of flexibility & easy scaling in K8s as compared to any other technology.

• Upgrade without downtime
• Quick scaling
• Redundancy & uptime
• Flexibility to choose the various CNI & CSI options.

• Reduced downtime by more than 50%.
• Increased upgrade frequency by 30%.
• Avoided management escalations by 45%.

Red Hat OpenStack Platform

Red Hat OpenStack Platform, CentOS Linux, Nuage Networks Virtualized Services Platform (VSP)