{"id":32389,"date":"2019-10-31T21:46:45","date_gmt":"2019-10-31T18:46:45","guid":{"rendered":"https:\/\/prohoster.info\/blog\/slyorm-intensiv-po-kubernetes-programma-i-bonusy\/"},"modified":"2019-10-31T21:46:45","modified_gmt":"2019-10-31T18:46:45","slug":"slyorm-intensiv-po-kubernetes-programma-i-bonusy","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/slyorm-intensiv-po-kubernetes-programma-i-bonusy","title":{"rendered":"Slurm: Intensive Course on Kubernetes. Program and Bonuses","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

From May 27 to 29, we are hosting the fourth Slurm: intensive course on Kubernetes.<\/p>\n

<\/p>\n

\"Slurm:<\/p>\n

<\/p>\n

Bonus: Online courses on Docker, Ansible, Ceph<\/strong>
\nWe have excluded topics from Slurm that are important for working with Kubernetes but are not directly related to k8s. How, why, and what came of it \u2014 below.
\nAll participants of Slurm-4 will gain access to these courses.<\/p>\n

<\/p>\n

Full money-back guarantee on the first day<\/strong>
\nAt the St. Petersburg Slurm, two participants left extremely negative feedback.<\/a><\/noindex>How I regretted not being able to go back in time and part ways with them without any mutual claims.
\nIf you realize that you absolutely dislike Slurm, on the first day<\/strong> let any of the organizers know. We will disable access and refund the full participation fee.<\/p>\n

<\/p>\n

CTO consultations<\/strong>
\nIf anyone knows Dmitry Simonov<\/a><\/noindex> (he gathered a club of CTOs), we invited him to Slurm (to learn, not to speak). He promised to consult everyone interested. This is unlikely to be interesting for administrators and developers, but very much so for IT managers.<\/p>\n

<\/a><\/noindex><\/p>\n

What is Slurm<\/h2>\n

<\/p>\n

\"Slurm:<\/p>\n

<\/p>\n

Slurm-4: Basic course (May 27-29)<\/strong>
\nDesigned for those seeing Kubernetes for the first time or looking to systematize their knowledge.
\nEach participant will create their own cluster in the Selectel cloud and deploy an application there.<\/p>\n

<\/p>\n

Price: 25,000<\/p>\n

\nProgram<\/b><\/p>\n

Topic #1: Introduction to Kubernetes, Core Components
\n\u2022 Introduction to k8s technology. Description, applications, concepts
\n\u2022 Pod, ReplicaSet, Deployment, Service, Ingress, PV, PVC, ConfigMap, Secret
\n\u2022 Practice<\/p>\n

<\/p>\n

Topic #2: Cluster Structure, Core Components, Fault Tolerance, k8s Network
\n\u2022 Cluster structure, main components, fault tolerance
\n\u2022 k8s Networking <\/p>\n

<\/p>\n

Topic #3: Kubespray, Tuning and Configuring Kubernetes Clusters
\n\u2022 Kubespray, configuring and tuning a Kubernetes cluster
\n\u2022 Practice <\/p>\n

<\/p>\n

Topic #4: Ceph, cluster configuration, and production-specific features
\n\u2022 Ceph, cluster configuration, and production-specific features
\n\u2022 Practice: setting up Ceph<\/p>\n

<\/p>\n

Topic #5: Advanced Kubernetes abstractions
\n\u2022 DaemonSet, StatefulSet, RBAC, Job, CronJob, Pod Scheduling, InitContainer <\/p>\n

<\/p>\n

Topic #6: Introduction to Helm
\n\u2022 Introduction to Helm
\n\u2022 Practice <\/p>\n

<\/p>\n

Topic #7: Publishing services and applications
\n\u2022 Overview of service publishing methods: NodePort vs LoadBalancer vs Ingress
\n\u2022 Ingress controller (Nginx): balancing incoming traffic
\n\u2022 Cert-manager: automatically obtaining SSL\/TLS certificates
\n\u2022 Practice<\/p>\n

<\/p>\n

Topic #8: Logging and monitoring
\n\u2022 Cluster monitoring, Prometheus
\n\u2022 Cluster logging, Fluentd\/Elastic\/Kibana
\n\u2022 Practice<\/p>\n

<\/p>\n

Topic #9: CI\/CD, building deployments in a cluster from scratch<\/p>\n

<\/p>\n

Topic #10: Practical work, dockerizing applications and launching in a cluster<\/p>\n

<\/p>\n

Slurm website<\/a><\/noindex><\/p>\n

<\/p>\n

MegaSlurm: advanced course (June 31 \u2014 June 2)<\/strong>
\nIntended for Kubernetes engineers and architects, as well as graduates of the basic course.
\nWe configure the cluster to simultaneously update the cluster components and deploy them to the cluster.<\/p>\n

<\/p>\n

Price: 60 thousand (45 thousand for Slyurm-4 participants)<\/p>\n

\nProgram<\/b><\/p>\n

Topic #1: The process of creating a fault-tolerant cluster from the inside
\n\u2022 Working with Kubespray
\n\u2022 Installing additional components
\n\u2022 Testing and troubleshooting the cluster
\n\u2022 Practice<\/p>\n

<\/p>\n

Topic #2: Authorization in the cluster using an external provider
\n\u2022 LDAP (Nginx + Python)
\n\u2022 OIDC (Dex + Gangway)
\n\u2022 Practice<\/p>\n

<\/p>\n

Topic #3: Network policy
\n\u2022 Introduction to CNI
\n\u2022 Network Security Policy
\n\u2022 Practice<\/p>\n

<\/p>\n

Topic #4: Secure and highly available applications in the cluster
\n\u2022 PodSecurityPolicy
\n\u2022 PodDisruptionBudget <\/p>\n

<\/p>\n

Topic #5: Kubernetes. Looking under the hood
\n\u2022 Controller structure
\n\u2022 Operators and CRD
\n\u2022 Practice <\/p>\n

<\/p>\n

Topic #6: Stateful applications in the cluster
\n\u2022 Running a DB cluster based on PostgreSQL
\n\u2022 Running a RabbitMQ cluster
\n\u2022 Practice <\/p>\n

<\/p>\n

Topic #7: Secrets management
\n\u2022 Managing secrets in Kubernetes
\n\u2022 Vault<\/p>\n

<\/p>\n

Topic #8: Horizontal Pod Autoscaler
\n\u2022 Theory
\n\u2022 Practice<\/p>\n

<\/p>\n

Topic #9: Backup and disaster recovery
\n\u2022 Backup and recovery of the cluster using Heptio Velero (formerly Ark) and etcd
\n\u2022 Practice<\/p>\n

<\/p>\n

Topic #10: Deploying applications
\n\u2022 Lint
\n\u2022 Templating and deployment tools
\n\u2022 Deployment strategies<\/p>\n

<\/p>\n

Topic #11: Practical work
\n\u2022 Building CI\/CD for application deployment
\n\u2022 Updating the cluster<\/p>\n

<\/p>\n

MegaSlyurm website<\/a><\/noindex><\/p>\n

<\/p>\n

Docker, Ansible, and Ceph<\/h2>\n

<\/p>\n

\"Slurm:<\/p>\n

<\/p>\n

A journey into history<\/strong><\/p>\n

<\/p>\n

The first Slyurm was an experiment. The speakers were finishing their presentations literally on stage, while the audience consisted of administrators skilled enough to be invited as speakers.<\/p>\n

<\/p>\n

The real foundational course emerged at the second Slyurm: 80% of the participants saw Kubernetes for the first time, and a third had never worked with Docker.
\nIt was evident how difficult it was for people to listen to a lecture on Docker in the morning and then work with it in a combat environment in the evening.
\nMany difficulties were caused by Ceph. Moreover, there were 20 people in the audience who absolutely needed an explanation of Ceph, and another 60 who had no use for it at all. <\/p>\n

<\/p>\n

By the third Slyurm, we separated Docker and Ansible into individual webinars, freeing up more time for Kubernetes. The solution turned out to be practical in essence but under-delivered in implementation: the lecture was uninteresting for experienced attendees, while the discussion was challenging for the newcomers.<\/p>\n

<\/p>\n

By the fourth Slyurm, we created online courses for Docker, Ansible, and Ceph. The idea is simple: those who need it will thoughtfully complete the course, while those who do not need it can comfortably ignore it. Based on feedback from the testing group, the Docker course takes 6-8 hours. Ansible and Ceph have not yet been timed.<\/p>\n

<\/p>\n

Disclaimer:<\/strong><\/p>\n

<\/p>\n