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.
Ingress access to services in specific namespaces - Kubernetes Tutorial
From the course: Automating Kubernetes with GitOps
Ingress access to services in specific namespaces
- [Instructor] Now in a GitOps environment it will be very interesting if Ingress can access Services in specific Nyamespaces. No there's a problem here. And the problem is that Ingress can only access Services in the same Namespace. Ingress is Namespaced, Services are Namespaced and by default there is no cross-Namespace access. In a GitOps environment where applications are running in specific Namespaces according to the stage that they are in, direct access from Ingress to these Services is very convenient, but not possible. Fortunately, there is a solution and that is the ExternalName Service type. It's a Service type that is not often used and it is used to connect to another DNS name. It's based on the fact that every Service in Kubernetes gets a DNS name. That is managed by the Kubernetes internal DNS name. And this ExternalName Service type can be living in any other Namespace referring to whatever Namespace you want. So that's a solution that you want to use. So Ingress is…
Contents
-
-
-
-
-
-
-
-
-
-
(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)
-
-
-
-
-
-
-
-
-
-