apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:36:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 513e2943-c2e3-4f94-834f-69d8d8a2fdd9 resourceVersion: "70225" uid: 1c87977f-0408-4d54-9d47-ea0c393337b0 spec: sourcePod: network-check-source-7d88cb55d8-ktts4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T19:43:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.90517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:22Z" - latency: 1.210269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:22Z" - latency: 1.385648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:23:22Z" - latency: 943.857µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:22:22Z" - latency: 1.137996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:21:22Z" - latency: 865.233µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:20:22Z" - latency: 1.210271ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:19:22Z" - latency: 1.513185ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:18:22Z" - latency: 1.346361ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:17:22Z" - latency: 1.076509ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:16:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:36:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 513e2943-c2e3-4f94-834f-69d8d8a2fdd9 resourceVersion: "75381" uid: c9cc736e-1ee0-4764-8cae-aaf95c05da08 spec: sourcePod: network-check-source-7d88cb55d8-ktts4 targetEndpoint: a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T19:42:22Z" message: 'load-balancer-api-external: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.825856ms message: 'load-balancer-api-external: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:30:22Z" - latency: 7.658436ms message: 'load-balancer-api-external: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:30:22Z" - latency: 4.155908ms message: 'load-balancer-api-external: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:22Z" - latency: 6.886399ms message: 'load-balancer-api-external: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:29:22Z" - latency: 5.822046ms message: 'load-balancer-api-external: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:22Z" - latency: 7.637703ms message: 'load-balancer-api-external: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:28:22Z" - latency: 4.40357ms message: 'load-balancer-api-external: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:22Z" - latency: 6.976871ms message: 'load-balancer-api-external: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:27:22Z" - latency: 6.554032ms message: 'load-balancer-api-external: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:22Z" - latency: 8.509017ms message: 'load-balancer-api-external: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:26:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:36:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 513e2943-c2e3-4f94-834f-69d8d8a2fdd9 resourceVersion: "75380" uid: 4b43d93e-6e91-41f1-9caa-4b7dc097d601 spec: sourcePod: network-check-source-7d88cb55d8-ktts4 targetEndpoint: a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T19:42:22Z" message: 'load-balancer-api-internal: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.905214ms message: 'load-balancer-api-internal: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:30:22Z" - latency: 7.698409ms message: 'load-balancer-api-internal: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:30:22Z" - latency: 4.46485ms message: 'load-balancer-api-internal: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:22Z" - latency: 6.953601ms message: 'load-balancer-api-internal: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:29:22Z" - latency: 5.801248ms message: 'load-balancer-api-internal: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:22Z" - latency: 7.694478ms message: 'load-balancer-api-internal: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:28:22Z" - latency: 4.392149ms message: 'load-balancer-api-internal: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:22Z" - latency: 7.050054ms message: 'load-balancer-api-internal: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:27:22Z" - latency: 4.61081ms message: 'load-balancer-api-internal: tcp connection to a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:22Z" - latency: 8.595858ms message: 'load-balancer-api-internal: resolved host name a0e16acf0db3047569f00673d45cf9b9-2aa0abf306a66c9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:26:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:36:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-network-check-target-ip-10-0-131-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 513e2943-c2e3-4f94-834f-69d8d8a2fdd9 resourceVersion: "70223" uid: 9cfc94e3-ea87-40cb-a0da-cd77f8020c89 spec: sourcePod: network-check-source-7d88cb55d8-ktts4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T19:43:22Z" message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.062263ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:22Z" - latency: 2.100028ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:22Z" - latency: 1.946618ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:23:22Z" - latency: 2.15426ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:22:22Z" - latency: 1.692939ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:21:22Z" - latency: 1.914928ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:20:22Z" - latency: 2.148197ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:19:22Z" - latency: 2.120359ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:18:22Z" - latency: 1.693222ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:17:22Z" - latency: 1.749162ms message: 'network-check-target-ip-10-0-131-248: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:16:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:36:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-network-check-target-ip-10-0-137-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 513e2943-c2e3-4f94-834f-69d8d8a2fdd9 resourceVersion: "70224" uid: 3654c654-e008-4e33-b02e-81fef14dc9fe spec: sourcePod: network-check-source-7d88cb55d8-ktts4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T19:43:22Z" message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.510373ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:22Z" - latency: 2.210773ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:22Z" - latency: 1.987788ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:23:22Z" - latency: 2.318161ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:22:22Z" - latency: 2.153155ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:21:22Z" - latency: 1.93131ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:20:22Z" - latency: 2.356414ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:19:22Z" - latency: 2.286243ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:18:22Z" - latency: 2.027706ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:17:22Z" - latency: 2.084694ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:16:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:36:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-network-check-target-ip-10-0-138-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 513e2943-c2e3-4f94-834f-69d8d8a2fdd9 resourceVersion: "70222" uid: dea5f095-447b-45d3-9834-9e4376c058ea spec: sourcePod: network-check-source-7d88cb55d8-ktts4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T19:43:22Z" message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.273µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:22Z" - latency: 864.777µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:22Z" - latency: 873.078µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:23:22Z" - latency: 890.85µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:22:22Z" - latency: 896.127µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:21:22Z" - latency: 1.304118ms message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:20:22Z" - latency: 923.146µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:19:22Z" - latency: 1.363583ms message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:18:22Z" - latency: 712.101µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:17:22Z" - latency: 744.797µs message: 'network-check-target-ip-10-0-138-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:16:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:36:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-37-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-37.ec2.internal uid: 513e2943-c2e3-4f94-834f-69d8d8a2fdd9 resourceVersion: "75379" uid: a6592251-c7f4-4c95-8817-c6d146cb55ea spec: sourcePod: network-check-source-7d88cb55d8-ktts4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T19:42:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.200102ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:30:22Z" - latency: 1.950736ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:30:22Z" - latency: 1.00815ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:22Z" - latency: 2.060104ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:29:22Z" - latency: 1.107059ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:22Z" - latency: 2.114942ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:28:22Z" - latency: 1.157406ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:22Z" - latency: 2.121591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:27:22Z" - latency: 954.119µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:22Z" - latency: 2.435387ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:26:22Z" kind: List metadata: resourceVersion: ""