Today we'll explore our running workloads, services, ingresses, and other Kubernetes resources we have mentioned but not delved into.
In previous parts of this course we have used the kubectl tool for all our interactions with Kubernetes. Once you have a solid understanding of kubectl and the YAML that drives resources, it's a good time to explore other tools you are likely to encounter. Neither of these tools can perform every operation that kubectl can, but they still well suited to certain roles and tasks. For example, someone who is mostly interested in seeing when a failure is occurring or looking at logs could do so very quickly with either tool below.
Skipping kubectl in favor of GUI-based tools, or trying to avoid understanding YAML is a recipe for disaster. Certain operations are only able to be performed in kubectl, and the official documentation assumes you have a solid understanding of YAML.
Follow along to learn how to use Datadog dashboards to quickly see the status of your Kubernetes resources.
If you are interested in running your own lab cluster, below are some options for doing so. Both of these projects are geared towards developers running a lab, and get you up and running quickly compared to deploying a traditional cluster.