Through this article, we will see a Proof of Concept on how to:
· Introduction · Kubelet API ∘ Don’t Panic (yet) · Searching for public unauthenticated APIs · Proof of Concept ∘ Creating a test environment ∘ Remote Code Execution ∘ Obtaining Service Account Tokens ∘ Accessing the API from inside…
If you are not patient and wants to skip the better part of the learning, here is your commands/files:
# Minikube setup
$ minikube start --kubernetes-version=v1.13.4 \
--memory=4096 \
--bootstrapper=kubeadm \
--extra-config=scheduler.address=0.0.0.0 \
--extra-config=controller-manager.address=0.0.0.0# Helm Initialization
$ kubectl create serviceaccount tiller --namespace kube-system$ kubectl create clusterrolebinding tiller-role-binding --clusterrole cluster-admin --serviceaccount=kube-system:tiller$ helm init --service-account tiller# Installing Prometheus Operator
$ helm install stable/prometheus-operator --version=4.3.6 --name=monitoring --namespace=monitoring --values=values_minikube.yaml
An introduction about terms, tools, Prometheus components and the architecture of the monitoring stack.
Prometheus, a Cloud Native Computing Foundation project, is a systems and service monitoring system. It collects…
When you are working with multiple Kubernetes clusters, it’s easy to mess up with contexts and run kubectl
in the wrong cluster. You don’t want to contribute to the kubernetes-failure-stories, I guess.
Beyond that, Kubernetes has restrictions for versioning mismatch between the client (kubectl) and server (kubernetes master), so running commands in the right context does not mean running the right client version.
[…] a client should be skewed no more than one minor version from the master, but may lead the master by up to one minor version.
Fortunately, there are some useful tools out there to help, which…
Linux lover, DevOps enthusiast, Kubernetes adept and {{insert_another_catchphrase}} — https://eduardobaitello.com.br