alcounit/browser-service repository overview

⁠Browser Service

Browser Service is an HTTP API and event streaming layer for the Selenosis ecosystem. It provides a REST interface and real-time events on top of the Browser and BrowserConfig resources managed by browser-controller.

This service does not create Pods directly. Instead, it operates as a client-facing facade over Kubernetes Browser and BrowserConfig CRDs.

---

⁠Overview

• Browser Service exposes REST and event APIs for Browser and BrowserConfig resources.
• browser-controller is responsible for reconciliation and Pod lifecycle.
• Browser / BrowserConfig CRDs are the shared contract between the service and the controller.

The service watches these resources and streams lifecycle events to clients over Server-Sent Events (SSE).

---

⁠Responsibilities

• Expose an HTTP API to create, read, list, and delete Browser and BrowserConfig resources
• Stream lifecycle events (ADDED / MODIFIED / DELETED) via SSE, with optional per-name filtering
• Provide read-only access to Browser.status and configuration state
• Ship a generated Go client with a typed event stream (pkg/client)
• Expose a /healthz endpoint
• Act as a thin abstraction over Kubernetes APIs (reads from informer cache, writes through the typed clientset)

---

⁠Dependency on browser-controller

Browser Service depends on browser-controller for:

• Browser and BrowserConfig CRD definitions
• Generated clientsets, informers, and listers
• Actual browser Pod creation and lifecycle management

The service assumes that:

• CRDs are already installed
• browser-controller is running in the cluster

Browser Service source code: https://github.com/alcounit/browser-service ⁠