7 Commits

Include renames

Author	SHA1	Message	Date
Story Crater Bot	3d52eab41d	fix(ci,deps): migrate to .gitea/workflows, update domain to forgejo.riotpiao.com/rock, fix k8s argocd config	2026-08-21 20:14:58 -07:00
Story Crater Bot	52b86ab8e8	feat: queue-operator auto-registers Temporal namespace before creating TemporalWorker ... A Queue's temporal.io/namespace label was trusted as-is -- if the referenced Temporal namespace was never registered (or typo'd), the failure only surfaced as a worker pod silently polling a namespace that doesn't exist. Now reconcileTemporalWorker calls RegisterNamespace (idempotent, ignores AlreadyExists) via a direct WorkflowService gRPC client before creating the TemporalWorker, so namespace and worker always come into existence together. Also grant queue-operator's ClusterRole create/delete on temporalworkers (previously missing, causing forbidden errors on the create-then-delete path).	2026-07-13 13:02:40 -07:00
Story Crater Bot	a584fb4462	fix: don't set cross-namespace owner ref on TemporalWorker ... Queue lives in the sqs namespace while its TemporalWorker is created in the Temporal namespace (KMSVC_TEMPORAL_NAMESPACE), so SetControllerReference always failed with "cross-namespace owner references are disallowed". Drop the owner ref (lifecycle already handled explicitly in reconcileDelete) and move Spec population into the CreateOrUpdate mutate closure so updates to an existing TemporalWorker actually stick. Also commit the generated TemporalWorker CRD and RBAC rules (temporalworkers, deployments) that were previously untracked.	2026-07-13 11:32:04 -07:00
Story Crater Bot	317396e785	feat: add TemporalWorker auto-provisioning from Queue labels ... - Validate temporal namespace and Kubernetes names - Configurable via env vars: KMSVC_TEMPORAL_NAMESPACE, KMSVC_TEMPORAL_WORKER_IMAGE - Set ownerReference for cascade deletion and lifecycle management - Use CreateOrUpdate for spec propagation (idempotent) - Clean up TemporalWorker on Queue deletion	2026-07-11 07:30:13 -07:00
riotpiaole	c7eeed2617	feat: stamp Queue shard status with availability zones ... Resolves each shard topic's replica broker IDs (internal/kafka.Admin. ReplicaBrokerIDs) to the topology.kubernetes.io/zone labels of the nodes hosting those brokers (ZoneLocator), and writes the result into ShardStatus.AvailabilityZones each reconcile. Uses mgr.GetAPIReader() rather than the cached client for the Pod/Node lookups, since the cached client would otherwise require cluster-wide list/watch RBAC on Pods just to serve occasional point Gets.	2026-06-22 17:30:26 -07:00
riotpiaole	9fa5420b22	fix: queue-operator dropped reconcile namespace and overflowed hash-range status ... main.go called Reconcile(ctx, req.Name) without req.Namespace, so the Get against the namespaced Queue CRD always 404'd and was silently swallowed as success -- no shard topics or Redis state were ever created. Separately, ShardStatus.HashRangeStart/End were uint32, but controller-gen maps that to OpenAPI format:int32, whose max (2147483647) is smaller than FullHashRangeEnd (0xFFFFFFFF), so the apiserver rejected every status update with the (misleadingly empty-looking) "must be of type integer with format int32" error. Widened to int64, regenerated the CRD, and synced the chart's bundled copy.	2026-06-22 12:23:23 -07:00
riotpiaole	3ac4083a68	feat(operator): add queue-operator CRD reconciler with shard split/drain ... Reconciles Queue CRs into Kafka topics + Redis shard-map/queue-meta state: creates shard-0 on first reconcile, splits a shard's hash range into two children once its split threshold is crossed, drains and closes a parent shard once its consumer group has fully caught up and its retention window has elapsed, and tears down every shard's topic + Redis state on deletion. Includes the manager entrypoint (cmd/queue-operator) and RBAC.	2026-06-21 17:08:17 -07:00