-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
coredns-1.8.yaml not found #737
Comments
Use helm chart instead.
|
I was able to install
When I try to go to https://storage.googleapis.com/kubernetes-the-hard-way in the browser, I get the following error:
I think the bucket has been accidentally destroyed. Or maybe the permissions are now set incorrectly. Edit: Hack to get workingI took the 1.7.0 yaml file out of the repo (https://github.com/kelseyhightower/kubernetes-the-hard-way/blob/master/deployments/coredns-1.7.0.yaml), updated Note this is all on
|
@hkz-aarvesen didn't know the coredns-1.7.0.yaml was in the repo. it worked to copy it locally and modify the image version and then apply it. appreciate your help! |
coredns-1.8.yaml installs 6 types of resources: ServiceAccount, ClusterRole, ClusterRoleBinding, ConfigMap, Deployment and Service.
With the default installation of helm chart you will have all of these resources, except ServiceAccount, ClusterRole and ClusterRoleBinding. ServiceAccount and roles will only be installed if you specify the
There are no pods because you are trying to select pods with the
You can always use I would say that using the official CoreDNS helm chart is the most correct way to get DNS on the cluster. |
download coredns-1.7.0.yaml locally , and fix image to 1.8.0, then run locally: kubectl apply -f coredns-1.8.0.yaml |
Hey! You can fork the 1.7.0 file to your own repository and change the image version to 1.8.0 and use it as raw content you wont need to ssh and you will be able to perform as the original guide was intended. I have it here: https://github.com/koenry/k8s-hard-way-core-dns-1.8 |
Good! |
See also: there is a ./manifests/ with a coredns-1.10.1.yaml here ... |
Hello, I am following the Kubernetes the Hard Way guide on the master branch. When I apply your manifest, it does not change anything regarding DNS resolution. For example, when I run nslookup google.com in any container in any pod in my Kubernetes cluster, it does not work. Do you have any ideas on what could be the issue? Thank you in advance |
working on the first step of Deploying the DNS Cluster Add-on and tried to do both
kubectl apply -f https://storage.googleapis.com/kubernetes-the-hard-way/coredns-1.8.yaml
and
kubectl apply -f https://storage.googleapis.com/kubernetes-the-hard-way/coredns.yaml
and received
error: unable to read URL "https://storage.googleapis.com/kubernetes-the-hard-way/coredns-1.8.yaml", server reported 404 Not Found, status code=404
The text was updated successfully, but these errors were encountered: