Services & Networking Network Policies
- For Networking here consider only Requests not Response
- Ingress: Incoming to a pod Egress: Outgoing from a pod
- These policies allow/block access to pods within the cluster
- needs to be exposed via service
Links :
Storage PV & PVC
- Volume needs to be configured for each pod
- To manage storage at central level PV is used
- PV & PVC is bound based on access modes, capacity and storage class name
Links :
Questions:
- https://github.com/dgkanatsios/CKAD-exercises/blob/main/g.state.md
- https://github.com/bmuschko/ckad-prep/blob/master/7-state-persistence.md
- Used to create storage or volume blocks dynamically
- When using Storage Class we dont need to create the PV, since PV will be created automatically when storage class is created
- Create Storage Class
- Specify Storage Class in PVC
- When PVC is created the specified storage class creates a PV based on the provider mentioned in the storage class file
- Pods are deployed sequentially , when 1st pod is running then only next 1 is created
- unique index for each pod i.e 0, 1 etc, First pod will always be 0
- Even is MAster pod or pod 0 restarts it will have same index i.e 0
- Same as deployment file except needs headless service and service name
- Headless Service : each pod gets dns entry
- When a pod is created its respective Storage, PV and PVC is generated.
- If pod restarts it ensures it is connected to same pvc