issue (bug_risk): Importing app packages into central causes their init() side effects (like memlimit.SetMemoryLimit) to run in the central process as well.

Some of these .../app packages (e.g. compliance, admission-control, k8s sensor, roxagent) call memlimit.SetMemoryLimit() or other side-effectful logic in init(). With these imports now always pulled into the central binary, that logic also runs when central starts, not just for the symlinked binaries. To avoid unintended impact on central’s own resource configuration, consider moving such calls out of init() and into the respective Run() paths so they only execute when that app is actually invoked.

⚠️ Potential issue | 🟡 Minor

Fix import formatting: pipeline failure due to extra blank line.

The CI style check failed because of an extra blank line before the BusyBox imports block.

 	pkgVersion "github.com/stackrox/rox/pkg/version"
-
 	// BusyBox-style consolidation - import app packages
 	complianceapp "github.com/stackrox/rox/compliance/cmd/compliance/app"

Verify each finding against the current code and only fix it if needed.

In `@central/main.go` around lines 234 - 243, Remove the extra blank line
preceding the BusyBox-style consolidation import block so the import comment and
the grouped imports are contiguous; locate the import block that lists
complianceapp, roxagentapp, configcontrollerapp, migratorapp,
admissioncontrolapp, kubernetessensorapp, and sensorupgraderapp and delete the
stray empty line above the comment so the style check passes.

suggestion (bug_risk): Defaulting to central on unknown binary names may hide misconfigurations.

Because any unexpected binaryName falls through to Main(), misnamed symlinks or typos will silently run central instead of failing fast. It would be safer to log a clear warning or exit non‑zero when the name is not recognized, so configuration issues are detected rather than masked.

Suggested implementation:

func main() {
	// BusyBox-style dispatcher: check how we were called
	binaryName := filepath.Base(os.Args[0])

	switch binaryName {
	case "central":
		Main()
	case "migrator":
		migratorMain()
	case "compliance":
		complianceMain()
	case "kubernetes-sensor":
		kubernetesSensorMain()
	case "sensor-upgrader":
		sensorUpgraderMain()
	case "admission-control":
		admissionControlMain()
	case "config-controller":
		configControllerMain()
	case "roxagent":
		roxagentMain()
	default:
		log.Errorf("unknown binary name %q; expected one of [central, migrator, compliance, kubernetes-sensor, sensor-upgrader, admission-control, config-controller, roxagent]", binaryName)
		os.Exit(1)
	}
}

You will also need to:

1. Ensure the import block at the top of central/main.go includes:
   • "os"
   • "path/filepath"
2. Confirm that log is a logger with Errorf available (e.g. from your existing logging package). If not, adjust the logging call to match your logging API.
3. Make sure functions like Main, kubernetesSensorMain, sensorUpgraderMain, and admissionControlMain are defined in this file or imported from the appropriate packages.