red-waitress-37932
05/23/2023, 3:57 PMbulky-sunset-52084
05/23/2023, 8:43 PMred-waitress-37932
05/24/2023, 8:39 AMrough-farmer-49135
05/25/2023, 2:56 PMred-waitress-37932
05/26/2023, 8:15 AMrough-farmer-49135
05/26/2023, 11:57 AMkubectl get nodes
and was caching/displaying it. My understanding of Rancher v2 vs v1 is that in v2 it moved to doing everything in & with existing Kubernetes object types.red-waitress-37932
05/26/2023, 3:12 PMkubectl get nodes
without knowing at least one node IP address?rough-farmer-49135
05/26/2023, 3:23 PMbulky-sunset-52084
05/26/2023, 5:07 PMacceptable-match-53099
05/28/2023, 2:38 PMred-waitress-37932
06/05/2023, 7:11 AMbulky-sunset-52084
06/05/2023, 1:50 PMred-waitress-37932
06/06/2023, 8:04 AMrough-farmer-49135
06/06/2023, 1:31 PMred-waitress-37932
06/08/2023, 3:18 PM$ kubectl --context <name of the context for the cluster that rancher runs on> get <http://nodes.management.cattle.io|nodes.management.cattle.io> -n c-<API id of the cluster> m-<API id of the node> -o yaml | grep -E ':$|172'
metadata:
annotations:
finalizers:
labels:
spec:
internalNodeSpec:
podCIDRs:
metadataUpdate:
status:
conditions:
dockerInfo:
Labels:
SecurityOptions:
internalNodeStatus:
addresses:
- address: <control node IP>
- address: <control node IP>
allocatable:
capacity:
conditions:
daemonEndpoints:
kubeletEndpoint:
nodeInfo:
limits:
nodeAnnotations:
<http://flannel.alpha.coreos.com/public-ip|flannel.alpha.coreos.com/public-ip>: <control node IP>
<http://projectcalico.org/IPv4Address|projectcalico.org/IPv4Address>: <control node IP>/24
<http://rke.cattle.io/external-ip|rke.cattle.io/external-ip>: <control node IP>
<http://rke.cattle.io/internal-ip|rke.cattle.io/internal-ip>: <control node IP>
nodeLabels:
nodePlan:
plan:
files:
processes:
kube-proxy:
binds:
command:
- --bind-address=<control node IP>
healthCheck:
labels:
volumesFrom:
kubelet:
binds:
command:
env:
healthCheck:
labels:
volumesFrom:
nginx-proxy:
args:
- CP_HOSTS=<worker1 IP>,<worker2 ip>
command:
env:
- CP_HOSTS=<worker1 IP>,<worker2 ip>
labels:
service-sidekick:
command:
labels:
share-mnt:
args:
binds:
nodeTemplateSpec:
requested:
rkeNode:
address: <control node IP>
labels:
role:
I am using that data to generate DNS entries for all nodes, even.rough-farmer-49135
06/08/2023, 3:39 PMbulky-sunset-52084
06/08/2023, 8:18 PM