#kubernetescluster

[dgruploads]

AWS EKS | Episode 14 | Creating Kubernetes cluster in EKS | Kubernetes Cluster creation

[govindhtech]

Kubernetes Cluster Autoscaler Gets Smarter and Faster

The things that you never have to consider might sometimes have the biggest effects when it comes to cloud infrastructure. Google Cloud has a long history of subtly innovating behind the scenes with Google Kubernetes Engine (GKE), optimising the unseen gears that keep your clusters operating smoothly. Even while these improvements don’t often make the news, users will still benefit from better performance, lower latency, and an easier user experience.

Some of these “invisible” GKE developments are being highlighted by Google  Cloud, especially in the area of infrastructure autoscaling . Let’s see how the latest updates to the Cluster Autoscaler (CA) can greatly improve the performance of your workload without requiring you to make any new configurations.

What has Cluster Autoscaler updated to?

The Cluster Autoscaler the part that regulates your node pools’ size automatically based on demand has been the subject of intense development by the GKE team. Below is a summary of some significant enhancements:

Target replica count tracking

This feature helps with scaling when multiple Pods are added at once (e.g., during major resizes or new deployments). Additionally, a 30-second delay that hampered GPU autoscaling is gone. The community as a whole will gain from enhanced Kubernetes performance when this capability becomes open-source.

Quick homogenous scale-up

By effectively bin-packing pods onto nodes, this optimisation expedites the scaling process if you have many identical pods.

Reduced CPU waste

When several scale-ups across many node pools are required, the Cluster Autoscaler now takes decisions more quickly. Furthermore, Cluster Autoscaler is more intelligent about when to execute its control loop, preventing needless delays.

Memory optimisation

The Cluster Autoscaler has also undergone memory optimisations, which add to its overall efficiency even though they are not immediately evident to the user.

Benchmarking outcomes

In order to showcase the practical implications of these modifications, Google Cloud carried out a sequence of tests utilising two GKE versions (1.27 and 1.29) and several scenarios:

At the infrastructure level

Autopilot generic 5k scaled workload: Google  Cloud assessed the time it took for each pod to become ready after deploying a workload with 5,000 replicas on Autopilot.

Busy batch cluster: By generating 100 node pools and launching numerous 20-replica jobs on a regular basis, Google  Cloud replicated a high-traffic batch cluster. The scheduling latency was then assessed by Google Cloud.

10-replica GPU test: The amount of time it took for each pod to be ready was determined using a 10-replica GPU deployment.

Level of workload:

Application end-user latency test: Google Cloud used a standard web application that, in the absence of load, reacts to an API call with a defined latency and response time. Google  Cloud evaluated the performance of different GKE versions under a typical traffic pattern that causes GKE to scale with both HPA and NAP using the industry-standard load testing tool, Locust. Google  Cloud used an HPA CPU goal of 50% and scaled the application on CPU to assess end-user delay for P50 and P95.

Results highlights 

ScenarioMetricGKE v1.27(baseline)GKE v1.29Autopilot generic 5k replica deploymentTime-to-ready7m 30s3m 30s (55% improvement)Busy batch clusterP99 scheduling latency9m 38s7m 31s(20% improvement)10-replica GPUTime-to-ready2m 40s2m 09s(20% improvement)Application end-user latencyApplication response latency as measured by the end user. P50 and P95 in seconds.P50: 0.43sP95: 3.4sP50: 0.4sP95: 2.7s(P95: 20% improvement)Note: These results are illustrative and will vary based on your specific workload and configuration

Major gains usually require rigorous optimisation or overprovisioned infrastructure, such as cutting the deployment time of 5k Pods in half or improving application response latency at the 95th percentile by 20%. One notable feature of the new modifications to Cluster Autoscaler is that these gains are achieved without the need for elaborate settings, unused resources, or overprovisioning.

Several new features, both visible and unseen, are added with every new version of GKE, so be sure to keep up with the latest updates. And keep checking back for further details on how Google  Cloud is working to adapt GKE to the needs of contemporary cloud-native applications!

This article offers instructions for maintaining the smoothest possible update of your Google Kubernetes Engine (GKE) cluster as well as suggestions for developing an upgrade plan that meets your requirements and improves the availability and dependability of your environments. With little interruption to your workload, you may use this information to maintain your clusters updated for stability and security.

Create several environments

Use of numerous environments is recommended by Google  Cloud as part of your software update delivery procedure. You may reduce risk and unplanned downtime by using multiple settings to test infrastructure and software changes apart from your production environment. You should have a pre-production or test environment in addition to the production environment, at the very least.

Enrol groups in channels for release

Updates for Kubernetes are frequently released in order to bring new features, address known bugs, and provide security updates. You can choose how much emphasis to place on the feature set and stability of the version that is deployed in the cluster using the GKE release channels. Google automatically maintains the version and upgrade cadence for the cluster and its node pools when you enrol a new cluster in a release channel.

In summary

Google  Cloud is dedicated to ensuring that using and managing Kubernetes is not only powerful but also simple. Google  Cloud helps GKE administrators focus on their applications and business objectives while ensuring that their clusters are expanding effectively and dependably by optimising core processes like Cluster Autoscaler.

Read more on govindhtech.com

[techdirectarchive]

(via Create and monitor Apps using the Azure Kubernetes Service manifest)

[virtualizationhowto]

Minikube vs k3s: Pros and Cons for Developers and DevOps

Minikube vs k3s: Pros and Cons for Developers and DevOps #kubernetes #minikube #k3s #rancherlabs #productionkubernetes #k8s #singlenodekubernetes #kubernetesdevelopmentcluster #kubernetescluster #minikubevsk3s #homelab #homeserver #devops #development

Kubernetes is one of the skills that developers and DevOps need to have experience within 2024 and beyond. Kubernetes has established itself as the de facto standard for running containers with high-availability. One of the places that most developers and DevOps start with is a local Kubernetes cluster for local development. There are a couple of Kubernetes distributions that many begin with for…

[zenesys]

Configure your Kubernetes cron jobs optimally to run the cron jobs as you expect on a Kubernetes cluster. You can simplify many daily Kubernetes cluster tasks through a web interface.

[johnthetechenthusiast]

Register here to join him: https://lnkd.in/dumUxaf5 Shubham Katara is going to share some extra thoughts and insights on Kubernetes!☸️ Don't miss his masterclass. It's not only about learning! it's about developing your career path!✨ Register now!! it's on 12th November at 10 AM🕙

[devopstrainingpune]

Want to explore new career options, We have DevOps & Kubernetes Training with placement opportunities. Join us and become a part of an IT world.

Register with us:

Contact us for details: +91 741 007 3340

visit our website:

https://devopstraininginpune.com/courses/kubernetes-online-training/

[devopsaws]

Free DevOps Real-time Projects video tutorials - Visualpath Java App Deployment on Kubernetes Cluster https://youtu.be/vtgg7aFbpNk Subscribe to our channel to get video updates. https://bit.ly/2NCWRWj For DevOps Real-time Projects Tutorial Playlist https://bit.ly/34PBzy0

[awesomebharathithings]

Kubernetes components

A cluster may be a set of machines, called nodes, that run containerized applications managed by Kubernetes. A cluster has at least one worker node and one master node

[markiis]

Kubernetes! Look at its market demand in the chart. Currently, China is leading the world by showing more interest in Kubernetes. #kubernetes #kubernetesio #kubernetestraining #kubernetesmsk #kubernetesmeetup #kubernetesconsulting #kubernetesmovie #kubernetesday #kubernetescluster #kubernetesdojo #kubernetesstudio #kubernetesasaservice #kubernetesmoscow #kubernetesdocker #kubernetessg #kubernetessea #kubernetestips #kubernetess #kubernetesengine #kubernetesonaws #kubernetescourse #kübernetes #kubernetes_sri_lanka #kubernetes❣️ #kubernetes101 #kubernetesapp #kubernetesservices #kubernetesdockerworkshop #kubernetes4eva #kubernetesahoi https://www.instagram.com/p/Bv6kzRQn6TE/?utm_source=ig_tumblr_share&igshid=15ummf6bkdchx

