You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected options.kubeconfig.updateDefaultKubeconfig and options.kubeconfig.switchCurrentContext to be declared and defined in resulting json object payload, regardless of boolean value.
Interestingly, when either field is defined as true
Running k3d binary on old dev imac with DOCKER_HOST pointing to dedicated host on lan.
$ echo$DOCKER_HOST
tcp://lab1:2375
$ uname -a
Darwin imac.lan 17.7.0 Darwin Kernel Version 17.7.0: Fri Oct 30 13:34:27 PDT 2020; root:xnu-4570.71.82.8~1/RELEASE_X86_64 x86_64 i386 Darwin
What did you do
Given the following config
And using
k3d config migrate ./config.yaml
, in order to validate, sanity-check, etc, config during orchestration workflowWhat did you expect to happen
I expected
options.kubeconfig.updateDefaultKubeconfig
andoptions.kubeconfig.switchCurrentContext
to be declared and defined in resulting json object payload, regardless of boolean value.Interestingly, when either field is defined as true
They make the cut
Which OS & Architecture
Running k3d binary on old dev imac with
DOCKER_HOST
pointing to dedicated host on lan.Dedicated host runtime
$ dist/bin/k3d runtime-info arch: x86_64 cgroupdriver: systemd cgroupversion: "2" endpoint: /var/run/docker.sock filesystem: extfs infoname: lab1 name: docker os: Ubuntu 24.04 LTS ostype: linux version: 27.1.1
Which version of
k3d
Which version of docker
Outside of the above, I've had no issues to speak of, which is to say good product guys and thank you for your efforts.
The text was updated successfully, but these errors were encountered: