Exploring docker container resource monitoring
blog.logscape.com2 pointsby thedevopsguy0 comments
1. between two people who don't know each other
2. between two people who do know each other
3. pronoun frequencies of an individual in a diary, blog over a period of time.
docker inspect $CONTAINER | grep -i VAR
docker inspect --format '{{ .NetworkSettings.IPAddress }}' replset1
K8s is complex because managing distributed services is. Not using it doesn't mean it goes away. The complexity migrates and ends up being bundled up in a separate tool or a runbook process or some script.
It's hard to maintain because the tools and apis are different from what some engineering teams are accustomed to using. Building an in-house tool gives them a warm fuzzy feeling and comfort that they can handle problems when they appear due to familiarity with their own code and design choices.
It's a fair trade off. I do wonder how much of the time spent doing this exercise could have been spent on K8S training.
I do feel that the K8S community do downplay how much a PITA k8s configuration can be and that the perceived robustness of cloud-managed K8S isn't up to scratch for something this complex.