[zasgar]

Co-founder/CEO of Pixie here.

Thanks for the feedback. In general we try to keep the footprint of services on customer environments small. Since Pixie is mostly an ephemeral system our storage requirements are relatively modest. What this does allow us to do is process enough of the data on the customer machines locally that we only have to send back and store summaries. The long term goal is to build a cloud + edge based system where we can efficiently process data by having data locality.

Kubernetes gives us a substrate where these types of systems are manageable without too many complications. In the longer run we will likely have VPC hosted services as well for people who just don’t want to deal with it.

[chermanowicz]

Off topic from the comment you replied to, but could you explain how Pixie is different from something like Crossplane? For some reason in my head that was the first comparison I made. Your blog post does hit on a major pain point for private cloud/on-prem deployments which is management & troubleshooting post-deployment. I'm looking for the best solutions for this problem so always like to hear what people recommend.

[imukherjee]

Hi! the other co-founder/cpo here.

Pixie is an observability platform which gives access to telemetry needed to troubleshoot your workloads (observe, debug and analyze). It is not aimed to help you provision and manage your workloads.

Projects like Crossplane (which is great!) are aimed to help with workload deployment and management. Crossplane specifically enables multi/hybrid cluster deployments. It isn't necessary focussed on observability (crossplane folks can correct me here :) )