Change:
This is a Bug Report Problem: section of page does not cover all required reference points which are mentioned throughout page. Proposed Solution: Add references of below topics under what's next section of page. learn about service, volume. kubelet, kubectl overview. Garbage Collection that Kubernetes uses to clean up cluster resources. Types of probes. Liveness, Readiness and Startup Probes. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/sig docs /language en /assign
/remove-kind bug /triage accepted I'm not sure how much we need to tell people about Services and Volumes; maybe we should instead signpost readers to learn more about Pods in general - perhaps links to specific fragments of relevant Pod pages? Same for garbage collection really.
Thanks for reply. In that case i will add one link in general to know more about pods and service under What's next section. For garbage collection its already available under what's next section. So i will not add reference link inside page.
Oops! it was my mistake, there is no reference link provided for under what's next section. will add this too.
Hi , Below, i prepared the preview changes what i am planning to do as per my understanding based your comment above. I would like to confirm is these changes you were expecting to do for this issue. ! Please suggest.
Hi Could you please confirm on above comment.
Hi Could you please take a look on Hi Please confirm if these changes sounds good to you. So that i can go ahead and work on it, Thanks.
When adding links, please use links that have words like “volumes”; readers don't need to see the URL. If you send in a pull request we can offer feedback on it directly. Ideally we can accept it as is!
Thanks for your response, i will soon open a PR for it.
Fixed it here .

Discussion:
### Differences from regular containers Init containers support all the fields and features of app containers, <del> including resource limits, volumes, and security settings. However, the </del> <ins> including resource limits, [volumes](/docs/concepts/storage/volumes/), and security settings. However, the </ins> resource requests and limits for an init container are handled differently, as documented in [Resources](#resources).

kubectl logs myapp-pod -c init-mydb      # Inspect the second init container ``` <del> At this point, those init containers will be waiting to discover Services named </del> <ins> At this point, those init containers will be waiting to discover {{< glossary_tooltip text="Services" term_id="service" >}} named </ins> `mydb` and `myservice`. Here's a configuration you can use to make those Services appear:

have to be done by someone with root access to nodes. * All containers in a Pod are terminated while `restartPolicy` is set to Always, forcing a restart, and the init container completion record has been lost due <del> to garbage collection. </del> <ins> to {{< glossary_tooltip text="garbage collection" term_id="garbage-collection" >}}. </ins> The Pod will not be restarted when the init container image is changed, or the init container completion record has been lost due to garbage collection. This

* Read about [creating a Pod that has an init container](/docs/tasks/configure-pod-container/configure-pod-initialization/#create-a-pod-that-has-an-init-container) * Learn how to [debug init containers](/docs/tasks/debug/debug-application/debug-init-containers/) <ins> * Read about an overview of [kubelet](/docs/reference/command-line-tools-reference/kubelet/) and [kubectl](/docs/reference/kubectl/) * Learn about the [types of probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe): liveness, readiness, startup probe. </ins>