wide-garage-9465
02/02/2023, 1:19 PMpolite-engineer-55788
02/02/2023, 6:58 PMrancher/k3d:x-dind
image ? I want to start a k3d cluster without mounting host docker sockpolite-engineer-55788
02/03/2023, 7:49 AMpolite-engineer-55788
02/05/2023, 10:11 AMfuture-vase-71145
02/10/2023, 7:01 PMrewrite name regex (.*).<http://local.example.com|local.example.com> public-nginx-ingress-nginx-controller.default.svc.cluster.local
. (Everything else was kept default.)
It appears from my reading of github issues that modifying the .:53
block in coredns is no longer supported? Any pointers on how to handle this? For now I'm doing this, but it feels... wrong.
kubectl -n kube-system patch configmap coredns --patch-file "coredns-patch.yaml"
kubectl wait --for=condition=Ready=true pod -l k8s-app=kube-dns -n kube-system
kubectl -n kube-system rollout restart deployment coredns
handsome-salesclerk-54324
02/12/2023, 8:28 PMchilly-toddler-80124
02/14/2023, 2:52 PMhttps://static.wixstatic.com/media/6f3936_2ce31d23816f43fb995912c961149785~mv2.png/v1/f[…]1,enc_auto/6f3936_2ce31d23816f43fb995912c961149785~mv2.png▾
chilly-toddler-80124
02/14/2023, 7:54 PMbulky-fish-74730
02/21/2023, 10:43 AMkubectl cluster-info
I get a couple of messages like memcache.go:255] couldn't get resource list for <http://metrics.k8s.io/v1beta1|metrics.k8s.io/v1beta1>: the server is currently unable to handle the request
victorious-mouse-54341
02/21/2023, 6:07 PMk3d cluster create doctorconsul --network doctorconsul_wan --api-port 127.0.0.1:6443 --k3s-arg="--disable=traefik@server:0" -p "8502:443@loadbalancer"
This works pretty much exactly as expected. It drops into my "doctorconsul_wan" network that is already built in docker compose.
The problem I'm having is that the external-IP used is dynamically the first available in that network (192.168.1.7 in my case) and I need to statically assign it (to 192.169.1.10). I'm not seeing a parameter to do so. I have a feeling that perhaps I have to pass a kube native config param through via --kubeconfig-update-default
, but frankly I don't know nearly enough about kube to figure that out.
Any help is much appreciated. Thanks!victorious-mouse-54341
02/21/2023, 9:51 PMk3d cluster create doctorconsul --network doctorconsul_wan \
--api-port 127.0.0.1:6443 \
-p "8502:443@loadbalancer" \
--k3s-arg="--disable=traefik@server:0" \
--k3s-arg="--node-ip=192.169.7.10@server:0" \
--k3s-arg="-node-external-ip=192.169.7.10@server:0"
The only server node does correctly have these IPs
Addresses: ││ InternalIP: 192.169.7.10 ││ ExternalIP: 192.169.7.10 ││ Hostname: k3d-doctorconsul-server-0
But coreDNS won't come up.
[INFO] plugin/ready: Still waiting on: "kubernetes"
[WARNING] plugin/kubernetes: Kubernetes API connection failure: Get "<https://10.43.0.1:443/version>": dial tcp 10.43.0.1:443: connect: no route to host
^^^ These are just repeatedly spammed. Anyone know why? I'm way out of my kube league and I'm just trying to get K3d to accept a static IP instead of choosing the first avail dynamically.
Thanksadamant-garage-54388
02/22/2023, 3:37 AMrough-farmer-49135
02/22/2023, 7:32 PMrough-farmer-49135
02/24/2023, 2:53 AMaloof-oxygen-4191
02/27/2023, 8:24 AM--k3s-server-arg '--kube-apiserver-arg=feature-gates=CPUManager=true --cpu-manager-policy=static'
maybe ?fancy-river-86403
02/27/2023, 1:50 PMrefined-memory-51625
03/02/2023, 4:34 PM--horizontal-pod-autoscaler-sync-period
, what's the proper way to do this?mammoth-laptop-63191
03/04/2023, 6:15 PMglamorous-needle-18908
03/05/2023, 10:18 AMk3d cluster create ingress --servers 1 --agents 3 -p "80:80@loadbalancer" -p "443:443@loadbalancer"
, I have attempted several approaches but without success. Every Service is working correctly and I can access the port by forwarding the pod or the service only when trying to access the ingress I get a 404 error. This is the case for everything exposed through the ingress.
I would appreciate any input or suggestions on how to resolve this issue. 🙂handsome-salesclerk-54324
03/05/2023, 3:32 PMk3d cluster create westie --api-port 127.0.0.1:6445 --servers 3 --agents 2 --volume '/home/mwoodpatrick/projects/git/westie-dev-pnpm:/westie-dev-pnpm@agent[*]' --port '8
080:80@loadbalancer'
I'm getting the error below, what am I doing wrong:
FATA[0000] failed to filter nodes for volume mapping '/home/mwoodpatrick/projects/git/westie-dev-pnpm:/westie-dev-pnpm': Failed to parse node filters: invalid format or empty subset in 'agent[*]'
aloof-oxygen-4191
03/06/2023, 8:11 AMerror dialing load balancer servers: all servers failed
even that disableLoadbalancer: true
(not sure related to the error ?)
my yaml is (if some values are needed will supply)
<https://termbin.com/sw7km6>
trying to make it more minimal meanwhile
CLI command that works
k3d cluster create $CLUSTER_NAME --registry-use $REGISTRY_NAME \
--api-port $KUBERNETES_SERVICE_HOST:$KUBERNETES_SERVICE_PORT \
--servers=$KUBEVIRT_NUM_SERVERS \
--agents=$KUBEVIRT_NUM_AGENTS \
--k3s-arg "--disable=traefik@server:0" \
--no-lb \
--k3s-arg "--flannel-backend=none@server:*" \
--k3s-arg "--kubelet-arg=cpu-manager-policy=static@agent:*" \
--k3s-arg "--kubelet-arg=kube-reserved=cpu=500m@agent:*" \
--k3s-arg "--kubelet-arg=system-reserved=cpu=500m@agent:*" \
--volume "$(pwd)/cluster-up/cluster/k3d/manifests/calico.yaml:/var/lib/rancher/k3s/server/manifests/calico.yaml@server:0" \
-v /dev/vfio:/dev/vfio@agent:* \
-v /lib/modules:/lib/modules@agent:* \
-v ${id1}:/etc/machine-id@server:0 \
-v ${id2}:/etc/machine-id@agent:0 \
-v ${id3}:/etc/machine-id@agent:1
Thankshandsome-salesclerk-54324
03/11/2023, 12:59 PMexport KUBECONFIG=/home/mwoodpatrick/.k3d/kubeconfig-local-k8s.yaml
and run
kubectl version
I get
Client Version: <http://version.Info|version.Info>{Major:"1", Minor:"20", GitVersion:"v1.20.15", GitCommit:"8f1e5bf0b9729a899b8df86249b56e2c74aebc55", GitTreeState:"clean", BuildDate:"2022-01-20T02:28:14Z", GoVersion:"go1.15.15", Compiler:"gc", Platform:"linux/amd64"}
Unable to connect to the server: context deadline exceeded
docker ps shows that the server and load balancer are running and I can use docker to exec into the server
If I run
k3s kubectl version
I get:
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: <http://version.Info|version.Info>{Major:"1", Minor:"25", GitVersion:"v1.25.6+k3s1", GitCommit:"9176e03c5788e467420376d10a1da2b6de6ff31f", GitTreeState:"clean", BuildDate:"2023-01-26T00:47:47Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
error: Get "<https://0.0.0.0:34117/version?timeout=32s>": context deadline exceeded - error from a previous attempt: EOF
Any suggestions on the best way to debug what the issue is?cold-ambulance-6848
03/13/2023, 5:12 PMhandsome-salesclerk-54324
03/19/2023, 10:23 AMbright-pizza-38404
03/19/2023, 12:55 PMaloof-oxygen-4191
03/21/2023, 3:41 PMflat-car-15181
03/21/2023, 9:40 PMflat-car-15181
03/21/2023, 9:41 PMflat-car-15181
03/21/2023, 9:42 PMflat-car-15181
03/21/2023, 9:42 PMflat-car-15181
03/21/2023, 9:42 PM