ignore k8s agents in agent updater #3106
No reviewers
Labels
No labels
1week
2weeks
Failed compliance check
IP cameras
NATS
Possible security concern
Review effort 1/5
Review effort 2/5
Review effort 3/5
Review effort 4/5
Review effort 5/5
UI
aardvark
accessibility
amd64
api
arm64
auth
back-end
bgp
blog
bug
build
checkers
ci-cd
cleanup
cnpg
codex
core
dependencies
device-management
documentation
duplicate
dusk
ebpf
enhancement
eta 1d
eta 1hr
eta 3d
eta 3hr
feature
fieldsurvey
github_actions
go
good first issue
help wanted
invalid
javascript
k8s
log-collector
mapper
mtr
needs-triage
netflow
network-sweep
observability
oracle
otel
plug-in
proton
python
question
reddit
redhat
research
rperf
rperf-checker
rust
sdk
security
serviceradar-agent
serviceradar-agent-gateway
serviceradar-web
serviceradar-web-ng
siem
snmp
sysmon
topology
ubiquiti
wasm
wontfix
zen-engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
carverauto/serviceradar!3106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/3106/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Imported from GitHub pull request.
Original GitHub pull request: #3108
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/3108
Original created: 2026-03-31T06:50:31Z
Original updated: 2026-03-31T15:22:43Z
Original head: carverauto/serviceradar:update/ignore-k8s-agent-updater
Original base: staging
Original merged: 2026-03-31T15:22:40Z by @mfreeman451
IMPORTANT: Please sign the Developer Certificate of Origin
Thank you for your contribution to ServiceRadar. Please note, when contributing, the developer must include
a DCO sign-off statement indicating the DCO acceptance in one commit message. Here
is an example DCO Signed-off-by line in a commit message:
Describe your changes
Issue ticket number and link
Code checklist before requesting a review
Imported GitHub PR review comment.
Original author: @Copilot
Original URL: https://github.com/carverauto/serviceradar/pull/3108#discussion_r3013895750
Original created: 2026-03-31T06:54:42Z
Original path: go/pkg/agent/push_loop.go
Original line: 3066
The doc comment here no longer matches the following function: it says
getAgentCapabilitiesbut it now documentsdeploymentHelloLabels(). This is misleading and can trip comment-based tooling; update/move the comment so it describes the correct function(s).Imported GitHub PR review comment.
Original author: @Copilot
Original URL: https://github.com/carverauto/serviceradar/pull/3108#discussion_r3013895781
Original created: 2026-03-31T06:54:43Z
Original path: go/pkg/agent/push_loop.go
Original line: 3079
detectDeploymentType/isKubernetesRuntime/isDockerRuntimeduplicate the existing deployment detection logic ingo/pkg/edgeonboarding/deployment.go(seeisKubernetes()/isDocker()around lines 72-108). Consider extracting this into a shared helper package to avoid divergence (e.g., future detection fixes need to be made in two places).Imported GitHub PR review comment.
Original author: @Copilot
Original URL: https://github.com/carverauto/serviceradar/pull/3108#discussion_r3013895800
Original created: 2026-03-31T06:54:43Z
Original path: elixir/web-ng/lib/serviceradar_web_ng_web/live/settings/agents_live/releases.ex
Original line: 1481
Kubernetes-managed agents are filtered out for the default (connected) cohort, but they can still be targeted via the "custom" cohort path (agent IDs are looked up and treated as compatible based only on os/arch). If Kubernetes-managed agents should always be excluded from rollouts, apply
kubernetes_managed_agent?/1filtering to the custom cohort selection/compatibility path as well (or filterpreview.compatible_agent_idsbefore creating the rollout).