apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T13:29:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 8f0e3d6c-a7a4-43c1-91dc-179712dc281a resourceVersion: "53496" uid: 7cf65cfc-2e49-43d3-b717-1698f3e345e7 spec: sourcePod: network-check-source-685456655f-pvnqg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T13:36:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.132483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:57:38Z" - latency: 1.542055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:56:38Z" - latency: 1.29321ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:55:38Z" - latency: 1.212241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:54:38Z" - latency: 1.107801ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:53:38Z" - latency: 1.200607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:52:38Z" - latency: 1.090624ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:51:38Z" - latency: 1.115031ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:50:38Z" - latency: 1.482407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:49:38Z" - latency: 1.136518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:48:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T13:29:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 8f0e3d6c-a7a4-43c1-91dc-179712dc281a resourceVersion: "55073" uid: 4eed64b2-b3c4-4dbe-a27f-14272eb6330d spec: sourcePod: network-check-source-685456655f-pvnqg targetEndpoint: a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T13:35:38Z" message: 'load-balancer-api-external: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.838715ms message: 'load-balancer-api-external: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:59:38Z" - latency: 8.257855ms message: 'load-balancer-api-external: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:59:38Z" - latency: 3.907448ms message: 'load-balancer-api-external: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:58:38Z" - latency: 9.256741ms message: 'load-balancer-api-external: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:58:38Z" - latency: 4.929296ms message: 'load-balancer-api-external: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:57:38Z" - latency: 8.403184ms message: 'load-balancer-api-external: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:57:38Z" - latency: 4.713504ms message: 'load-balancer-api-external: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:56:38Z" - latency: 12.397172ms message: 'load-balancer-api-external: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:56:38Z" - latency: 6.234732ms message: 'load-balancer-api-external: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:55:38Z" - latency: 9.323839ms message: 'load-balancer-api-external: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:55:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T13:29:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 8f0e3d6c-a7a4-43c1-91dc-179712dc281a resourceVersion: "55074" uid: 56b254ca-d5cc-4789-968f-e8e29c8e4278 spec: sourcePod: network-check-source-685456655f-pvnqg targetEndpoint: a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T13:35:38Z" message: 'load-balancer-api-internal: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.343576ms message: 'load-balancer-api-internal: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:59:38Z" - latency: 8.351251ms message: 'load-balancer-api-internal: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:59:38Z" - latency: 9.627684ms message: 'load-balancer-api-internal: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:58:38Z" - latency: 9.315573ms message: 'load-balancer-api-internal: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:58:38Z" - latency: 6.189044ms message: 'load-balancer-api-internal: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:57:38Z" - latency: 8.463891ms message: 'load-balancer-api-internal: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:57:38Z" - latency: 4.700367ms message: 'load-balancer-api-internal: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:56:38Z" - latency: 12.369879ms message: 'load-balancer-api-internal: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:56:38Z" - latency: 5.698703ms message: 'load-balancer-api-internal: tcp connection to a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:55:38Z" - latency: 9.382015ms message: 'load-balancer-api-internal: resolved host name a6fed80a496fb413a931e7dd7a8165e3-1b765c6cab0a8ed6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T13:55:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T13:29:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-network-check-target-ip-10-0-129-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 8f0e3d6c-a7a4-43c1-91dc-179712dc281a resourceVersion: "53494" uid: 45d06bdb-2c80-4471-aa68-a4d6cf722d83 spec: sourcePod: network-check-source-685456655f-pvnqg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T13:36:38Z" message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.765µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:57:38Z" - latency: 1.321373ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:56:38Z" - latency: 1.254342ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:55:38Z" - latency: 1.340216ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:54:38Z" - latency: 1.080269ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:53:38Z" - latency: 1.540807ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:52:38Z" - latency: 958.803µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:51:38Z" - latency: 1.361877ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:50:38Z" - latency: 834.546µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:49:38Z" - latency: 1.622205ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:48:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T13:29:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-network-check-target-ip-10-0-135-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 8f0e3d6c-a7a4-43c1-91dc-179712dc281a resourceVersion: "53493" uid: 296e5de4-58f1-4cb5-a9b7-7c1a0a449789 spec: sourcePod: network-check-source-685456655f-pvnqg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T13:36:38Z" message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.166487ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:57:38Z" - latency: 2.0595ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:56:38Z" - latency: 2.297246ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:55:38Z" - latency: 2.437691ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:54:38Z" - latency: 2.330333ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:53:38Z" - latency: 2.410379ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:52:38Z" - latency: 1.868374ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:51:38Z" - latency: 2.027235ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:50:38Z" - latency: 2.427151ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:49:38Z" - latency: 2.616659ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:48:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T13:29:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-network-check-target-ip-10-0-136-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 8f0e3d6c-a7a4-43c1-91dc-179712dc281a resourceVersion: "53495" uid: 73a56dd1-dbd0-4de2-afb7-1c612a52e9d5 spec: sourcePod: network-check-source-685456655f-pvnqg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T13:36:38Z" message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.537779ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:57:38Z" - latency: 2.548179ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:56:38Z" - latency: 2.403597ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:55:38Z" - latency: 2.18198ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:54:38Z" - latency: 2.29246ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:53:38Z" - latency: 2.130054ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:52:38Z" - latency: 2.203249ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:51:38Z" - latency: 2.614862ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:50:38Z" - latency: 2.372327ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:49:38Z" - latency: 2.008579ms message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:48:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T13:29:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 8f0e3d6c-a7a4-43c1-91dc-179712dc281a resourceVersion: "55072" uid: b10b8b42-566a-4cee-bcb7-538ebdc2707d spec: sourcePod: network-check-source-685456655f-pvnqg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T13:35:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.172774ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:59:38Z" - latency: 1.885081ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:59:38Z" - latency: 894.349µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:58:38Z" - latency: 2.747728ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:58:38Z" - latency: 1.057164ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:57:38Z" - latency: 1.945278ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:57:38Z" - latency: 1.108372ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:56:38Z" - latency: 2.155137ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:56:38Z" - latency: 897.877µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T13:55:38Z" - latency: 1.819419ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T13:55:38Z" kind: List metadata: resourceVersion: ""