-
-
Notifications
You must be signed in to change notification settings - Fork 392
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
TLS Cert Signing Error with Second Cluster #1087
Comments
Thanks for reporting. I have identified the problem. |
This should be fixed now. Can you kindly confirm by installing the development version with |
@abiosoft
|
You need to uninstall the stable one first.
|
Awesome. LGTM! Thanks for replying/fixing so quickly. You rock 🚀 |
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [abiosoft/colima](https://github.com/abiosoft/colima) | patch | `v0.7.0` -> `v0.7.1` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>abiosoft/colima (abiosoft/colima)</summary> ### [`v0.7.1`](https://github.com/abiosoft/colima/releases/tag/v0.7.1) [Compare Source](abiosoft/colima@v0.7.0...v0.7.1) #### Highlights This is an incremental release with bug fixes. - Interrupted disk image download will now resume on subsequent `colima start`. - Docker container port mapping to specific host IP addresses is now supported. For more details about v0.70 features, check [v0.70 release notes](https://github.com/abiosoft/colima/releases/tag/v0.7.0). #### Other Fixes - Disk image downloader no longer duplicating downloads. Fixes [#​1098](abiosoft/colima#1098) - Support for binding to host IP address in containers. Fixes [#​492](abiosoft/colima#492) - Ensure proper loading of docker deamon settings on startup. Fixes [#​902](abiosoft/colima#902) - Running multiple Colima profiles with k3s enabled. Fixes [#​1087](abiosoft/colima#1087) #### Commits - k3s: use random port for cluster API by [@​abiosoft](https://github.com/abiosoft) in abiosoft/colima#1088 - k3s: re-use default port for existing instances by [@​abiosoft](https://github.com/abiosoft) in abiosoft/colima#1090 - net: support forwarding to specific host IP addresses by [@​abiosoft](https://github.com/abiosoft) in abiosoft/colima#1091 - core: nested virtualization and other fixes by [@​abiosoft](https://github.com/abiosoft) in abiosoft/colima#1094 - build(deps): bump golang.org/x/term from 0.22.0 to 0.23.0 by [@​dependabot](https://github.com/dependabot) in abiosoft/colima#1095 - fix(docker): apply configuration on first boot by [@​milas](https://github.com/milas) in abiosoft/colima#1097 - core: fix downloader duplicating downloads by [@​abiosoft](https://github.com/abiosoft) in abiosoft/colima#1099 - core: update disk images by [@​abiosoft](https://github.com/abiosoft) in abiosoft/colima#1102 **Full Changelog**: abiosoft/colima@v0.7.0...v0.7.1 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40NDAuNyIsInVwZGF0ZWRJblZlciI6IjM3LjQ0MC43IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiXX0=-->
Description
Starting the first cluster works as expected, however I am now receiving a TLS error getting pods for a second started cluster.
Version
Operating System
Output of
colima status
Reproduction Steps
colima start mirror0 -k --kubernetes-disable=traefik -c 4 -m 8 --network-address
kubectl get pods
result as expectedcolima start mirror1 -k --kubernetes-disable=traefik -c 4 -m 8 --network-address
kubectl config use-context mirror1
kubectl get pods
results inExpected 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.The text was updated successfully, but these errors were encountered: