[Documentation] Remove mention of --disable-agent flag #891
Comments
davidnuzik
added
the
kind/documentation
This was referenced Oct 15, 2019
|
Resolved in rancher/docs#1886 |
catherineluse
pushed a commit
to catherineluse/docs
that referenced
this issue
Nov 19, 2019
- Add children to "Installation Options" covering Node Requirements, Single Server Install, and HA install (Experimental) - Make some small tweaks as needed to hide "--disable-agent" as per k3s-io/k3s#891 - Make some miscellaneous tweaks such as to hide "--storage-backend" as this is no longer used and other changes as recommended in a recent internal meeting
catherineluse
pushed a commit
to catherineluse/docs
that referenced
this issue
Nov 23, 2019
- Add children to "Installation Options" covering Node Requirements, Single Server Install, and HA install (Experimental) - Make some small tweaks as needed to hide "--disable-agent" as per k3s-io/k3s#891 - Make some miscellaneous tweaks such as to hide "--storage-backend" as this is no longer used and other changes as recommended in a recent internal meeting
zodiac1214
pushed a commit
to zodiac1214/kcap
that referenced
this issue
Dec 14, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are going to hide the --disable-agent flag from the cli. It has caused confusion for GA and some of the community. The agent should typically be running on master nodes. If the agent is not running then the kubelet is not running and you cannot list the node (i.e. with
kubectl get nodes) or otherwise interface with it with kubectl.We should move it to any developer docs if necessary.
Hide in CLI issue: #890
The text was updated successfully, but these errors were encountered: