apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-250.ec2.internal uid: d4b54757-4326-4ec7-b96c-f52c07bd0612 resourceVersion: "77040" uid: 7aff466a-375a-4973-9c0b-dd5a387eee53 spec: sourcePod: network-check-source-7d88cb55d8-q69pz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T17:41:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.145674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:30:58Z" - latency: 1.059345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:29:58Z" - latency: 951.419µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:28:58Z" - latency: 1.100145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:27:58Z" - latency: 1.185962ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:26:58Z" - latency: 1.002271ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:25:58Z" - latency: 1.000831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:24:58Z" - latency: 884.717µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:23:58Z" - latency: 1.520738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:22:58Z" - latency: 1.292397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:21:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-250.ec2.internal uid: d4b54757-4326-4ec7-b96c-f52c07bd0612 resourceVersion: "74710" uid: 627914dc-4d7a-4765-ba8e-c6700a10107b spec: sourcePod: network-check-source-7d88cb55d8-q69pz targetEndpoint: ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T17:40:58Z" message: 'load-balancer-api-external: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.43717ms message: 'load-balancer-api-external: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:28:58Z" - latency: 9.867737ms message: 'load-balancer-api-external: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:28:58Z" - latency: 4.66319ms message: 'load-balancer-api-external: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:27:58Z" - latency: 7.949216ms message: 'load-balancer-api-external: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:27:58Z" - latency: 4.393697ms message: 'load-balancer-api-external: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:26:58Z" - latency: 9.203885ms message: 'load-balancer-api-external: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:26:58Z" - latency: 4.635038ms message: 'load-balancer-api-external: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:25:58Z" - latency: 7.75049ms message: 'load-balancer-api-external: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:25:58Z" - latency: 3.977568ms message: 'load-balancer-api-external: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:24:58Z" - latency: 7.961568ms message: 'load-balancer-api-external: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:24:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-250.ec2.internal uid: d4b54757-4326-4ec7-b96c-f52c07bd0612 resourceVersion: "74709" uid: 5d4e056f-8227-4030-bdcb-22a573594442 spec: sourcePod: network-check-source-7d88cb55d8-q69pz targetEndpoint: ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T17:40:58Z" message: 'load-balancer-api-internal: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.97021ms message: 'load-balancer-api-internal: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:28:58Z" - latency: 9.848574ms message: 'load-balancer-api-internal: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:28:58Z" - latency: 5.000651ms message: 'load-balancer-api-internal: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:27:58Z" - latency: 8.017014ms message: 'load-balancer-api-internal: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:27:58Z" - latency: 6.18814ms message: 'load-balancer-api-internal: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:26:58Z" - latency: 9.143374ms message: 'load-balancer-api-internal: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:26:58Z" - latency: 4.16763ms message: 'load-balancer-api-internal: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:25:58Z" - latency: 7.783045ms message: 'load-balancer-api-internal: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:25:58Z" - latency: 3.887358ms message: 'load-balancer-api-internal: tcp connection to ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:24:58Z" - latency: 8.014384ms message: 'load-balancer-api-internal: resolved host name ae144355299bf4389bc4de8c3f5833a3-3811e8137bed6147.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T18:24:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-250-to-network-check-target-ip-10-0-135-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-250.ec2.internal uid: d4b54757-4326-4ec7-b96c-f52c07bd0612 resourceVersion: "77038" uid: feb8d5c2-530f-422b-ad78-bbec9e43ceb2 spec: sourcePod: network-check-source-7d88cb55d8-q69pz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-30T17:41:58Z" message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.500064ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:30:58Z" - latency: 2.448365ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:29:58Z" - latency: 2.431298ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:28:58Z" - latency: 2.524697ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:27:58Z" - latency: 2.48535ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:26:58Z" - latency: 2.403018ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:25:58Z" - latency: 2.485441ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:24:58Z" - latency: 2.200949ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:23:58Z" - latency: 2.139339ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:22:58Z" - latency: 2.558267ms message: 'network-check-target-ip-10-0-135-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:21:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-250-to-network-check-target-ip-10-0-137-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-250.ec2.internal uid: d4b54757-4326-4ec7-b96c-f52c07bd0612 resourceVersion: "77037" uid: 158e3b2a-4998-4d66-b07e-d118109f022c spec: sourcePod: network-check-source-7d88cb55d8-q69pz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T17:41:58Z" message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 963.095µs message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:30:58Z" - latency: 980.158µs message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:29:58Z" - latency: 1.520916ms message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:28:58Z" - latency: 982.218µs message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:27:58Z" - latency: 1.072946ms message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:26:58Z" - latency: 997.057µs message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:25:58Z" - latency: 999.066µs message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:24:58Z" - latency: 1.299594ms message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:23:58Z" - latency: 765.65µs message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:22:58Z" - latency: 1.856769ms message: 'network-check-target-ip-10-0-137-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:21:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-250-to-network-check-target-ip-10-0-140-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-250.ec2.internal uid: d4b54757-4326-4ec7-b96c-f52c07bd0612 resourceVersion: "77039" uid: 7ab066e7-cd84-4af2-8db4-24872dc92e93 spec: sourcePod: network-check-source-7d88cb55d8-q69pz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-30T17:41:58Z" message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.364676ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:30:58Z" - latency: 2.473395ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:29:58Z" - latency: 2.36486ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:28:58Z" - latency: 2.393014ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:27:58Z" - latency: 2.643051ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:26:58Z" - latency: 2.421126ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:25:58Z" - latency: 2.378177ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:24:58Z" - latency: 2.312989ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:23:58Z" - latency: 2.008698ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:22:58Z" - latency: 2.780285ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:21:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:34:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-250.ec2.internal uid: d4b54757-4326-4ec7-b96c-f52c07bd0612 resourceVersion: "74708" uid: 6fec3583-ec32-4596-98ea-3b6179d21dd9 spec: sourcePod: network-check-source-7d88cb55d8-q69pz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T17:40:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.044541ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:28:58Z" - latency: 2.023693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T18:28:58Z" - latency: 1.031293ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:27:58Z" - latency: 1.74482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T18:27:58Z" - latency: 965.387µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:26:58Z" - latency: 1.879575ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T18:26:58Z" - latency: 946.774µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:25:58Z" - latency: 1.888951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T18:25:58Z" - latency: 881.75µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T18:24:58Z" - latency: 1.633684ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T18:24:58Z" kind: List metadata: resourceVersion: ""