Deploy Apache Pulsar on AKS
Budget: ₹12,500 – ₹37,500 INR
I need a production-ready Apache Pulsar cluster running on Azure Kubernetes Service so I can move all of my real-time data streaming into one place. The cluster will ingest streams coming simultaneously from IoT devices, several web applications, and our core database systems, so resilience and horizontal scalability are critical.
I’m already committed to AKS, so please work with native Kubernetes objects and any Azure-specific best practices you rely on. Helm is fine, as are plain manifests—what matters most is that the deployment is repeatable and can be promoted between environments without surprises.
Deliverables I expect:
• A fully automated deployment (Helm chart or equivalent) that spins up a multi-broker Pulsar cluster with BookKeeper, ZooKeeper, and any required proxies on AKS
• Secure networking, TLS enabled, and RBAC configured for topic-level access
• Pulsar topics pre-created or templated for the three data sources mentioned above, each with sensible partitions and retention policies
• Basic monitoring wired into Prometheus and Grafana dashboards so I can track broker health, storage usage, and end-to-end latency
• A short run sheet or README that walks me through scaling a broker, upgrading the chart, and adding a new topic
The work is done when I can run one command, watch the pods come up cleanly, and push sample messages from my IoT simulator, a web app, and a test database connector—all of which should arrive in the right topics without data loss.
I’m already committed to AKS, so please work with native Kubernetes objects and any Azure-specific best practices you rely on. Helm is fine, as are plain manifests—what matters most is that the deployment is repeatable and can be promoted between environments without surprises.
Deliverables I expect:
• A fully automated deployment (Helm chart or equivalent) that spins up a multi-broker Pulsar cluster with BookKeeper, ZooKeeper, and any required proxies on AKS
• Secure networking, TLS enabled, and RBAC configured for topic-level access
• Pulsar topics pre-created or templated for the three data sources mentioned above, each with sensible partitions and retention policies
• Basic monitoring wired into Prometheus and Grafana dashboards so I can track broker health, storage usage, and end-to-end latency
• A short run sheet or README that walks me through scaling a broker, upgrading the chart, and adding a new topic
The work is done when I can run one command, watch the pods come up cleanly, and push sample messages from my IoT simulator, a web app, and a test database connector—all of which should arrive in the right topics without data loss.
Related categories:
Linux
Cloud Computing
Azure
MySQL
Amazon Web Services
Kubernetes
DevOps
Containerization