--k3s-arg=--disable=... does nothing but --kubernetes-disable still works
- Dominant language
- Go
- Stars
- 30.8k
- Forks
- 613
- PR merge metrics
- No merged PRs in 30d
Description
### Description
Starting colima with custom --k3s-arg doesn't work.
Using `colima start --help` example:
```
colima start --kubernetes --k3s-arg=--disable=coredns,servicelb,traefik,local-storage,metrics-server
```
colima installs traefik, servicelb, local-path-provisioner (local-storage), metrics-server but does NOT install coredns.
k9s screenshot
Looking at the source, it looks like `--kubernetes-disable` is still available but hidden. If I use that version, then colima does the right thing
ex:
```
colima start --kubernetes --kubernetes-disable=coredns --kubernetes-disable=servicelb --kubernetes-disable=traefik --kubernetes-disa
ble=local-storage --kubernetes-disable=metrics-server
```
k9s screenshot
### Version
```
❯ colima version && limactl --version
colima version 0.8.1
git commit: 96598cc5b64e5e9e1e64891642b91edc8ac49d16
limactl version 1.0.2
```
### Operating System
- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [X] Apple Silicon >= 14 (Sonoma)
- [ ] Linux
### Output of `colima status`
_No response_
### Reproduction Steps
1.
2.
3.
### Expected behaviour
```colima start --kubernetes --k3s-arg=--disable=coredns,servicelb,traefik,local-storage,metrics-server``` should actually disable the specified components.
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.