bug: flag(start up parameter) include problem

[magicwang-cn]

currently, the startup parameters does not include flag.CommandLine, like this which is just set to flag's CommandLine, not in cmd's Flags. so when we start controller-manager with --kubeconfig or --master, there will be the problem as follows:

Error: unknown flag: --kubeconfig
Usage:
  controller-manager [flags]

Flags:
      --cluster-available-delay duration     Time to wait before reconciling on a healthy cluster. (default 20s)
      --cluster-monitor-period duration      How often to monitor the cluster health (default 40s)
      --cluster-unavailable-delay duration   Time to wait before giving up on an unhealthy cluster. (default 1m0s)
      --feature-gates mapStringBool          A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:
                                             AllAlpha=true|false (ALPHA - default=false)
                                             CrossClusterServiceDiscovery=true|false (ALPHA - default=true)
                                             FederatedIngress=true|false (ALPHA - default=true)
                                             PushReconciler=true|false (ALPHA - default=true)
                                             SchedulerPreferences=true|false (ALPHA - default=true)
      --federation-namespace string          The namespace the federation control plane is deployed in. (default "federation-system")
  -h, --help                                 help for controller-manager
      --install-crds                         install the CRDs used by the controller as part of startup (default true)
      --install-resources-dir string         install the resources by the controller
      --limited-scope                        Whether the federation namespace will be the only target for federation.
      --log-flush-frequency duration         Maximum number of seconds between log flushes (default 5s)
      --registry-namespace string            The cluster registry namespace. (default "kube-multicluster-public")
      --version                              Prints the Version info of controller-manager

unknown flag: --kubeconfig
root@SZV1000139235:/var/paas/workspace/src/github.com/kubernetes-sigs/federation-v2/cmd/controller-manager#

[magicwang-cn]

/kind bug

[marun]

I'm curious how you discovered this problem. Do you have a use case that suggest running the controller manager outside of a cluster?

[magicwang-cn]

haha... yeah. we have deployed the federated controller plane out side of the k8s cluster

[magicwang-cn]

/close