[snapblocs]

Kubernetes is an open source platform that automates many of the manual processes like deploying and managing applications. With snapblocs deploy your apps on Kubernetes. For more information visit our website.

[syseleven]

Der Kubernetes Hype: Mit MetaKube ein eigenes Produkt

Der Hype um Kubernetes ist ungebrochen. Aber was genau bedeutet es, wenn Kubernetes Dein Job ist und Du mit MetaKube einen neuen Kubernetes Dienst aus Deutschland kreiert hast? Wir haben mit den SysEleven Experten Olaf und Simon genau darüber gesprochen und warum es für beide eine gute Sache ist, Teil der SysEleven Familie zu sein.

Was macht das Thema “Kubernetes” für euch so spannend?

Simon: Kubernetes macht einfach mehr richtig als andere Tools. Es kümmert sich beispielsweise darum, dass Deine Applikation lebt, ohne dass wir da eingreifen müssten.

Olaf: Stimmt. Kubernetes verändert unsere traditionelle Operations-Arbeit massiv. Und zwar zum Besseren! Wenn früher zum Beispiel ein Web- oder App-Server abgeschmiert ist, musste ein Kollege aus Operations raus und ihn neu von Hand starten. Oder wenn die Last stieg, musste man nachts raus und ein paar Webserver bauen, um die Last zu verteilen. Das sind ja alles Sachen, die Kubernetes maschinell übernimmt. Und das sogar echt vernünftig inkl. Infrastrukturzuweisung oder einer eigenen API, so dass man eigene Dienste deployen und weiter automatisieren kann.

Simon: Bei Docker bzw. Kubernetes skalierst Du tatsächlich Applikationen. Und das mit einem super geringen Overhead.

Olaf: Aber man muss echt betonen: Ohne Dockerhub wäre der Hype nicht da. Weil “Docker run Ngnix” ist im Endeffekt der Grund, warum es heute so einfach ist zu spawnen oder zu betreiben.

Wie kam es zu der Idee von MetaKube?

Simon: Wir wollten unseren Kunden eine Container-Infrastruktur anbieten. Wir mussten aber relativ schnell einsehen: Wenn wir für jeden Kunden ein Kubernetes-Cluster erstellen, wäre der Wildwuchs nicht mehr weit gewesen. Dann hätten wir auf einmal an die 100 Cluster managen müssen. Da wären wir ja nur noch mit für unsere Kunden ineffizientem Management als mit allem anderen beschäftigt…

Olaf (schmunzelt): Wir sind halt nicht so die klassischen Manager-Typen.

Simon: Genau! Und für den Kunden hätte das unnötige Overheads bedeutet.

Olaf: Dadurch dass wir Control Planes der Kundencluster zentral managen, können wir Ressourcen viel effizienter verwalten. Außerdem können wir unseren Kunden so besser und schneller helfen. Das war ehrlich gesagt das größte Ziel bei MetaKube: Wir wollten es dem Kunden einfach machen, Kubernetes für sich zu nutzen. Quasi den komplizierten Teil abnehmen, so dass der Kunde direkt produktiv sein kann.

Simon: Und das haben wir erreicht. Mit MetaKube hast Du in 5 Minuten Dein eigenes Cluster und kannst loslegen. Wir sind dabei als Team immer im Hintergrund und stehen mit Rat und Tat zur Seite.

Wie ist es für euch, mit MetaKube ein eigenes Produkt aus der Taufe zu heben?

Simon: Es ist cool, wenn man etwas baut, dass die Kunden dann auch benutzen wollen. Und wenn wir positives Feedback bekommen — sowohl vom Kunden als auch den Kollegen.

Olaf: Ja, da fallen mir auch unsere internen und externen MetaKube Workshops ein, die Basti und Du regelmäßig haltet. Da sieht man, dass unser Fachwissen wirklich geschätzt wird und der manchmal mühsame Weg, es zu erlangen, sich gelohnt hat.

Simon: Stimmt. Plus wir haben natürlich viel mehr Freiheiten und Flexibilität, da wir MetaKube entwickeln. Hätten wir zum Beispiel einfach Openshift eingekauft und es würde etwas nicht laufen, dann könnten wir nur ein Ticket beim Hersteller aufmachen und unsere Kunden könnten nicht arbeiten. Das entspricht einfach nicht dem Anspruch von SysEleven.

Olaf: Wir setzten ja auf dem Produkt Kubermatic unseres Partners Loodse auf. Hier haben wir zum Beispiel Quellcode-Zugriff, obwohl es nicht rein OpenSource ist. So können wir nicht nur Request stellen, sondern entwickeln auch selber neue Lösungen zum Beispiel für Backup, Monitoring oder WebUIs.

Simon: SysEleven ist auch als einer der wenigen in Deutschland als Certified Hosting Provider der CNCF gelistet — und der damit die Vorgaben erfüllt. Das macht uns schon stolz.

Wie ist es eigentlich für Euch, direkten Kundenkontakt zu haben?

Simon: Das ist super. Natürlich mag es auf den ersten Blick etwas beängstigend sein, weil theoretisch ja auch negative Kritik kommen kann. Aber das ist bis jetzt Gott sei Dank noch nicht vorgekommen.

Olaf: Wir entwicklen ja für den Kunden und nicht fürs stille Kämmerlein. So verstehen wir auch unseren Support: Pro aktiv und nachhaltig. Wenn wir im Monitoring erkennen, dass etwas im Kundencluster nicht stimmt, dann fixen wir es — oft bevor der Kunde es überhaupt festgestellt hat — und erklären dann dem Kunden, was wir gemacht haben. Das sind immer gute Gespräche auf Augenhöhe und am Ende werden so alle nur besser.

Letzte Frage: Was macht SysEleven für Euch besonders als Arbeitgeber?

Olaf: Ich hab echt das Gefühl, dass wir den Kunden weiterbringen können. Und das ist ein gutes Gefühl. Außerdem ist SysEleven selbst finanziert und wir können deshalb ohne Investorendruck arbeiten — ich glaube das ist in Berlin wirklich selten geworden. Außerdem sind wir echt ein richtig gutes Team!

Simon: Bei SysEleven kann ich mit MetaKube etwas bauen, dass Menschen wirklich benutzen wollen. Außerdem können wir uns hier mit Gleichgesinnten austauschen. Das Fachwissen der Kollegen ist bemerkenswert und zudem fahren wir regelmäßig auf internationale Konferenzen, um uns weltweit zu vernetzen und Wissen zu teilen. Für uns gilt: Je mehr Kommunikation, desto leichter fällt es, besser zu werden.

Gerne zeigen Dir Simon, Olaf und der Rest des Teams, wie Du mit Kubernetes erfolgreich sein kannst. Zum Beispiel bei unseren Workshops oder bei einem Kaffee in Berlin-Friedrichshain! Du möchtest Teil des Teams werden? Dann findest Du hier alle IT-Jobs, die wir aktuell ausgeschrieben haben.

Mehr News aus der IT-Welt auf: www.syseleven.de/blog

[govindhtech]

Use SUSE Edge For Telco On Dell PowerEdge XR8620 Servers

SUSE Certification for Telecom Transformation on Dell Telecom Servers. The CSPs may benefit from increased performance and flexibility in cloud transformation with to SUSE Edge and Dell’s joint certification.

Navigating the Future of Telecom with SUSE Certification and Dell’s PowerEdge XR8620

Staying ahead in the ever evolving telecoms industry requires implementing cutting-edge technology that may spur creativity and efficiency.

Integrating a strong infrastructure that can handle complicated telecom demands is essential for mobile carriers. The partnership between SUSE and Dell Technologies becomes crucial at this point. The SUSE Edge for Telco Platform on Dell PowerEdge XR8620 servers offers a potent telecom industry solution with to its joint accreditation in the Dell Technologies Open Telecom Ecosystem Lab (OTEL).

The Value of Joint Certification in OTEL

Joint certification ensures that the integration of SUSE and Dell’s technologies satisfies strict requirements for performance, scalability, and reliability by using the best of both companies’ capabilities. This lowers the risk and complexity frequently connected with new technology installations for mobile operators by implementing solutions that have been extensively tested and tailored for telecom settings.

The OTEL accreditation procedure also demonstrates both businesses’ dedication to advancing cloud transformation and assisting telecom networks’ digital transformation.

Why Choose SUSE Edge for Telco on Dell PowerEdge XR8620?

Enhanced Performance 

Optimal performance for telecom operations is ensured by the combination of the strong hardware of the Dell PowerEdge XR8620 server and the high-performance capabilities of the SUSE Telco platform. This integration is a great option for operators that want to improve their infrastructure since it works especially well for managing demanding telecom applications at the data center, cloud, or edge.

Scalability 

To effectively manage the enormous number of Kubernetes clusters, telecom operators need scalable solutions. Large-scale deployments are supported by the Dell PowerEdge XR8620 server, which is a suitable match for SUSE Edge for Telco’s capacity to manage heavy telecom workloads.

Reliability 

Both the Dell PowerEdge XR8620 and SUSE Edge for Telco servers provide reliable and consistent performance in a sector where uptime and dependability are crucial. For telecom providers that need to guarantee smooth service delivery to their clients, this dependability is essential.

Adaptability and Personalization

The Dell PowerEdge XR8620 servers’ adaptable hardware and SUSE Edge for Telco’s open and flexible architecture make it simple to integrate and customize with current systems. Because of this flexibility, operators may modify their infrastructure to suit certain requirements, increasing operational effectiveness.

Efficient Management 

Complex telecom networks can be difficult to manage. Nevertheless, this procedure is streamlined by solutions like SUSE Rancher Prime, which make infrastructure administration easier and cut down on operational complexity and time. Telecom operators are able to concentrate less on daily administration duties and more on strategic initiatives as a result of this efficiency.

Ease of Deployment

Telecom operators can set up and maintain their infrastructure with less manual involvement thanks to the most recent version of the SUSE Telco platform, which offers zero-touch deployment. This deployment simplicity is perfect for effectively growing operations and promptly adjusting to shifting business requirements.

Focusing on Telecom Workloads

For telecom workloads, the joint certification of the SUSE Telco platform on Dell PowerEdge XR8620 is very important. From core to edge, this reference architecture makes it easier to host contemporary, cloud-native telecom apps at scale. It gives telecom operators the adaptability and durability required to satisfy the needs of the modern digital environment by supporting network edge applications, centralized RAN, and distributed RAN.

In conclusion

The certified combination of SUSE Edge for Telco and Dell PowerEdge XR8620 servers is an attractive option for mobile operators looking to lead innovation and speed up modernization. In addition to improving performance and dependability, our collaboration offers the flexibility and management effectiveness required for a successful cloud shift.

Telecom operators may confidently create an infrastructure that supports their expansion and adjusts to the changing needs of the telecom sector by selecting SUSE and Dell. Examine the Reference Architecture created by Dell and SUSE to see how this partnership may revolutionize your business processes and propel you to the forefront of telecom innovation.

Read more on govindhtech.com

[techdirectarchive]

(via Create and monitor Apps using the Azure Kubernetes Service manifest)

[virtualizationhowto]

K8Studio New Kubernetes Cluster Management IDE Tool

K8Studio New Kubernetes Cluster Management IDE Tool #vmwarecommunities #kubernetes #containers #docker #kubernetesmanagement #kuberneteside #k8studio #learningkubernetes #kubernetescluster #kubernetesdevelopment #virtualizationhowto #vhtforums

I am always looking for new Kubernetes tools to manage Kubernetes clusters differently or with new capabilities. I saw a tool that caught my attention called K8Studio. By its own description, K8Studio is designed to simplify and enhance the experience of managing Kubernetes clusters. Table of contentsWhat is K8Studio?K8Studio featuresPrerequisites for the installInstalling K8StudioImpressions…