JGillam
commented
8 months ago I'm going to nudge @corysabol on this one since he knows more about what's going on with the k8s labs.
Open double16 opened 8 months ago
JGillam
commented
8 months ago I'm going to nudge @corysabol on this one since he knows more about what's going on with the k8s labs.
corysabol
commented
8 months ago I will take a look later this evening when I'm back near a computer :)
On Sat, Mar 9, 2024, 9:00 AM Jason @.***> wrote:
I'm going to nudge @corysabol https://github.com/corysabol on this one since he knows more about what's going on with the k8s labs.
— Reply to this email directly, view it on GitHub https://github.com/SamuraiWTF/katana/pull/68#issuecomment-1986865099, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDBVFAZNUDSAFY6YRMBVYLYXMIYZAVCNFSM6AAAAABENJFRC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWHA3DKMBZHE . You are receiving this because you were mentioned.Message ID: @.***>
corysabol
commented
8 months ago I suspect the test is failing in the runner because the minikube driver is set to --docker in the k8s-labs setup.sh. The test log shows it exiting the cluster setup here - https://github.com/SamuraiWTF/katana/actions/runs/8207803587/job/22449894918?pr=68#step:6:85
I imagine the test github action is itself a docker container so getting the docker driver to work would take some tweaking most likely. In the samuraivm itself I think there was some hackery I had to do to get the docker driver to work as root. I'd like to find a better solution to this, but I also had a lot of issues when using --driver=none. I should re-investigate this relatively soon. I think the test itself looks fine at a cursory glance though.
double16
commented
8 months ago I don't think the ports are correct. This is running from a VM on my local:
vagrant@vagrant:~$ curl --verbose http://192.168.58.2:31337
* Trying 192.168.58.2:31337...
* connect to 192.168.58.2 port 31337 failed: Connection refused
* Failed to connect to 192.168.58.2 port 31337 after 0 ms: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 192.168.58.2 port 31337 after 0 ms: Connection refused
vagrant@vagrant:~$ curl --verbose http://192.168.58.2:31380
* Trying 192.168.58.2:31380...
* connect to 192.168.58.2 port 31380 failed: Connection refused
* Failed to connect to 192.168.58.2 port 31380 after 2 ms: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 192.168.58.2 port 31380 after 2 ms: Connection refusedss -antup:
vagrant@vagrant:~$ ss -antup
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:*
udp UNCONN 0 0 10.0.2.15%eth0:68 0.0.0.0:*
tcp LISTEN 0 511 0.0.0.0:80 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:*
tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:32768 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:32769 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:32770 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:32771 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:32772 0.0.0.0:*
tcp ESTAB 0 0 10.0.2.15:22 10.0.2.2:54365
tcp LISTEN 0 511 [::]:80 [::]:*
tcp LISTEN 0 128 [::]:22 [::]:*
The test fails because the ports aren't mapped correctly with nginx. I can't readily tell which ports are supposed to be mapped. I had to move the nginx conf to the
startoperation because the cluster IP isn't available until minikube is started.