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
We use Tekton and its CLI for some CI/CD: it works fine for us on GKE, EKS.
We'd like also to use it now on dev laptops with MicroK8s
But, 'microk8s --help' (see below) tends to demonstrate that microk8s wraps standard K8s CLI : kubectl, istioctl, etc.
Does it mean that I have no chance to get standard tkn cli working on MacOs?
Unsuccessful trials until now in using 'microk8s kubectl config view --raw > "kube-config"' and using the generated kube-config-file as input to the --kubeconfig of tkn cli.
Thanks in advance for your feedback.
Didier
The text was updated successfully, but these errors were encountered:
The API server is listening on port 16443 on all interfaces so on a Mac you will need to change the endpoint IP you get with microk8s kubectl config view --raw to the IP of the VM running MicroK8s. Alternatively you can use microk8s config to get the kubeconfig file.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi there,
We use Tekton and its CLI for some CI/CD: it works fine for us on GKE, EKS.
We'd like also to use it now on dev laptops with MicroK8s
But, 'microk8s --help' (see below) tends to demonstrate that microk8s wraps standard K8s CLI : kubectl, istioctl, etc.
Does it mean that I have no chance to get standard tkn cli working on MacOs?
Unsuccessful trials until now in using 'microk8s kubectl config view --raw > "kube-config"' and using the generated kube-config-file as input to the --kubeconfig of tkn cli.
Thanks in advance for your feedback.
Didier
The text was updated successfully, but these errors were encountered: