adventurous-judge-8212501/10/2023, 3:49 PM
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 ip
adventurous-judge-8212501/10/2023, 3:50 PM
polite-engineer-5578801/17/2023, 6:06 AM
polite-engineer-5578801/17/2023, 6:06 AM
creamy-pencil-8291301/17/2023, 6:24 AM
creamy-pencil-8291301/17/2023, 6:25 AM
polite-engineer-5578801/17/2023, 7:09 AM
apiVersion: <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-8408801/26/2023, 11:21 AM
. Can I override that somehow? When I create a cluster and registry in one go, I can set any name:
But when creating the registry alone, I always get the
k3d cluster create --registry-create foo:127.0.0.1:1234
k3d registry create foo --port 127.0.0.1:1234
bland-area-3012001/27/2023, 9:01 AM
best-carpenter-9540801/30/2023, 4:04 PM
. A manual docker pull works fine so I’m assuming k3d can’t use the gcloud credential helper.
Permission "artifactregistry.repositories.downloadArtifacts" denied on resource
quiet-dentist-4325001/31/2023, 4:25 PM
polite-engineer-5578802/02/2023, 6:58 PM
image ? I want to start a k3d cluster without mounting host docker sock
future-vase-7114502/10/2023, 7:01 PM
. (Everything else was kept default.) It appears from my reading of github issues that modifying the
rewrite name regex (.*).<http://local.example.com|local.example.com> public-nginx-ingress-nginx-controller.default.svc.cluster.local
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-5432402/12/2023, 8:28 PM
chilly-toddler-8012402/14/2023, 2:52 PM
chilly-toddler-8012402/14/2023, 7:54 PM
bulky-fish-7473002/21/2023, 10:43 AM
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-5434102/21/2023, 6:07 PM
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 220.127.116.11). 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
k3d cluster create doctorconsul --network doctorconsul_wan --api-port 127.0.0.1:6443 --k3s-arg="--disable=traefik@server:0" -p "8502:443@loadbalancer"
, but frankly I don't know nearly enough about kube to figure that out. Any help is much appreciated. Thanks!
victorious-mouse-5434102/21/2023, 9:51 PM
The only server node does correctly have these IPs
k3d 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=18.104.22.168@server:0" \ --k3s-arg="-node-external-ip=22.214.171.124@server:0"
But coreDNS won't come up.
Addresses: ││ InternalIP: 126.96.36.199 ││ ExternalIP: 188.8.131.52 ││ Hostname: k3d-doctorconsul-server-0
^^^ 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. Thanks
[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
adamant-garage-5438802/22/2023, 3:37 AM
rough-farmer-4913502/22/2023, 7:32 PM
rough-farmer-4913502/24/2023, 2:53 AM
aloof-oxygen-419102/27/2023, 8:24 AM
--k3s-server-arg '--kube-apiserver-arg=feature-gates=CPUManager=true --cpu-manager-policy=static'
fancy-river-8640302/27/2023, 1:50 PM
refined-memory-5162503/02/2023, 4:34 PM
, what's the proper way to do this?
mammoth-laptop-6319103/04/2023, 6:15 PM
glamorous-needle-1890803/05/2023, 10:18 AM
, 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. 🙂
k3d cluster create ingress --servers 1 --agents 3 -p "80:80@loadbalancer" -p "443:443@loadbalancer"