mirror of
https://github.com/jpetazzo/container.training.git
synced 2026-07-18 20:39:17 +00:00
Making slide easier to read
This commit is contained in:
@@ -2,21 +2,23 @@
|
||||
|
||||
- We cannot have two resources with the same name
|
||||
|
||||
(Or can we...?)
|
||||
|
||||
--
|
||||
|
||||
- We cannot have two resources *of the same type* with the same name
|
||||
|
||||
(But it's OK to have a `rng` service, a `rng` deployment, and a `rng` daemon set)
|
||||
(But it's OK to have a `rng` service, a `rng` deployment, and a `rng` daemon set!)
|
||||
|
||||
--
|
||||
|
||||
- We cannot have two resources of the same type with the same name *in the same namespace*
|
||||
|
||||
(But it's OK to have e.g. two `rng` services in different namespaces)
|
||||
(But it's OK to have e.g. two `rng` services in different namespaces!)
|
||||
|
||||
--
|
||||
|
||||
- In other words: the tuple *(type, name, namespace)* needs to be unique
|
||||
- In other words: <mark>the tuple *(type, name, namespace)* needs to be unique</mark>
|
||||
|
||||
(In the resource YAML, the type is called `Kind`)
|
||||
|
||||
@@ -190,4 +192,4 @@ Note: it might take a minute or two for the app to be up and running.
|
||||
|
||||
- the [Kubernetes documentation about network policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/)
|
||||
|
||||
- this [talk about network policies at KubeCon 2017 US](https://www.youtube.com/watch?v=3gGpMmYeEO8) by [@ahmetb](https://twitter.com/ahmetb)
|
||||
- this [talk about network policies at KubeCon 2017 US](https://www.youtube.com/watch?v=3gGpMmYeEO8) by [@ahmetb](https://twitter.com/ahmetb)
|
||||
|
||||
Reference in New Issue
Block a user