Learning Kubernetes isn't easy. In fact, there are so many places to start that people literally don’t know where to begin. Do they learn Kubernetes security? Networking? Infrastructure? Development? Michael Levan catches up with Kevin Evans and Robin Smorenburg to talk about their journeys into Kubernetes, how each of them started, links to learning resources, and where they’re at now.
The post Kubernetes Unpacked 007: Kubernetes From Beginner To Advanced appeared first on Packet Pushers.
Forty years ago there was an implied loyalty between companies and employees—but that world is long gone. As much as companies would like their employees to be loyal, layoff culture has crept into every corner of the modern world, especially as we move into an economic downturn. Giovanni Messina joins Russ White and Tom Ammon to talk about being prepared to be laid off, including such topics as being financially prepared, building skills for the long term, and finding community.
On today’s Tech Bytes podcast, we talk Data Processing Units (DPUs) with sponsor NVIDIA. The context is VMware’s Project Monterey. Wes Kennedy, TME for BlueField at NVIDIA, is here to discuss how NVIDIA is partnering with VMware to enable offloads of applications such as NSX and VSAN.
The post Tech Bytes: NVIDIA BlueField And Project Monterey (Sponsored) appeared first on Packet Pushers.
When people hear ‘microservices’ they often think about Kubernetes, which is a declarative container orchestrator. Because of its declarative nature, Kubernetes treats microservices as entities, which presents some challenges when it comes to troubleshooting. Let’s take a look at why troubleshooting microservices in a Kubernetes environment can be challenging, and some best practices for getting it right.
To understand why troubleshooting microservices can be challenging, let’s look at an example. If you have an application in Kubernetes, you can deploy it as a pod and leverage Kubernetes to scale it. The entity is a pod that you can monitor. With microservices, you shouldn’t monitor pods; instead, you should monitor services. So you can have a monolithic workload (a single container deployed as a pod) and monitor it, but if you have a service made up of several different pods, you need to understand the interactions between those pods to understand how the service is behaving. If you don’t do that, what you think is an event might not really be an event (i.e. might not be material to the functioning of the service).
When it comes to monitoring microservices, you need to monitor at Continue reading