adventurous-judge-82125
01/10/2023, 3:49 PM--network host
and checked that the resolv.conf has the correct search domains. The host machine can reach the domain. The pod cannot and but if it can ping the ipadventurous-judge-82125
01/10/2023, 3:50 PMpolite-engineer-55788
01/17/2023, 6:06 AMpolite-engineer-55788
01/17/2023, 6:06 AM+
and -
variants ;Dcreamy-pencil-82913
01/17/2023, 6:24 AMcreamy-pencil-82913
01/17/2023, 6:25 AMpolite-engineer-55788
01/17/2023, 7:09 AMapiVersion: <http://k3d.io/v1alpha4|k3d.io/v1alpha4>
kind: Simple
metadata:
name: gitops-quickstart
servers: 1
agents: 1
image: rancher/k3s:v1.24.4-k3s1
network: gitops-quickstart
ports:
# Drone CI
- port: 0.0.0.0:30980:30980
nodeFilters:
- loadbalancer
# Gitea
- port: 0.0.0.0:30950:30950
nodeFilters:
- loadbalancer
# Argo CD
- port: 0.0.0.0:30080:30080
nodeFilters:
- loadbalancer
salmon-morning-84088
01/26/2023, 11:21 AMk3d
. Can I override that somehow?
When I create a cluster and registry in one go, I can set any name: k3d cluster create --registry-create foo:127.0.0.1:1234
But when creating the registry alone, I always get the k3d
prefix: k3d registry create foo --port 127.0.0.1:1234
bland-area-30120
01/27/2023, 9:01 AMbest-carpenter-95408
01/30/2023, 4:04 PMPermission "artifactregistry.repositories.downloadArtifacts" denied on resource
. A manual docker pull works fine so I’m assuming k3d can’t use the gcloud credential helper.quiet-dentist-43250
01/31/2023, 4:25 PMwide-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. 🙂