The coming eBPF revolution and why Kubernetes monitoring will never be the same
1–10 of 14 posts
Re: The coming eBPF revolution and why Kubernetes monitoring will never be the same
#2> You need Kubernetes, and you need to be able to monitor your environment, but you don’t have the resources to staff up.
Then you don't necessarily need it. You can also use cloud native solutions which is meant to address many scenarios (of course not every) like this one where there's lots to do and not enough people, offload the thinking to a provider. If you're running thin, then you should not be subjecting yourself to a system like k8s, it requires going in with eyes wide open and a lot of awareness.
Re: The coming eBPF revolution and why Kubernetes monitoring will never be the same
#3> You need Kubernetes
No, you THINK you need k8s.
Re: The coming eBPF revolution and why Kubernetes monitoring will never be the same
#4Cilium wasn't mentioned and i think thats wrong. It should be part of the history of eBPF with Kubernetes as a fundamental CNI (now also with a service mesh) build with eBPF.
Its also part of the micro docume regarding eBPF and Brendan Greggs usage of eBPF for performance insights etc.
Re: The coming eBPF revolution and why Kubernetes monitoring will never be the same
#5> You need Kubernetes, and you need to be able to monitor your environment, but you don’t have the resources to staff up. Then you don't necessarily need it. You can also use cloud native solutions which is meant to address many scenarios (of course not every) like this one where there's lots to do and not enough people, offload the thinking to a provider. If you're running thin, then you should not be subjecting you…
Agree and disagree.
K8s is the only opensource infrastructure layer there is, which has value.
But if you already have a small infra/cloud team, you do have potentially enough dev teams / product size to go with k8s if you want to.
Re: The coming eBPF revolution and why Kubernetes monitoring will never be the same
#6With the marketshare that Kubernetes has, I can definitely see why so many eBPF projects focus on supporting it.
Still makes me wish more of them had support for things like HashiCop Nomad, standalone Docker/Podman, or standalone hosts.
Maybe one day! Could be really interesting to see this kind of stuff used inthe likes of homelabs or just smaller environments, or even just environments where kubernetes isn't in.
Re: The coming eBPF revolution and why Kubernetes monitoring will never be the same
#7> You need Kubernetes, and you need to be able to monitor your environment, but you don’t have the resources to staff up. Then you don't necessarily need it. You can also use cloud native solutions which is meant to address many scenarios (of course not every) like this one where there's lots to do and not enough people, offload the thinking to a provider. If you're running thin, then you should not be subjecting you…
Agree and disagree. K8s is the only opensource infrastructure layer there is, which has value. But if you already have a small infra/cloud team, you do have potentially enough dev teams / product size to go with k8s if you want to.
There hashicorp nomad which dead simple to run and maintain.
Re: The coming eBPF revolution and why Kubernetes monitoring will never be the same
#8Earlier quoted context omitted.
Agree and disagree. K8s is the only opensource infrastructure layer there is, which has value. But if you already have a small infra/cloud team, you do have potentially enough dev teams / product size to go with k8s if you want to.
There hashicorp nomad which dead simple to run and maintain.
It's also not open source.
Re: The coming eBPF revolution and why Kubernetes monitoring will never be the same
#9> You need Kubernetes, and you need to be able to monitor your environment, but you don’t have the resources to staff up. Then you don't necessarily need it. You can also use cloud native solutions which is meant to address many scenarios (of course not every) like this one where there's lots to do and not enough people, offload the thinking to a provider. If you're running thin, then you should not be subjecting you…
Agree and disagree. K8s is the only opensource infrastructure layer there is, which has value. But if you already have a small infra/cloud team, you do have potentially enough dev teams / product size to go with k8s if you want to.
> K8s is the only opensource infrastructure layer there is, which has value.
Depending on your definition, I think both docker swarm and incus (nee LXD) count. Maybe even proxmox.
Re: The coming eBPF revolution and why Kubernetes monitoring will never be the same
#10Earlier quoted context omitted.
There hashicorp nomad which dead simple to run and maintain.
It's also not open source.
Just wanting to understand the definition of Open Source you are using here, considering that you can see and download the source here:
https://github.com/hashicorp/nomad
Are you maybe referring to their Enterprise offering?