Closed
Description
Description
Starting the first cluster works as expected, however I am now receiving a TLS error getting pods for a second started cluster.
Version
colima version 0.7.0
git commit: 4b14e8a9993b17d2e6f5071fd9059513111cd365
limactl version 0.22.0
qemu-img version 9.0.2
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers
Operating System
- macOS Intel <= 13 (Ventura)
- macOS Intel >= 14 (Sonoma)
- Apple Silicon <= 13 (Ventura)
- Apple Silicon >= 14 (Sonoma)
- Linux
Output of colima status
INFO[0000] colima [profile=mirror0] is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] address: 192.168.106.2
INFO[0000] socket: unix:///Users/richardautry/.colima/mirror0/docker.sock
INFO[0000] kubernetes: enabled
Reproduction Steps
colima start mirror0 -k --kubernetes-disable=traefik -c 4 -m 8 --network-addresskubectl get podsresult as expectedcolima start mirror1 -k --kubernetes-disable=traefik -c 4 -m 8 --network-addresskubectl config use-context mirror1kubectl get podsresults in
Unable to connect to the server: tls: failed to verify certificate: x509: certificate signed by unknown authority
Expected behaviour
You should be able to get pods status, logs, etc using kubectl on the second cluster.
Additional context
Recently upgraded to colima 0.7.0, but this multi-cluster test was working previously.