connect

const (
	DefaultNamespace   = "burrow"
	DefaultService     = "burrowd"
	DefaultPort        = 8080
	DefaultTokenSecret = "burrowd-api-token"
	DefaultTokenKey    = "token"
	// DefaultAddonNamespace is where `install` provisions Burrow's curated backing services
	// (logs, metrics) and their collectors — separate from both the control-plane namespace
	// (which holds credentials) and the app namespace (user workloads), so add-ons don't
	// clutter apps and stay out of the credential blast radius (ADR-0025).
	DefaultAddonNamespace = "burrow-addons"
	// DefaultAppNamespace is where `install` deploys apps by default: a dedicated namespace
	// rather than the cluster's shared `default`, so burrowd's namespace-scoped Secrets grant
	// (ADR-0029) stays isolated to Burrow's own app workloads. An operator may still choose
	// `--app-namespace default` explicitly.
	DefaultAppNamespace = "burrow-apps"
	// DefaultBuildNamespace is the dedicated namespace `install` provisions for the in-cluster build
	// (ADR-0053, issue #278): each build runs as a Job here, isolated from both the app namespace (so
	// build steps cannot reach a running app's Secrets) and the control-plane namespace (so they
	// cannot reach burrowd's credentials or database). install grants burrowd a namespaced Role here;
	// burrowd never creates the namespace itself (least privilege).
	DefaultBuildNamespace = "burrow-builds"

	// DefaultRegistryService is the in-cluster Service name of the optional lightweight registry
	// `burrow cluster registry install` deploys (Zot, ADR-0053 §5). It is the zero-config default
	// push target for the in-cluster build — a registry that happens to be local; external
	// registries remain fully supported.
	DefaultRegistryService = "burrow-registry"
	// DefaultRegistryPort is the port the in-cluster registry serves on (Zot's default).
	DefaultRegistryPort = 5000
)

const ProbeTimeout = 5 * time.Second