If this is about validating accessibility in general, you could just replace your production container by one coming with ping pre-installed (like ubuntu), fire off your ping, and be good.
If you're okay with the ICMP flowing next to your production container, add that helper container as a sidecar. Finally, if you really need to ping from the IP address of your production container, you'll have to make sure it exists inside the container one way or another. Either build a new image to add the tool, or (given your container is based off of some Linux distribution) execute apt-get or similar package management command to install ping directly inside the container. The latter will taint your container though until it dies. These days, it's often easier to fire off an HTTP request (such as through curl), so maybe that's another option for you. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
