Lab 3.1. Install Kubernetes; Calico URL 404

mitchell.roe

In "Lab 3.1. Install Kubernetes", the PDF provides a link to calico.yml as the following:

root@cp: ~# wget https://docs.projectcalico.org/manifests/calico.yaml

This URL results in a 404. Upon investigation into Calico installation, it appears the installation paradigm has changed somewhat, and I'm not sure how best to continue.

chrispokorni

Hi @mitchell.roe,

I just verified running the wget command and pasting the URL in a browser and it successfully downloaded the file. Is there a firewall you may have in place to block access to the site?

Regards,
-Chris

mitchell.roe

Hm, interesting. I tried it successively two days in a row without success; now it seems to work. Oh well. Thank you!

marc.moline

Hello,

I have the same issue:

`
root@controlplane:~# wget https://docs.projectcalico.org/manifests/calico.yaml
--2023-02-08 14:53:35-- https://docs.projectcalico.org/manifests/calico.yaml
Resolving docs.projectcalico.org (docs.projectcalico.org)... 35.231.208.25, 54.84.236.175, 2600:1f18:2489:8200::c8, ...
Connecting to docs.projectcalico.org (docs.projectcalico.org)|35.231.208.25|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://docs.tigera.io/calico/manifests/calico.yaml [following]
--2023-02-08 14:53:35-- https://docs.tigera.io/calico/manifests/calico.yaml
Resolving docs.tigera.io (docs.tigera.io)... 34.148.97.127, 34.148.19.16, 2600:1f18:2489:8202::c8, ...
Connecting to docs.tigera.io (docs.tigera.io)|34.148.97.127|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-02-08 14:53:35 ERROR 404: Not Found.

`

Access via web browser:

How you install Calico?

Thanks

fazlur.khan

Hello @marc.moline

Use the below command

kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml

marc.moline

@fazlur.khan said:
Hello @marc.moline

Use the below command

kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml

It works! Thanks fazlur.khan

kirankoduru

I am having the same issue. I even tried the new link. I still get connection refused
root@master:~# kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml
The connection to the server localhost:8080 was refused - did you specify the right host or port?
root@master:~#

kirankoduru

root@master:~# wget https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml
--2023-02-14 23:17:51-- https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.111.133, 185.199.110.133, 185.199.109.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.111.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 238089 (233K) [text/plain]
Saving to: ‘calico.yaml.1’

calico.yaml.1 100%[================================================================>] 232.51K --.-KB/s in 0.02s

2023-02-14 23:17:52 (13.2 MB/s) - ‘calico.yaml.1’ saved [238089/238089]

root@master:~# kubectl apply -f calico.yaml
The connection to the server localhost:8080 was refused - did you specify the right host or port?
root@master:~#

kirankoduru

I need to run as regular user where .kube is created. issue resolved.

edsonz

I had a similar problem and ran:
wget https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml

And it worked.

rajapandian

After running on non root user as well same error..

k8s@k8s-VirtualBox:~$ sudo kubectl apply -f calico.yaml
The connection to the server localhost:8080 was refused - did you specify the right host or port?

chrispokorni

Hi @rajapandian,

Perhaps following the latest lab guide release may help to successfully complete the installation lab exercise.
In addition please ensure that each VirtualBox VM is adequate in size (2 CPU cores, 8 GB RAM, 20 GB disk), one bridged network interface per VM, promiscuous mode enabled to allow all inbound traffic, running Ubuntu 20.04 LTS.

Regards,
-Chris