Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. It groups related containers into logical units called pods and manages the pods' lifecycles and services. Key Kubernetes objects include pods, deployments, services, and secrets. The declarative model defines the desired state and Kubernetes ensures the actual state matches it.
Kubernetes is designed to be an extensible system. But what is the vision for Kubernetes Extensibility? Do you know the difference between webhooks and cloud providers, or between CRI, CSI, and CNI? In this talk we will explore what extension points exist, how they have evolved, and how to use them to make the system do new and interesting things. We’ll give our vision for how they will probably evolve in the future, and talk about the sorts of things we expect the broader Kubernetes ecosystem to build with them.
ZCloud Consensus on Hardware for Distributed Systems
3rd Workshop on Dependability,
May 8, Monday 2017, İYTE,
https://goo.gl/fSVnZy
http://dcs.iyte.edu.tr/ws/ppt/10/presentation.pdf
In distributed applications where the number of members in the cluster increases, the
separation of the consensus related operations at the hardware level is essential for the
following reasons:
1. At the operating system level, messages broadcast on the protocol stack cause latency.
2. It is necessary to increase the number of completed transactions in the communication of
distributed system components and on the network unit (throughput).
3. For devices with limited storage and CPU computing facilities that use embedded operating
systems such as IOT devices, it is also necessary to reduce the processing burden due to
"consensus" operations.
4. A common consensus communication model is needed for different applications that need
to work together in (BFT) distributed systems.
Using Deep Learning Toolkits with Kubernetes clusters
Slides for the talk at the O'Reilly AI Conference San Francisco 2017 - https://conferences.oreilly.com/artificial-intelligence/ai-ca/public/schedule/detail/59613
Driving Business and Technical Agility in the Enterprise!
Container World 2017 is the only independent conference offering an exploration of the entire container ecosystem. Over 3 days, you’ll hear from the innovative enterprises, tech giants and startups who are transforming enterprise IT and driving business innovation on such topics as:
Containers and legacy infrastructure
Operations/DevOps
Orchestration & Workloads
Security
Storage/Persistent storage
Standardization and Certification
Emerging technology like serverless, unikernel and beyond
View the brochure for more information: https://goo.gl/OpnoEr
Kubernetes Interview Questions And Answers | Kubernetes Tutorial | Kubernetes...
( Kubernetes Certification Training: https://www.edureka.co/kubernetes-certification )
This Edureka tutorial on "Kubernetes Interview Questions" will help you crack interviews on various Kubernetes related roles in the industry. The different types of questions included in this session are:
1. Basic Kubernetes Interview Questions
2. Kubernetes Architecture-Based Interview Questions
3. Scenario-Based Interview Questions
4. Multiple Choice Questions
DevOps Tutorial Blog Series: https://goo.gl/P0zAfF
On Friday 5 June 2015 I gave a talk called Cluster Management with Kubernetes to a general audience at the University of Edinburgh. The talk includes an example of a music store system with a Kibana front end UI and an Elasticsearch based back end which helps to make concrete concepts like pods, replication controllers and services.
Kubernetes seems to be the biggest buzz word currently in the DevOps world. The Google designed container orchestrator based in their 10+ years of experience running production applications using containers seems to have positioned as the market leader.
Open source, available in both Google Cloud and Azure container platforms or as a custom installation, it is ready to receive production loads.
During this talk we will discover how does Kubernetes works, its architecture, what components compose a Kubernetes cluster. We will also learn what objects can a developer use to deploy its applications on a Kubernetes cluster. We will see a live demo where we will deploy an application and then introduce changes to it without any downtime.
Continuous deployment of polyglot microservices: A practical approach
This document discusses a practical approach to continuous deployment of polyglot microservices. It introduces the author and describes how traditional companies are adopting DevOps practices. The approach focuses on being continuous, using multiple programming languages as needed, immutable infrastructure with containers, reliability through functional testing, automated deployments, and practical architecture. Kubernetes and OpenShift are discussed as platform options. Lessons learned include that Kubernetes alone often fits needs better than OpenShift, and external service discovery can replace ingress controllers when using an external router.
Introduction to containers, k8s, Microservices & Cloud Native
Slides built to upskill and enable internal team and/or partners on foundational infra skills to work in a containerized world.
Topics covered
- Container / Containerization
- Docker
- k8s / container orchestration
- Microservices
- Service Mesh / Serverless
- Cloud Native (apps & infra)
- Relationship between Kubernetes and Runtime Fabric
Audiences: MuleSoft internal technical team, partners, Runtime Fabric users.
This document provides an introduction to containers and container orchestration technologies. It discusses the evolution from virtual machines to containers and the benefits of containers. It then explains why an orchestrator tool is needed to manage containers at scale. The remainder of the document defines common container and orchestration concepts, including Docker, Kubernetes objects and components, Helm for package management, and Istio for traffic management and security.
Taking the Next Hot Mobile Game Live with Docker and IBM SoftLayer
Presentation at the IBM InterConnect Conference in Las Vegas, Nevada on February 24, 2016.
Mobile games are the fastest-growing sector of the $70 billion video game industry, far outpacing traditional consoles. But companies that aspire to create the next hot title have to account for more than just the app downloaded to a user device. They must prepare for huge spikes in game play with scalable backends to handle massive data and transactions behind socially linked user profiles and global leaderboards. This talk looks at how IBM successfully partnered with Firemonkeys, a major studio that had hit their vertical scaling limit, to design and deploy a new Docker-based architecture on SoftLayer. This scale-out architecture is able to handle an order of magnitude more customers for their next major release.
Kube Overview and Kube Conformance Certification OpenSource101 Raleigh
This is my Introduction to Kubernetes and Overview of the Kubernetes Conformance Certification Program talk presented at OpenSource101 Raleigh on Feb 17, 2018
Cloud Foundry Diego: The New Cloud Runtime - CloudOpen Europe Talk 2015
The document describes Cloud Foundry Diego, a new container-based runtime for Cloud Foundry that supports running heterogeneous workloads like Docker containers, .NET applications, and tasks on different infrastructure environments. Some key points:
- Diego is an extensible, distributed system that orchestrates and schedules containerized applications and tasks across Linux and Windows container execution nodes.
- It introduces new abstractions like tasks for running single units of work, and long-running processes. These can be distributed across cells for high availability.
- The runtime aims to support running Docker images, .NET applications natively on Windows cells, as well as traditional Cloud Foundry apps, through platform-neutral APIs.
- Developers
This document discusses microservices with Docker, Kubernetes and Jenkins. It provides an overview of Kubernetes concepts like pods, replication controllers, services and labels. It also discusses how Kubernetes can help manage containers across multiple hosts and address challenges of scaling, avoiding port conflicts and keeping containers running. The document promotes using Jenkins and Kubernetes for continuous integration and delivery of containerized microservices applications. It recommends Fabric8 as a tool that can help create and deploy microservices on Kubernetes.
Kubernetes for FaaS (Function as a Service) - Serverless evolution, some basic constructs, kubenetes features, comparisons - from Serverless conference 2017 Bangalore.
Soft Introduction to Google's framework for taming containers in the cloud. For devs and architects that they just enter the world of cloud, microservices and containers
Kubernetes is an open-source tool for managing containerized applications across clusters of nodes. It provides capabilities for deployment, maintenance, and scaling of applications. The document discusses Kubernetes concepts like pods, deployments, services, namespaces and components like the API server, scheduler and kubelet. It also covers Kubernetes commands and configuration using objects like config maps, secrets, volumes and labels.
The document discusses various Kubernetes concepts including pods, deployments, services, ingress, labels, health checks, config maps, secrets, volumes, autoscaling, resource quotas, namespaces, Helm, and the Kubernetes Dashboard. Kubernetes is a container orchestration tool that manages container deployment, scaling, and networking. It uses pods to group containers, deployments to manage pods, and services for exposing applications.
Container orchestration engine for automating deployment, scaling, and management of containerized applications.
What are Microservices?
What is container?
What is Containerization?
What is Docker?
This document provides an overview of Kubernetes architecture and components. It describes how to run a simple Kubernetes setup using a Docker container. The container launches all key Kubernetes components including the API server, scheduler, etcd and controller manager. Using kubectl, the document demonstrates deploying an nginx pod and exposing it as a service. This allows curling the nginx default page via the service IP to confirm the basic setup is functioning.
Docker allows creating isolated environments called containers from images. Containers provide a standard way to develop, ship, and run applications. The document discusses how Docker can be used for scientific computing including running different versions of software, automating computations, sharing research environments and results, and providing isolated development environments for users through Docker IaaS tools. K-scope is a code analysis tool that previously required complex installation of its Omni XMP dependency, but could now be run as a containerized application to simplify deployment.
This document provides an overview of Kubernetes and containerization concepts including Docker containers, container orchestration with Kubernetes, deploying and managing applications on Kubernetes, and using Helm to package and deploy applications to Kubernetes. Key terms like pods, deployments, services, configmaps and secrets are defined. Popular container registries, orchestrators and cloud offerings are also mentioned.
Kubernetes is a portable, extensible open-source platform that facilitates automated deployment, scaling, and management of Linux containerized applications. It was developed by Google, written using the GO language. It is a PaaS(Platform as a Service) when used on the cloud, whereas it is also flexible as an IaaS(Infrastructure as a Service) and SaaS(Software as a Service) by enabling portability, simplified scaling, and provision of robust software models.
Sumo Logic Cert Jam - Advanced Metrics with Kubernetes
This document outlines an agenda for a course to become certified as a Sumo Kubernetes Analyst. The course will provide an introduction to Kubernetes and Sumo Logic's monitoring capabilities, including four different views into Kubernetes systems. Attendees will participate in hands-on labs and have the opportunity to get certified through an online exam.
This document provides an overview of Kubernetes concepts including:
- Kubernetes architecture with masters running control plane components like the API server, scheduler, and controller manager, and nodes running pods and node agents.
- Key Kubernetes objects like pods, services, deployments, statefulsets, jobs and cronjobs that define and manage workloads.
- Networking concepts like services for service discovery, and ingress for external access.
- Storage with volumes, persistentvolumes, persistentvolumeclaims and storageclasses.
- Configuration with configmaps and secrets.
- Authentication and authorization using roles, rolebindings and serviceaccounts.
It also discusses Kubernetes installation with minikube, and common networking and deployment
In the era of Microservices, Cloud Computing and Serverless architecture, it’s useful to understand Kubernetes and learn how to use it. However, the official Kubernetes documentation can be hard to decipher, especially for newcomers. In this book, I will present a simplified view of Kubernetes and give examples of how to use it for deploying microservices using different cloud providers, including Azure, Amazon, Google Cloud and even IBM.
Docker uses a client-server architecture with a Docker client communicating with the Docker daemon. The daemon manages Docker objects like images, containers, networks and volumes. Kubernetes is an open-source system that automates deployment, scaling, and management of containerized applications. It ensures containers run as expected and acquires necessary resources. Key Kubernetes components include pods, deployments, services, nodes, and the control plane which manages the cluster.
This document provides an overview of Kubernetes and DevOps. It begins with an introduction to Kubernetes, explaining that it is a container orchestration system originally developed by Google to automate deployment, scaling, and management of containerized applications. It then describes the main components of Kubernetes, including Pods, Services, Deployments, and the control plane and node structure. The document also discusses concepts like continuous integration, containers, microservices applications, and DevOps practices like rolling updates that Kubernetes facilitates.
Docker Online Training | Kubernetes Training in Ameerpet
Visualpath provides top-quality Certified Kubernetes Security Specialist Training Worldwide led by real-time instructors. We offer daily recordings and presentations for reference. Enroll for a Free Demo. Call +91-9989971070.
Visit Blog: https://visualpathblogs.com/
WhatsApp: https://www.whatsapp.com/catalog/917032290546/
Visit: https://www.visualpath.in/DevOps-docker-kubernetes-training.html
Federated Kubernetes: As a Platform for Distributed Scientific Computing
A high level overview of Kubernetes Federation and the challenges encountered when building out a Platform for multi-institutional Research and Distributed Scientific Computing.
A Kubernetes cluster contains a set of worker
machines known as nodes that run
containerized applications
ü Every cluster has at least one worker node.
Hence, if a node fails, your application will still
be accessible from the other nodes as in a
cluster, multiple nodes are grouped
Docker Kubernetes Istio
Understanding Docker and creating containers.
Container Orchestration based on Kubernetes
Blue Green Deployment, AB Testing, Canary Deployment, Traffic Rules based on Istio
Google has been running everything in containers for the past 15 years, but how do we orchestrate and manage all those containers? We've built and released the open source Kubernetes (http://kubernetes.io), which is based on years of running containers internally at Google. Join us for an introduction to containers and Kubernetes, followed by a hands-on workshop building and deploying your own Kubernetes cluster with multiple front end, database and caching instances.
Docker containers help solve the issue of process-level reproducibility by packaging up your apps and execution environments into a number of containers. But once you have a lot of containers running, you'll need to coordinate them across a cluster of machines while keeping them healthy and making sure they can find each other. This can quickly turn into an unmanageable mess! Wouldn't it be helpful if you could declare what wanted, and then have the cluster assign the resources to get it done and to recover from failures and scale on demand? Kubernetes is here to help!
Key takeaways
- Gentle introduction into containers: why and how
- Learn how Google manages applications using containers
- Intro to Kubernetes: managing applications and services
- Build and deploy your own multi-tier application using Kubernetes
Kubernetes is designed to be an extensible system. But what is the vision for Kubernetes Extensibility? Do you know the difference between webhooks and cloud providers, or between CRI, CSI, and CNI? In this talk we will explore what extension points exist, how they have evolved, and how to use them to make the system do new and interesting things. We’ll give our vision for how they will probably evolve in the future, and talk about the sorts of things we expect the broader Kubernetes ecosystem to build with them.
ZCloud Consensus on Hardware for Distributed SystemsGokhan Boranalp
3rd Workshop on Dependability,
May 8, Monday 2017, İYTE,
https://goo.gl/fSVnZy
http://dcs.iyte.edu.tr/ws/ppt/10/presentation.pdf
In distributed applications where the number of members in the cluster increases, the
separation of the consensus related operations at the hardware level is essential for the
following reasons:
1. At the operating system level, messages broadcast on the protocol stack cause latency.
2. It is necessary to increase the number of completed transactions in the communication of
distributed system components and on the network unit (throughput).
3. For devices with limited storage and CPU computing facilities that use embedded operating
systems such as IOT devices, it is also necessary to reduce the processing burden due to
"consensus" operations.
4. A common consensus communication model is needed for different applications that need
to work together in (BFT) distributed systems.
Using Deep Learning Toolkits with Kubernetes clustersJoy Qiao
Slides for the talk at the O'Reilly AI Conference San Francisco 2017 - https://conferences.oreilly.com/artificial-intelligence/ai-ca/public/schedule/detail/59613
Driving Business and Technical Agility in the Enterprise!
Container World 2017 is the only independent conference offering an exploration of the entire container ecosystem. Over 3 days, you’ll hear from the innovative enterprises, tech giants and startups who are transforming enterprise IT and driving business innovation on such topics as:
Containers and legacy infrastructure
Operations/DevOps
Orchestration & Workloads
Security
Storage/Persistent storage
Standardization and Certification
Emerging technology like serverless, unikernel and beyond
View the brochure for more information: https://goo.gl/OpnoEr
Kubernetes Interview Questions And Answers | Kubernetes Tutorial | Kubernetes...Edureka!
( Kubernetes Certification Training: https://www.edureka.co/kubernetes-certification )
This Edureka tutorial on "Kubernetes Interview Questions" will help you crack interviews on various Kubernetes related roles in the industry. The different types of questions included in this session are:
1. Basic Kubernetes Interview Questions
2. Kubernetes Architecture-Based Interview Questions
3. Scenario-Based Interview Questions
4. Multiple Choice Questions
DevOps Tutorial Blog Series: https://goo.gl/P0zAfF
On Friday 5 June 2015 I gave a talk called Cluster Management with Kubernetes to a general audience at the University of Edinburgh. The talk includes an example of a music store system with a Kibana front end UI and an Elasticsearch based back end which helps to make concrete concepts like pods, replication controllers and services.
Kubernetes seems to be the biggest buzz word currently in the DevOps world. The Google designed container orchestrator based in their 10+ years of experience running production applications using containers seems to have positioned as the market leader.
Open source, available in both Google Cloud and Azure container platforms or as a custom installation, it is ready to receive production loads.
During this talk we will discover how does Kubernetes works, its architecture, what components compose a Kubernetes cluster. We will also learn what objects can a developer use to deploy its applications on a Kubernetes cluster. We will see a live demo where we will deploy an application and then introduce changes to it without any downtime.
Continuous deployment of polyglot microservices: A practical approachJuan Larriba
This document discusses a practical approach to continuous deployment of polyglot microservices. It introduces the author and describes how traditional companies are adopting DevOps practices. The approach focuses on being continuous, using multiple programming languages as needed, immutable infrastructure with containers, reliability through functional testing, automated deployments, and practical architecture. Kubernetes and OpenShift are discussed as platform options. Lessons learned include that Kubernetes alone often fits needs better than OpenShift, and external service discovery can replace ingress controllers when using an external router.
Introduction to containers, k8s, Microservices & Cloud NativeTerry Wang
Slides built to upskill and enable internal team and/or partners on foundational infra skills to work in a containerized world.
Topics covered
- Container / Containerization
- Docker
- k8s / container orchestration
- Microservices
- Service Mesh / Serverless
- Cloud Native (apps & infra)
- Relationship between Kubernetes and Runtime Fabric
Audiences: MuleSoft internal technical team, partners, Runtime Fabric users.
This document provides an introduction to containers and container orchestration technologies. It discusses the evolution from virtual machines to containers and the benefits of containers. It then explains why an orchestrator tool is needed to manage containers at scale. The remainder of the document defines common container and orchestration concepts, including Docker, Kubernetes objects and components, Helm for package management, and Istio for traffic management and security.
Taking the Next Hot Mobile Game Live with Docker and IBM SoftLayerDaniel Krook
Presentation at the IBM InterConnect Conference in Las Vegas, Nevada on February 24, 2016.
Mobile games are the fastest-growing sector of the $70 billion video game industry, far outpacing traditional consoles. But companies that aspire to create the next hot title have to account for more than just the app downloaded to a user device. They must prepare for huge spikes in game play with scalable backends to handle massive data and transactions behind socially linked user profiles and global leaderboards. This talk looks at how IBM successfully partnered with Firemonkeys, a major studio that had hit their vertical scaling limit, to design and deploy a new Docker-based architecture on SoftLayer. This scale-out architecture is able to handle an order of magnitude more customers for their next major release.
Kube Overview and Kube Conformance Certification OpenSource101 RaleighBrad Topol
This is my Introduction to Kubernetes and Overview of the Kubernetes Conformance Certification Program talk presented at OpenSource101 Raleigh on Feb 17, 2018
Cloud Foundry Diego: The New Cloud Runtime - CloudOpen Europe Talk 2015David Soul
The document describes Cloud Foundry Diego, a new container-based runtime for Cloud Foundry that supports running heterogeneous workloads like Docker containers, .NET applications, and tasks on different infrastructure environments. Some key points:
- Diego is an extensible, distributed system that orchestrates and schedules containerized applications and tasks across Linux and Windows container execution nodes.
- It introduces new abstractions like tasks for running single units of work, and long-running processes. These can be distributed across cells for high availability.
- The runtime aims to support running Docker images, .NET applications natively on Windows cells, as well as traditional Cloud Foundry apps, through platform-neutral APIs.
- Developers
Java one kubernetes, jenkins and microservicesChristian Posta
This document discusses microservices with Docker, Kubernetes and Jenkins. It provides an overview of Kubernetes concepts like pods, replication controllers, services and labels. It also discusses how Kubernetes can help manage containers across multiple hosts and address challenges of scaling, avoiding port conflicts and keeping containers running. The document promotes using Jenkins and Kubernetes for continuous integration and delivery of containerized microservices applications. It recommends Fabric8 as a tool that can help create and deploy microservices on Kubernetes.
Kubernetes for FaaS (Function as a Service) - Serverless evolution, some basic constructs, kubenetes features, comparisons - from Serverless conference 2017 Bangalore.
Soft Introduction to Google's framework for taming containers in the cloud. For devs and architects that they just enter the world of cloud, microservices and containers
Kubernetes is an open-source tool for managing containerized applications across clusters of nodes. It provides capabilities for deployment, maintenance, and scaling of applications. The document discusses Kubernetes concepts like pods, deployments, services, namespaces and components like the API server, scheduler and kubelet. It also covers Kubernetes commands and configuration using objects like config maps, secrets, volumes and labels.
The document discusses various Kubernetes concepts including pods, deployments, services, ingress, labels, health checks, config maps, secrets, volumes, autoscaling, resource quotas, namespaces, Helm, and the Kubernetes Dashboard. Kubernetes is a container orchestration tool that manages container deployment, scaling, and networking. It uses pods to group containers, deployments to manage pods, and services for exposing applications.
Container orchestration engine for automating deployment, scaling, and management of containerized applications.
What are Microservices?
What is container?
What is Containerization?
What is Docker?
Kubernetes Architecture with ComponentsAjeet Singh
This document provides an overview of Kubernetes architecture and components. It describes how to run a simple Kubernetes setup using a Docker container. The container launches all key Kubernetes components including the API server, scheduler, etcd and controller manager. Using kubectl, the document demonstrates deploying an nginx pod and exposing it as a service. This allows curling the nginx default page via the service IP to confirm the basic setup is functioning.
Docker allows creating isolated environments called containers from images. Containers provide a standard way to develop, ship, and run applications. The document discusses how Docker can be used for scientific computing including running different versions of software, automating computations, sharing research environments and results, and providing isolated development environments for users through Docker IaaS tools. K-scope is a code analysis tool that previously required complex installation of its Omni XMP dependency, but could now be run as a containerized application to simplify deployment.
This document provides an overview of Kubernetes and containerization concepts including Docker containers, container orchestration with Kubernetes, deploying and managing applications on Kubernetes, and using Helm to package and deploy applications to Kubernetes. Key terms like pods, deployments, services, configmaps and secrets are defined. Popular container registries, orchestrators and cloud offerings are also mentioned.
Kubernetes: A Top Notch Automation SolutionFibonalabs
Kubernetes is a portable, extensible open-source platform that facilitates automated deployment, scaling, and management of Linux containerized applications. It was developed by Google, written using the GO language. It is a PaaS(Platform as a Service) when used on the cloud, whereas it is also flexible as an IaaS(Infrastructure as a Service) and SaaS(Software as a Service) by enabling portability, simplified scaling, and provision of robust software models.
Sumo Logic Cert Jam - Advanced Metrics with KubernetesSumo Logic
This document outlines an agenda for a course to become certified as a Sumo Kubernetes Analyst. The course will provide an introduction to Kubernetes and Sumo Logic's monitoring capabilities, including four different views into Kubernetes systems. Attendees will participate in hands-on labs and have the opportunity to get certified through an online exam.
This document provides an overview of Kubernetes concepts including:
- Kubernetes architecture with masters running control plane components like the API server, scheduler, and controller manager, and nodes running pods and node agents.
- Key Kubernetes objects like pods, services, deployments, statefulsets, jobs and cronjobs that define and manage workloads.
- Networking concepts like services for service discovery, and ingress for external access.
- Storage with volumes, persistentvolumes, persistentvolumeclaims and storageclasses.
- Configuration with configmaps and secrets.
- Authentication and authorization using roles, rolebindings and serviceaccounts.
It also discusses Kubernetes installation with minikube, and common networking and deployment
In the era of Microservices, Cloud Computing and Serverless architecture, it’s useful to understand Kubernetes and learn how to use it. However, the official Kubernetes documentation can be hard to decipher, especially for newcomers. In this book, I will present a simplified view of Kubernetes and give examples of how to use it for deploying microservices using different cloud providers, including Azure, Amazon, Google Cloud and even IBM.
Cloud technology with practical knowledgeAnshikaNigam8
Docker uses a client-server architecture with a Docker client communicating with the Docker daemon. The daemon manages Docker objects like images, containers, networks and volumes. Kubernetes is an open-source system that automates deployment, scaling, and management of containerized applications. It ensures containers run as expected and acquires necessary resources. Key Kubernetes components include pods, deployments, services, nodes, and the control plane which manages the cluster.
This document provides an overview of Kubernetes and DevOps. It begins with an introduction to Kubernetes, explaining that it is a container orchestration system originally developed by Google to automate deployment, scaling, and management of containerized applications. It then describes the main components of Kubernetes, including Pods, Services, Deployments, and the control plane and node structure. The document also discusses concepts like continuous integration, containers, microservices applications, and DevOps practices like rolling updates that Kubernetes facilitates.
Visualpath provides top-quality Certified Kubernetes Security Specialist Training Worldwide led by real-time instructors. We offer daily recordings and presentations for reference. Enroll for a Free Demo. Call +91-9989971070.
Visit Blog: https://visualpathblogs.com/
WhatsApp: https://www.whatsapp.com/catalog/917032290546/
Visit: https://www.visualpath.in/DevOps-docker-kubernetes-training.html
Federated Kubernetes: As a Platform for Distributed Scientific ComputingBob Killen
A high level overview of Kubernetes Federation and the challenges encountered when building out a Platform for multi-institutional Research and Distributed Scientific Computing.
Containers and container orchestration platforms like Kubernetes provide benefits for development and deployment but also introduce challenges for monitoring. A container monitoring solution needs to collect metrics on hosts, containers, the orchestration framework and applications. It should provide features like real-time analysis, predictive analytics, automated dashboards and service maps to provide visibility into the dynamic container environment. Choosing a monitoring platform that supports OpenTelemetry avoids vendor lock-in and works across cloud and self-hosted environments.
Performance Budgets for the Real World by Tammy EvertsScyllaDB
Performance budgets have been around for more than ten years. Over those years, we’ve learned a lot about what works, what doesn’t, and what we need to improve. In this session, Tammy revisits old assumptions about performance budgets and offers some new best practices. Topics include:
• Understanding performance budgets vs. performance goals
• Aligning budgets with user experience
• Pros and cons of Core Web Vitals
• How to stay on top of your budgets to fight regressions
Fluttercon 2024: Showing that you care about security - OpenSSF Scorecards fo...Chris Swan
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge.
You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter.
The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
Video traffic on the Internet is constantly growing; networked multimedia applications consume a predominant share of the available Internet bandwidth. A major technical breakthrough and enabler in multimedia systems research and of industrial networked multimedia services certainly was the HTTP Adaptive Streaming (HAS) technique. This resulted in the standardization of MPEG Dynamic Adaptive Streaming over HTTP (MPEG-DASH) which, together with HTTP Live Streaming (HLS), is widely used for multimedia delivery in today’s networks. Existing challenges in multimedia systems research deal with the trade-off between (i) the ever-increasing content complexity, (ii) various requirements with respect to time (most importantly, latency), and (iii) quality of experience (QoE). Optimizing towards one aspect usually negatively impacts at least one of the other two aspects if not both. This situation sets the stage for our research work in the ATHENA Christian Doppler (CD) Laboratory (Adaptive Streaming over HTTP and Emerging Networked Multimedia Services; https://athena.itec.aau.at/), jointly funded by public sources and industry. In this talk, we will present selected novel approaches and research results of the first year of the ATHENA CD Lab’s operation. We will highlight HAS-related research on (i) multimedia content provisioning (machine learning for video encoding); (ii) multimedia content delivery (support of edge processing and virtualized network functions for video networking); (iii) multimedia content consumption and end-to-end aspects (player-triggered segment retransmissions to improve video playout quality); and (iv) novel QoE investigations (adaptive point cloud streaming). We will also put the work into the context of international multimedia systems research.
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
Quality Patents: Patents That Stand the Test of TimeAurora Consulting
Is your patent a vanity piece of paper for your office wall? Or is it a reliable, defendable, assertable, property right? The difference is often quality.
Is your patent simply a transactional cost and a large pile of legal bills for your startup? Or is it a leverageable asset worthy of attracting precious investment dollars, worth its cost in multiples of valuation? The difference is often quality.
Is your patent application only good enough to get through the examination process? Or has it been crafted to stand the tests of time and varied audiences if you later need to assert that document against an infringer, find yourself litigating with it in an Article 3 Court at the hands of a judge and jury, God forbid, end up having to defend its validity at the PTAB, or even needing to use it to block pirated imports at the International Trade Commission? The difference is often quality.
Quality will be our focus for a good chunk of the remainder of this season. What goes into a quality patent, and where possible, how do you get it without breaking the bank?
** Episode Overview **
In this first episode of our quality series, Kristen Hansen and the panel discuss:
⦿ What do we mean when we say patent quality?
⦿ Why is patent quality important?
⦿ How to balance quality and budget
⦿ The importance of searching, continuations, and draftsperson domain expertise
⦿ Very practical tips, tricks, examples, and Kristen’s Musts for drafting quality applications
https://www.aurorapatents.com/patently-strategic-podcast.html
Coordinate Systems in FME 101 - Webinar SlidesSafe Software
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights.
During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to:
- Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value
- Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems
- Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors
- Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported
- Look Ahead: Gain insights into where FME is headed with coordinate systems in the future
Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
GDG Cloud Southlake #34: Neatsun Ziv: Automating AppsecJames Anderson
The lecture titled "Automating AppSec" delves into the critical challenges associated with manual application security (AppSec) processes and outlines strategic approaches for incorporating automation to enhance efficiency, accuracy, and scalability. The lecture is structured to highlight the inherent difficulties in traditional AppSec practices, emphasizing the labor-intensive triage of issues, the complexity of identifying responsible owners for security flaws, and the challenges of implementing security checks within CI/CD pipelines. Furthermore, it provides actionable insights on automating these processes to not only mitigate these pains but also to enable a more proactive and scalable security posture within development cycles.
The Pains of Manual AppSec:
This section will explore the time-consuming and error-prone nature of manually triaging security issues, including the difficulty of prioritizing vulnerabilities based on their actual risk to the organization. It will also discuss the challenges in determining ownership for remediation tasks, a process often complicated by cross-functional teams and microservices architectures. Additionally, the inefficiencies of manual checks within CI/CD gates will be examined, highlighting how they can delay deployments and introduce security risks.
Automating CI/CD Gates:
Here, the focus shifts to the automation of security within the CI/CD pipelines. The lecture will cover methods to seamlessly integrate security tools that automatically scan for vulnerabilities as part of the build process, thereby ensuring that security is a core component of the development lifecycle. Strategies for configuring automated gates that can block or flag builds based on the severity of detected issues will be discussed, ensuring that only secure code progresses through the pipeline.
Triaging Issues with Automation:
This segment addresses how automation can be leveraged to intelligently triage and prioritize security issues. It will cover technologies and methodologies for automatically assessing the context and potential impact of vulnerabilities, facilitating quicker and more accurate decision-making. The use of automated alerting and reporting mechanisms to ensure the right stakeholders are informed in a timely manner will also be discussed.
Identifying Ownership Automatically:
Automating the process of identifying who owns the responsibility for fixing specific security issues is critical for efficient remediation. This part of the lecture will explore tools and practices for mapping vulnerabilities to code owners, leveraging version control and project management tools.
Three Tips to Scale the Shift Left Program:
Finally, the lecture will offer three practical tips for organizations looking to scale their Shift Left security programs. These will include recommendations on fostering a security culture within development teams, employing DevSecOps principles to integrate security throughout the development
How Social Media Hackers Help You to See Your Wife's Message.pdfHackersList
In the modern digital era, social media platforms have become integral to our daily lives. These platforms, including Facebook, Instagram, WhatsApp, and Snapchat, offer countless ways to connect, share, and communicate.
In this follow-up session on knowledge and prompt engineering, we will explore structured prompting, chain of thought prompting, iterative prompting, prompt optimization, emotional language prompts, and the inclusion of user signals and industry-specific data to enhance LLM performance.
Join EIS Founder & CEO Seth Earley and special guest Nick Usborne, Copywriter, Trainer, and Speaker, as they delve into these methodologies to improve AI-driven knowledge processes for employees and customers alike.
Are you interested in learning about creating an attractive website? Here it is! Take part in the challenge that will broaden your knowledge about creating cool websites! Don't miss this opportunity, only in "Redesign Challenge"!
Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...Erasmo Purificato
Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)
Blockchain technology is transforming industries and reshaping the way we conduct business, manage data, and secure transactions. Whether you're new to blockchain or looking to deepen your knowledge, our guidebook, "Blockchain for Dummies", is your ultimate resource.
2. Kubernetes a clustered container orchestration Software
an open-source system for automating deployment, scaling, and
management of containerized applications.
It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon 15
years of experience of running production workloads at Google, combined with best-of-breed ideas and practices from the
community.
Now maintained by CNCF a non profit organization sponsored by the largest companies in tech like
google,amazon,microsoft , redhat …...
5. Desired State And the Declarative Model
In k8s we use the declarative model instead of the procedural model .
In the the declarative model we define the desired state of our object .
unlike the procedural model where we define steps and execute them.
In k8s every configuration is made using the declarative model where
we describe the target status of our object
So in the procedural model we would run a container like this : Docker run nginx
6. Desired State And the Declarative Model
In the declarative model it would be:
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
containers:
– name: nginx
image: nginx
7. Basics - POD
Pod
Kubernetes targets the management of elastic applications that consist of multiple
microservices communicating with each other. Often those microservices are
tightly coupled forming a group of containers that would typically, in a
non-containerized setup run together on one server. This group, the smallest unit
that can be scheduled to be deployed through K8s is called a pod.
8. Basics - POD
This group of containers would share storage, Linux namespaces, cgroups, IP
addresses. These are co-located, hence share resources and are always
scheduled together.
Pods are not intended to live long. They are created, destroyed and re-created on
demand, based on the state of the server and the service itself.
9. Basics - DEPLOYMENT
A Deployment controller provides declarative updates for Pods and
ReplicaSets.
You describe a desired state in a Deployment object, and the
Deployment controller changes the actual state to the desired
state at a controlled rate. You can define Deployments to create
new ReplicaSets, or to remove existing Deployments and adopt all
their resources with new Deployments.
10. Basics - SERVICE
As pods have a short lifetime, there is no guarantee about the IP address they are served on. This could make the communication of
microservices hard.
Imagine a typical Frontend communication with Backend services.
Hence K8s has introduced the concept of a service, which is an abstraction on top of a number of pods, typically requiring to run a
proxy on top, for other services to communicate with it via a Virtual IP address.
This is where you can configure load balancing for your numerous pods and expose them via a service.
11. Basics - SERVICE
We can create different types of services :
➜ Clusterip Create a clusterIP service.
➜ externalname Create an ExternalName service.
➜ Loadbalancer Create a LoadBalancer service.
➜ nodeport Create a NodePort service.
14. Networking
The Kubernetes networking model is based on a flat address space. All pods in a cluster can directly see each other. Each
pod has its own IP address. There is no need to configure any NAT. In addition, containers in the same pod share their pod's
IP address and can communicate with each other through localhost. This model is pretty opinionated, but once set up, it
simplifies life considerably both for developers and administrators. It makes it particularly easy to migrate traditional
network
applications to Kubernetes. A pod represents a traditional node and each container represents a traditional process.
15. Networking
Kubernetes use the CNI drivers model . where container networking is a driver in kubernetes and can be replaced
The major cni drivers are
Docker - Default network for single node ( minikube) uses macvlan network
Weave - an overlay network driver
Flannel - full subnet to every host backed by etcd to manage networks uses in kernel VXlAN
Calico - layer 3 kernel level implementation uses bgp for node communication does not need to use nat
Canal - a mix of both flannel and calico combines the best of bot
16. Networking
Kubernetes networking
Inter-pod communication (pod to pod)
Pods in Kubernetes are allocated a network-visible IP address (not private to the node). Pods can communicate directly without the aid
of network address translation, tunnels, proxies, or any other obfuscating layer. Well-known port
numbers can be used for a configuration-free communication scheme. The pod's internal IP address is the same as its external IP
address that other pods see (within the cluster network; not exposed to the outside world). That means that standard
naming and discovery mechanisms such as DNS work out of the box.
Pod to service communication
Pods can talk to each other directly using their IP addresses and well-known ports, but that requires the pods to know each other's IP
addresses. In a Kubernetes cluster, pods can be destroyed and created constantly. The service provides a layer of indirection that is
very useful because the service is stable even if the set of actual pods that respond to requests is ever-changing. In addition, you get
automatic, highly available load balancing because the Kube-proxy on each node takes care of redirecting traffic to the correct pod:
18. Deployments
A Deployment controller provides declarative updates for Pods and ReplicaSets.
You describe a desired state in a Deployment object, and the Deployment controller changes the actual state to the
desired state at a controlled rate. You can define Deployments to create new ReplicaSets, or to remove existing
Deployments and adopt all their resources with new Deployments.
19. Deployments
The best practices for multi tier apps on k8s are standard we
will discuss a few points .
● differentiate between the backend and the frontend with
some logical api
● all logs should be printed to stdout of containers
● all apps should be stateless except for the storage points
which should have an external storage
20. Deployments
● all apps should be defined in k8s as deployments with :
○ replicas more than one
○ health check should be defined
○ resource requests and limit should be set to be able to
account for storage /cpu /memory starvation
○ versioning metadata should be defined .
21. Deployments
● when updating databases facing app:
○ have any update to be backward compatible or
○ every database should be wrapped with an api dal
○ in any case avoid multiple writers/readers to the same
DB at most try to keep one reader/writer
● plan for failure and at any time fails pods to test for system
stability (chaos monkey)
22. METADATA
Metadata in k8s has a very big role .
As k8s provides the ability to do service discovery . we need a way to describe our services and
application
And based on that discovery we do the internal data flow of our app .
To help us in achieving manageable application k8s adds a meta data to all our apps .
Based on that metadata we define and control the flow of data in our apps .
In each pod/deployment/service/replicaset we can add a label inside our metadata section .
That allows us to tag our resources with a simple key: value pair .
We can use that key value pair to then connect services to pod/deployments and play with the flow of our
apps .
24. Deployments methods
Canary Release is the technique that we use to “softly” deploy
a new version of an application into Production. It consists of
letting only a part of the audience get access to the new
version of the app, while the rest still access the “old” version
one. This is very useful when we want to be sure about
stability in case of any changes which may be breaking, and
have big side effects.
25. Deployments methods
The point is: canary release has never been easy to be put into practice.
Depending on the environment we have, it can take so long to be put in
place that we often prefer to leave this away.
However, with Docker containers and Kubernetes orchestration it is quite
friendly to do that.
26. Deployments methods
Blue-green deployment is a technique that reduces downtime and risk by
running two identical production environments called Blue and Green.
At any time, only one of the environments is accessable , with the live
environment serving all production traffic. For this example, Blue is
currently live and Green is idle.
27. Deployments methods
As you prepare a new version of your software, deployment and the final
stage of testing takes place in the environment that is not live: in this
example, Green. Once you have deployed and fully tested the software in
Green, you switch the router so all incoming requests now go to Green
instead of Blue. Green is now live, and Blue is idle.
This technique can eliminate downtime due to application deployment. In
addition, blue-green deployment reduces risk: if something unexpected
happens with your new version on Green, you can immediately roll back to
the last version by switching back to Blue.
28. Deployments methods
A/B testing (sometimes called split testing) is comparing
two versions of a web page to see which one performs
better.
You compare two web pages by showing the two variants
(let's call them A and B) to similar visitors at the same time.
The one that gives a better conversion rate, wins!
29. Deployments methods
Rolling update
To update a service without an outage, kubectl supports what is called ‘rolling update’, which updates one pod at a time,
rather than taking down the entire service at the same time.
Rolling Update Deployment
The Deployment updates Pods in a rolling update fashion when .spec.strategy.type==RollingUpdate. You can specify
maxUnavailable and maxSurge to control the rolling update process.
30. Deployments Hands on
Login labs.play-with-k8s.com
clone : https://github.com/mikiha81/k8smeetup.git
On labs.play-with-k8s press the + button to add a node . and run the commands
1. kubeadm init --apiserver-advertise-address $(hostname -i)
2. kubectl apply -n kube-system -f
"https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 |tr -d
'n')"
Then press the + again and copy from the first node the kubeadm join command
and run it in the second node
31. Deployments Hands on
Deploy the yamls from nginx folder in the git project this is
the base line deploy .
Verify you can access it using curl run
Kubectl get svc and check the node port in the 3XXXX range
And from node 2 issue the command :
while true; do curl http://localhost:30938/version.html ; sleep
1 ; done
32. Deployments Hands on
Canray release :
In the canary-release folder print the yaml and look at the changes ….
apply the deployment yaml .
Run kubectl get pod verify the pod is up and ready .
Then go back to the 2nd node and look at the result of the curl .
Whats going on ?
Next delete the deployment for canary kubectl delete -f deployment.yaml
33. Deployments Hands on
Blue green deployment :
In the blue green deployment
First apply the service-2.0.yaml
Then apply the deployment.yaml
Wait for the container to become ready .
And apply the service.yaml …
Look the result of the curl .
What’s going on ?
Now delete the deployment .. and apply the service.yaml from the nginx folder .
34. Deployments Hands on
A/B TESTING :
How do you do it ?
Play with the deployment yaml and the service.yaml from the nginx folder and use
the v2.5 tag
Remember to reset deployment and service back to nginx default before moving
on
35. Deployments Hands on
Rolling update :
Because our default update policy is rolling update is
To do a rolling update ..
Run the command
kubectl set image deployment nginx nginx=mikiha/nginx:2.6
Run a kubectl get pod and look the pods replacing ope by one .
And go to the second node … look the curl log
36. K8s deployments limitations
deployments in kubernetes while being advanced still has some limitations
● no dependencies between different deployments
● no versioning of deployments
● somewhat limited variables declaration
● no flow control in descriptive
● no hooks when deploying and upgrading so /deploy/upgrade is linear
● no central repository for application deployment declaration
37. Deployment solution
The solution for our issues HELM
helm is maintained by the CNCF which also maintains k8s
helm uses go syntax for declarative language in deploying application to k8s
advantages of helm
● central repository
● full descriptive language with flow control
● full hooks for before and after deploying
● allows specifying of dependencies
● full versioning support
● full templating support
38. Helm - intro
Helm is a clients server solution made out of two apps .
Tiller thats the server that talks k8s and deploys the configuration to K8s.
Helm . the Client that does some of the heavy lifting and compiles the charts and
turns them into releases that deploys to tiller .
both tiller and helm are go binaries . (small and static)
as helm supports remote repositories helm know how to download charts from
remote repositories (like yum apt brew apk) . but helm does not provide a way to
upload a chart to a remote server .
39. Helm - intro continued
Helm deploys charts - those are the templates to create k8s deployments
services and most of the resources that k8s supports .
once a chart is “compiled “ and deploys to a k8s server it turn to a release .
to look for releases in a repo you can use helm search
to list charts and releases use helm ls
for instance :
helm ls
NAME REVISION UPDATED STATUS CHART NAMESPACE
miki-wordpress 1 Sun Apr 15 00:32:55 2018 DEPLOYED wordpress-1.0.0 default
viable-aardvark 1 Tue Apr 10 15:29:04 2018 DEPLOYED wordpress-1.0.0 default
40. Helm - intro continued
as you can see in this case we have two different releases for wordpress with the
same chart , this is done when using the helm install.
the first chart was installed with --name = RELEASE NAME flag , the second one
was just helm install wordpress .
also we can see the status, namespace and the revision , we can do rollback to
previous versions
helm ls
NAME REVISION UPDATED STATUS CHART
NAMESPACE
miki-wordpress 1 Sun Apr 15 00:32:55 2018 DEPLOYED wordpress-1.0.0 default
viable-aardvark 1 Tue Apr 10 15:29:04 2018 DEPLOYED wordpress-1.0.0 default
41. Helm - intro
to create a chart we use the create command in helm once we do this we create a boilerplate folder with
the name of the chart we use so . .
helm create miki-small-app
this creates the files we need for our owne chart
Charts.yaml - contains the name,description,version of the chart
values.yaml - default values that we can modify and access from each template
templates folder - a template folder contains our resources templates, we will
we will modify them for our deployments as the
template files - this can al be yaml files we declare and container resources
they must not start with _
_helpers.tpl - template file for go definitions such as function or descriptive logic code
miki-small-app/
├── charts
├── Chart.yaml
├── templates
│ ├── deployment.yaml
│ ├── _helpers.tpl
│ ├── ingress.yaml
│ ├── NOTES.txt
│ └── service.yaml
└── values.yaml
42. Helm - intro
chart folder can container a number of other chart to install other charts manually
- an optional file is requirements.yaml in the that can link to dependent charts
and their versions like
also alias field can point
to a release name
and is optional
tags and condition is also
optional
condition can link to
a value that we can reference from our parent chart
miki-small-app/
├── charts
├── Chart.yaml
├── templates
│ ├── deployment.yaml
│ ├── _helpers.tpl
│ ├── ingress.yaml
│ ├── NOTES.txt
│ └── service.yaml
└── values.yaml
dependencies:
- name: subchart
repository: http://localhost:10191
version: 0.1.0
alias: new-subchart-1
tag:
- subchart1
condition: subchart1.enabled
43. Helm - intro
looking at out default deployment :
we see some default yaml we know and love from k8s
but there are some {{ }} code . this is a generated code
from the go engine of helm , we can use this to create
descriptive code we can access from other files .
so in the name field we have the {{template “chart.fullname”}}
this actually goes to our templates file and looks for the name
of the variables we define .
same as .Values.replicacount goes to our variable.yaml file .
and the .Release.Name goes to our Charts.yaml and takes our
release name .
apiVersion: apps/v1beta2
kind: Deployment
metadata:
name: {{ template "miki-small-app.fullname" . }}
labels:
app: {{ template "miki-small-app.name" . }}
chart: {{ template "miki-small-app.chart" . }}
release: {{ .Release.Name }}
heritage: {{ .Release.Service }}
spec:
replicas: {{ .Values.replicaCount }}
selector:
matchLabels:
app: {{ template "miki-small-app.name" . }}
release: {{ .Release.Name }}
template:
metadata:
labels:
app: {{ template "miki-small-app.name" . }}
release: {{ .Release.Name }}
spec:
containers:
- name: {{ .Chart.Name }}
image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
imagePullPolicy: {{ .Values.image.pullPolicy }}
44. Helm - intro
also in our code is a reference to toYaml
this is for cases when our code is already in yaml format
for this to Yaml solves our issue with importing code
also in case where our code cannot be indented in the source
file we need to match the it to the resulting generated
yaml file we can pipe to an indent functions like so |indent NUM
we can also include function from our _helpers file
so for instance we define a code block in our template :
{{- define "my_labels" }}
labels:
generator: helm
date: {{ now | htmlDate }}
{{- end }}
and access it in our resource.yaml file like so
{{ template "mychart_app" . }}
or use the include function in the template function the code is added as as and in include its proccesd
as a function .
{{ toYaml .Values.resources | indent 12 }}
{{- with .Values.nodeSelector }}
nodeSelector:
{{ toYaml . | indent 8 }}
{{- end }}
{{- with .Values.affinity }}
affinity:
{{ toYaml . | indent 8 }}
{{- end }}
{{- with .Values.tolerations }}
tolerations:
{{ toYaml . | indent 8 }}
{{- end }}
45. Helm- Lab
To install helm download the release from here
https://storage.googleapis.com/kubernetes-helm/helm-v2.9.1-linux-amd64.tar.gz
Unpack on node 1 and run helm init
Once it's done run helm install