apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:33:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-22-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-22.ec2.internal uid: f7417e20-8f95-464b-b398-801773fae3d8 resourceVersion: "15528" uid: 71118764-b6c3-4bd5-9dfe-de09f7e1cba8 spec: sourcePod: network-check-source-869dcfcdcd-nhqk8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T15:40:48Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.567µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:48Z" - latency: 1.137095ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:48Z" - latency: 1.007455ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:48Z" - latency: 972.533µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:48Z" - latency: 1.023426ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:48Z" - latency: 1.140661ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:48Z" - latency: 962.876µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:34:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:33:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-22-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-22.ec2.internal uid: f7417e20-8f95-464b-b398-801773fae3d8 resourceVersion: "15161" uid: db09ab16-89ab-4510-b53c-3796b892d9b7 spec: sourcePod: network-check-source-869dcfcdcd-nhqk8 targetEndpoint: a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:39:48Z" message: 'load-balancer-api-external: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.142647ms message: 'load-balancer-api-external: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:48Z" - latency: 8.52458ms message: 'load-balancer-api-external: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:39:48Z" - latency: 5.100667ms message: 'load-balancer-api-external: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:48Z" - latency: 8.454761ms message: 'load-balancer-api-external: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:38:48Z" - latency: 6.393815ms message: 'load-balancer-api-external: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:48Z" - latency: 7.759969ms message: 'load-balancer-api-external: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:37:48Z" - latency: 4.873584ms message: 'load-balancer-api-external: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:48Z" - latency: 8.061358ms message: 'load-balancer-api-external: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:36:48Z" - latency: 4.560715ms message: 'load-balancer-api-external: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:48Z" - latency: 7.983141ms message: 'load-balancer-api-external: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:35:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:33:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-22-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-22.ec2.internal uid: f7417e20-8f95-464b-b398-801773fae3d8 resourceVersion: "15162" uid: de25a265-bb79-4f32-9f8f-945085fa50e3 spec: sourcePod: network-check-source-869dcfcdcd-nhqk8 targetEndpoint: a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:39:48Z" message: 'load-balancer-api-internal: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.155843ms message: 'load-balancer-api-internal: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:48Z" - latency: 8.649155ms message: 'load-balancer-api-internal: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:39:48Z" - latency: 4.366303ms message: 'load-balancer-api-internal: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:48Z" - latency: 8.514207ms message: 'load-balancer-api-internal: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:38:48Z" - latency: 6.374689ms message: 'load-balancer-api-internal: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:48Z" - latency: 7.840111ms message: 'load-balancer-api-internal: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:37:48Z" - latency: 4.508419ms message: 'load-balancer-api-internal: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:48Z" - latency: 8.186919ms message: 'load-balancer-api-internal: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:36:48Z" - latency: 4.900886ms message: 'load-balancer-api-internal: tcp connection to a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:48Z" - latency: 8.046706ms message: 'load-balancer-api-internal: resolved host name a62e873c158594956aa4afdc9a03a478-b618da23853255ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:35:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:33:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-22-to-network-check-target-ip-10-0-130-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-22.ec2.internal uid: f7417e20-8f95-464b-b398-801773fae3d8 resourceVersion: "15525" uid: 962807ff-618e-4af4-9a82-811bc7b99231 spec: sourcePod: network-check-source-869dcfcdcd-nhqk8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:40:48Z" message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.953646ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:48Z" - latency: 1.800376ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:48Z" - latency: 1.936729ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:48Z" - latency: 2.016738ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:48Z" - latency: 1.922452ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:48Z" - latency: 1.927989ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:48Z" - latency: 2.246574ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:34:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:33:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-22-to-network-check-target-ip-10-0-130-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-22.ec2.internal uid: f7417e20-8f95-464b-b398-801773fae3d8 resourceVersion: "15526" uid: a2def71c-ef02-4f4f-ab15-380e5b58dea0 spec: sourcePod: network-check-source-869dcfcdcd-nhqk8 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:40:48Z" message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 771.811µs message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:48Z" - latency: 1.145068ms message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:48Z" - latency: 1.611908ms message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:48Z" - latency: 1.438ms message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:48Z" - latency: 697.357µs message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:48Z" - latency: 792.93µs message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:48Z" - latency: 1.244328ms message: 'network-check-target-ip-10-0-130-22: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:34:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:33:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-22-to-network-check-target-ip-10-0-141-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-22.ec2.internal uid: f7417e20-8f95-464b-b398-801773fae3d8 resourceVersion: "15527" uid: a581d66e-7b11-46d0-83a8-e79a03135d1b spec: sourcePod: network-check-source-869dcfcdcd-nhqk8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:40:48Z" message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.13682ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:48Z" - latency: 1.939073ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:48Z" - latency: 1.87935ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:48Z" - latency: 2.170812ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:48Z" - latency: 1.755368ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:48Z" - latency: 1.856012ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:48Z" - latency: 2.11591ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:34:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:33:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-22-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-22.ec2.internal uid: f7417e20-8f95-464b-b398-801773fae3d8 resourceVersion: "15160" uid: b48e4901-fd3a-4d85-b30f-29b44e96f9b2 spec: sourcePod: network-check-source-869dcfcdcd-nhqk8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T15:39:48Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 940.967µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:48Z" - latency: 1.738227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:39:48Z" - latency: 794.776µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:48Z" - latency: 1.972458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:38:48Z" - latency: 1.036857ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:48Z" - latency: 1.598256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:37:48Z" - latency: 995.453µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:48Z" - latency: 1.594746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:36:48Z" - latency: 892.419µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:48Z" - latency: 1.615422ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:35:48Z" kind: List metadata: resourceVersion: ""