creamy-autumn-87994
05/10/2023, 1:12 AMdry-dawn-97788
05/11/2023, 5:46 PMcert-manager
, or more specifically when I define ClusterIssuer
which in turn trigger the webhook cert-manager-webhook
.
As it is the API server that want to connect to the webhook, it needs two things:
• Be able to resolve the DNS address of the URL https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s - for which it needs configuration and reachability to the CoreDNS service.
• Then it needs to be able to reach the service endpoint as well.
Neither of these two works.
What puzzles me is that the API server runs as a host-networked pod, and therefore lacks the DNS config needed, it just has config that points to the external name server (e.g. as if the ClusterFirstWithHostNet setting was not set on the pod). Secondly I do not known how to debug the issue with not being able to reach the service (must be some kind of iptables misconfiguration?).
All help / ideas are welcome! Thanks!hundreds-evening-84071
05/11/2023, 8:59 PMcloud-provider-name: external
However, when I do kubectl get nodes -o wide
, on one cluster I see both Internal-IP and External-IP populated (in this case both are same which is expected).
But on second cluster, I have Internal-IP populated but for External-IP it shows <none>...
I am trying to figure out why is this different?adamant-kite-43734
05/12/2023, 10:35 AMquiet-potato-9276
05/12/2023, 10:36 AMno route to host
error - can curl that ip on all my nodes (including master). I thought it might have been SELinux so I disabled that but still the same issue. I've attached my cluster.yaml and some logs.white-address-50409
05/12/2023, 11:42 AMacoustic-motherboard-98931
05/12/2023, 11:56 AMsteep-manchester-31195
05/12/2023, 1:53 PMbillions-easter-91774
05/12/2023, 5:16 PMbillions-easter-91774
05/12/2023, 5:17 PMrke2-killall.sh
Now, why is it like that though?broad-farmer-70498
05/13/2023, 3:12 PMable-zebra-19664
05/15/2023, 11:15 AM"couldn't get resource list for <http://metrics.k8s.io/v1beta1|metrics.k8s.io/v1beta1>: the server is currently unable to handle the request".
i haven t done anything, it s the default metrics server. i only installed the cluster and after deploying some apps this error started to occure after every kubectl command. also in api-service <http://v1beta1.metrics.k8s.io|v1beta1.metrics.k8s.io> , not local but in kubesystem/rke2-metrics-server and false(failedDiscoveryCheck)
. 😬careful-orange-63732
05/15/2023, 11:35 AM[root@k8s-rancher-rocky-cp1 ~]# journalctl -u rancher-system-agent
May 15 08:24:32 k8s-rancher-rocky-cp1 systemd[1]: Started Rancher System Agent.
May 15 08:24:32 k8s-rancher-rocky-cp1 rancher-system-agent[5319]: time="2023-05-15T08:24:32-03:00" level=info msg="Rancher System Agent version v0.3.2 (afbc4aa) is starting"
May 15 08:24:32 k8s-rancher-rocky-cp1 rancher-system-agent[5319]: time="2023-05-15T08:24:32-03:00" level=info msg="Using directory /var/lib/rancher/agent/work for work"
May 15 08:24:32 k8s-rancher-rocky-cp1 rancher-system-agent[5319]: time="2023-05-15T08:24:32-03:00" level=info msg="Starting remote watch of plans"
May 15 08:24:32 k8s-rancher-rocky-cp1 rancher-system-agent[5319]: E0515 08:24:32.466285 5319 memcache.go:206] couldn't get resource list for <http://management.cattle.io/v3|management.cattle.io/v3>:
May 15 08:24:32 k8s-rancher-rocky-cp1 rancher-system-agent[5319]: time="2023-05-15T08:24:32-03:00" level=info msg="Starting /v1, Kind=Secret controller"
quiet-musician-28232
05/15/2023, 8:25 PMquiet-musician-28232
05/15/2023, 8:29 PMmagnificent-vr-88571
05/15/2023, 10:54 PMacoustic-tiger-92861
05/16/2023, 6:24 AMable-zebra-19664
05/16/2023, 9:26 AMhundreds-evening-84071
05/16/2023, 2:00 PMrke2-uninstall.ps1
However this did not clean up things under c:\var\lib\
Is there a different (proper) way to do uninstall on Windows nodes?acoustic-tiger-92861
05/16/2023, 5:23 PMbroad-farmer-70498
05/16/2023, 6:02 PM+ helm_v3 install --set-string global.clusterCIDR=10.42.0.0/16 --set-string global.clusterCIDRv4=10.42.0.0/16 --set-string global.clusterDNS=10.43.0.10 --set-string global.clusterDomain=cluster.local --set-string global.rke2DataDir=/var/lib/rancher/rke2 --set-string global.serviceCIDR=10.43.0.0/16 rke2-coredns /tmp/rke2-coredns.tgz --values /config/values-10_HelmChartConfig.yaml
Error: INSTALLATION FAILED: cannot re-use a name that is still in use
quiet-musician-28232
05/16/2023, 11:30 PMworried-football-17739
05/17/2023, 9:25 AMHighThresholdPercent
• LowThresholdPercent
These values are set to 85% and 80% percent accordingly.
Any suggestion where can I change these values?creamy-autumn-87994
05/17/2023, 10:24 PM299 - core
and 295 - services
, but 295 ends up being the primary nic on the VM and 299 secondary. This is on Rancher 2.7.0.acoustic-tiger-92861
05/18/2023, 5:55 AMbroad-farmer-70498
05/18/2023, 3:40 PMbrave-rainbow-31093
05/18/2023, 4:58 PMspec:
defaultPodSecurityAdmissionConfigurationTemplateName: rancher-restricted
rkeConfig:
machineSelectorConfig:
- config:
profile: cis-1.23
protect-kernel-defaults: true
Then I tried CIS scan using rke2-cis-1.23-profile-hardened
profile following this guide https://ranchermanager.docs.rancher.com/pages-for-subheaders/cis-scan-guides and got this result.
Is this expected result?
PS: CIS benchmark app version is 4.0.0brave-rainbow-31093
05/18/2023, 5:07 PMagreeable-airplane-98995
05/19/2023, 6:36 PMabundant-noon-17295
05/23/2023, 8:27 AMdnsPolicy
, currently it is set to ClusterFirst
and since api-server is static pod using hostnetwork, the dnsPolicy
will fallback to default
behaviour
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/