bureaucraten, interfacemoderatoren, Beheerders (Semantic MediaWiki), Curatoren (Semantic MediaWiki), Redacteuren (Semantic MediaWiki), toezichthouders, beheerders
205
bewerkingen
Projects:Kubernetes: verschil tussen versies
Naar navigatie springen
Naar zoeken springen
→Accessing a Deployment using an Ingress
| Regel 638: | Regel 638: | ||
Sure enough, if you visit your external IP on port 80, you should see the same page served by Nginx appear! | Sure enough, if you visit your external IP on port 80, you should see the same page served by Nginx appear! | ||
== A summary so far == | |||
We've talked about: | |||
* Nodes, the machines (usually physical or VMs) that together form the Kubernetes cluster | |||
** Master nodes are nothing special, except they (also) run Pods that together form the Kubernetes Control Plane | |||
* Pods, the basic unit of scheduling; they run on Nodes and consist of at least one Container running an actual Docker Image | |||
* Deployments, which are a way to tell Kubernetes to always have some type of Pod running | |||
* Jobs, which are a way to tell Kubernetes to keep running some type of Pod until it finishes successfully | |||
* Services, which are a way to make some application in Pods accessible over TCP | |||
* Volumes, which provide various kinds of storage to Pods | |||
** Persistent Volumes are provided by the cluster administrator to allow storage | |||
** Persistent Volume Claims claim such volumes for some user | |||
** Pods can have a Persistent Volume Claim attached to them, making the contents of the volume actually usable | |||
== Accessing a Deployment using an Ingress == | == Accessing a Deployment using an Ingress == | ||