/en/tags/kubernetes/Recent content in Kubernetes on Mi&Bee BlogHugo -- gohugo.ioen蓝宝石的傻话Fri, 10 Feb 2023 00:00:00 +0000/en/posts/telemetry/pixie-try/Fri, 10 Feb 2023 00:00:00 +0000/en/posts/telemetry/pixie-try/<p>Deployment process and instructions reference: <a href="https://docs.px.dev/installing-pixie/install-guides/self-hosted-pixie/">pixie install</a></p> <h2 id="pixie-platform-main-components">Pixie Platform Main Components</h2> <ul> <li> <p><strong>Pixie Edge Module (PEM)</strong>: Pixie&rsquo;s agent, installed per node. PEMs use eBPF to collect data, which is stored locally on the node.</p> </li> <li> <p><strong>Vizier</strong>: Pixie&rsquo;s collector, installed per cluster. Responsible for query execution and managing PEMs.</p> </li> <li> <p><strong>Pixie Cloud</strong>: Used for user management, authentication, and data proxying. Can be hosted or self-hosted.</p> </li> <li> <p><strong>Pixie CLI</strong>: Used to deploy Pixie. Can also be used to run queries and manage resources like API keys.</p>/en/posts/architecture/prometheus-evolution-history-two/Mon, 12 Oct 2020 00:00:00 +0000/en/posts/architecture/prometheus-evolution-history-two/<h2 id="recap">Recap</h2> <p>In &ldquo;Monitoring System Enterprise Architecture Evolution — First Steps with Prometheus&rdquo;, the monitoring system had already been upgraded from a single-node architecture to a single <code>IDC</code> distributed architecture. The content of the previous article applies to both VM-based and container-based deployments. <code>Prometheus</code> is a product of the cloud-native era and is commonly used alongside <code>Kubernetes</code>, but <code>Prometheus</code> itself can also replace traditional monitoring solutions like <code>Zabbix</code> in non-<code>Kubernetes</code> environments. In this article, we begin to use <code>Kubernetes</code> deployment to upgrade the entire monitoring system architecture, making it more flexible for cross-region hybrid cloud business scenarios.</p>