-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing kubeadm #46366
Comments
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/language en |
page related to the issue: https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ |
confirm RELEASE_VERSION has been set |
/triage needs-information |
As per the doc RELEASE_VERSION is "v0.16.2", if you replace the value in the url, you can get the config details. So there is no issue in the provided URL. |
There is also DOWNLOAD_DIR in that command. So make sure you do something like: export RELEASE_VERSION="v0.16.2"
export DOWNLOAD_DIR="./"
curl -sSL "https://raw.githubusercontent.com/kubernetes/release/${RELEASE_VERSION}/cmd/krel/templates/latest/kubeadm/10-kubeadm.conf" | \
sed "s:/usr/bin:${DOWNLOAD_DIR}:g" | \
sudo tee /usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf |
/kind support |
@neolit123: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
curl -sSL "https://raw.githubusercontent.com/kubernetes/release/${RELEASE_VERSION}/cmd/krel/templates/latest/kubeadm/10-kubeadm.conf" | sed "s:/usr/bin:${DOWNLOAD_DIR}:g" | sudo tee /usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf
10-kubeadm.conf dose not exist. Is there any other address that can be accessed
The text was updated successfully, but these errors were encountered: