Commit 3b8ec740 authored by Brad Davidson's avatar Brad Davidson Committed by Brad Davidson

Update disables list when building with no_stage

The --disable/--no-deploy flags actually turn off some built-in controllers, in addition to preventing manifests from getting loaded. Make it clear which controllers can still be disabled even when the packaged components are ommited by the no_stage build tag. Signed-off-by: 's avatarBrad Davidson <brad.davidson@rancher.com>
parent ea916030
// +build no_stage
package cmds
const (
// The coredns and servicelb controllers can still be disabled, even if their manifests
// are missing. Same with CloudController/ccm.
DisableItems = "coredns, servicelb"
)
......@@ -8,8 +8,6 @@ import (
)
const (
DisableItems = "coredns, servicelb, traefik, local-storage, metrics-server"
defaultSnapshotRentention = 5
defaultSnapshotIntervalHours = 12
)
......
// +build !no_stage
package cmds
const (
// coredns and servicelb run controllers that are turned off when their manifests are disabled.
// The k3s CloudController also has a bundled manifest and can be disabled via the
// --disable-cloud-controller flag or --disable=ccm, but the latter method is not documented.
DisableItems = "coredns, servicelb, traefik, local-storage, metrics-server"
)
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment