From the course: Automating Kubernetes with GitOps
Unlock this course with a free trial
Join today to access over 24,700 courses taught by industry experts.
Providing operator API access - Kubernetes Tutorial
From the course: Automating Kubernetes with GitOps
Providing operator API access
- So if you are going to use Kubernetes operators, these are applications that need access to the API and that is not going to be allowed without any preparation. So what is involved? Well, in a Kubernetes GitOps environment, we want to use operators that automatically create and update applications in Kubernetes. To do so, the operator needs permissions. And to allow Kubernetes applications to manage other Kubernetes resources. Kubernetes provides the ServiceAccount resource. Each application uses a default ServiceAccount, and this default ServiceAccount provides very limited access to the cluster. For the GitOps operator to work, the ServiceAccount needs additional permissions and to obtain these permissions, RoleBindings or ClusterRoleBindings to roles and cluster roles is needed. Before continuing, let's explore the default ServiceAccount. So kubectl get pods is showing that we have default pod. So let's do this on "defaultpod -o yaml | less". And there we go, ServiceAccount is…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.
Contents
-
-
(Locked)
Module 1: Understanding the fundamentals introduction19s
-
(Locked)
Learning objectives40s
-
(Locked)
Understanding DevOps3m 44s
-
(Locked)
Exploring GitOps3m 34s
-
(Locked)
Kubernetes and GitOps49s
-
(Locked)
Deploying everything as code1m 12s
-
(Locked)
DevOps and GitOps core components46s
-
(Locked)
DevOps environments2m 43s
-
(Locked)
DevOps stages1m 50s
-
(Locked)
Webhooks and operators1m 15s
-
(Locked)
-
-
(Locked)
Module 2: From code to image introduction24s
-
(Locked)
Learning objectives29s
-
(Locked)
Understanding Git6m 48s
-
Git fundamentals8m 58s
-
(Locked)
Using Git advanced authentication7m 3s
-
(Locked)
Working with branches and merges5m 46s
-
(Locked)
Organizing Git repositories for GitOps environments2m 19s
-
(Locked)
-
-
(Locked)
Learning objectives41s
-
(Locked)
Using namespaces to represent GitOps environments1m 38s
-
(Locked)
Labels and annotations5m 57s
-
(Locked)
Using ConfigMaps to provide application data3m 58s
-
(Locked)
Kubernetes storage9m 7s
-
(Locked)
Using services1m 34s
-
(Locked)
Using Ingress9m 12s
-
(Locked)
Ingress access to services in specific namespaces5m 24s
-
(Locked)
Using NetworkPolicy to isolate GitOps environments6m 56s
-
(Locked)
-
-
(Locked)
Learning objectives49s
-
(Locked)
Understanding the project4m 44s
-
(Locked)
Preparation: Setting up Git5m 49s
-
(Locked)
Preparation: Creating a worker image7m 28s
-
(Locked)
Preparation: Setting up storage4m 39s
-
(Locked)
Preparation: Creating the YAML files14m 48s
-
(Locked)
Implementing the CI process10m 15s
-
(Locked)
Implementing the CD process2m 56s
-
(Locked)
Performing the blue/green application update45s
-
(Locked)
-
-
(Locked)
Module 5: Using Kubernetes ecosystem solutions introduction28s
-
(Locked)
Learning objectives31s
-
(Locked)
Understanding observability3m 23s
-
(Locked)
Using Kubernetes observability solutions2m 29s
-
(Locked)
Using Metrics Server3m 20s
-
(Locked)
Using Prometheus7m 4s
-
(Locked)
GitOps observability4m 57s
-
(Locked)