apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T00:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-115-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-115.ec2.internal uid: af05b0c1-6f57-466b-b9ed-386b7022fee2 resourceVersion: "44121" uid: 3b3a9155-a3e4-4966-bccf-f3f5f5860103 spec: sourcePod: network-check-source-8894fc9bd-jtsx5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T00:14:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.151933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:35:23Z" - latency: 817.77µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:34:23Z" - latency: 863.865µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:33:23Z" - latency: 1.17669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:32:23Z" - latency: 853.077µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:31:23Z" - latency: 1.001199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:30:23Z" - latency: 1.645869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:29:23Z" - latency: 1.14246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:28:23Z" - latency: 1.053018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:27:23Z" - latency: 926.024µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:26:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T00:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-115-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-115.ec2.internal uid: af05b0c1-6f57-466b-b9ed-386b7022fee2 resourceVersion: "46696" uid: b6db805e-81f7-42cb-9e97-d72b6a2a8348 spec: sourcePod: network-check-source-8894fc9bd-jtsx5 targetEndpoint: a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T00:13:23Z" message: 'load-balancer-api-external: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.802129ms message: 'load-balancer-api-external: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:37:23Z" - latency: 8.430712ms message: 'load-balancer-api-external: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:37:23Z" - latency: 4.84016ms message: 'load-balancer-api-external: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:36:23Z" - latency: 8.740124ms message: 'load-balancer-api-external: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:36:23Z" - latency: 4.052678ms message: 'load-balancer-api-external: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:35:23Z" - latency: 7.723305ms message: 'load-balancer-api-external: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:35:23Z" - latency: 5.196708ms message: 'load-balancer-api-external: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:34:23Z" - latency: 8.709798ms message: 'load-balancer-api-external: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:34:23Z" - latency: 4.701707ms message: 'load-balancer-api-external: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:33:23Z" - latency: 7.403491ms message: 'load-balancer-api-external: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:33:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T00:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-115-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-115.ec2.internal uid: af05b0c1-6f57-466b-b9ed-386b7022fee2 resourceVersion: "46697" uid: 2311f47b-8307-4302-a978-6ad6672d0033 spec: sourcePod: network-check-source-8894fc9bd-jtsx5 targetEndpoint: a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T00:13:23Z" message: 'load-balancer-api-internal: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.764704ms message: 'load-balancer-api-internal: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:37:23Z" - latency: 8.474927ms message: 'load-balancer-api-internal: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:37:23Z" - latency: 4.935934ms message: 'load-balancer-api-internal: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:36:23Z" - latency: 8.678657ms message: 'load-balancer-api-internal: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:36:23Z" - latency: 3.932384ms message: 'load-balancer-api-internal: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:35:23Z" - latency: 7.830965ms message: 'load-balancer-api-internal: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:35:23Z" - latency: 5.187335ms message: 'load-balancer-api-internal: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:34:23Z" - latency: 8.626629ms message: 'load-balancer-api-internal: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:34:23Z" - latency: 4.693944ms message: 'load-balancer-api-internal: tcp connection to a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:33:23Z" - latency: 7.478747ms message: 'load-balancer-api-internal: resolved host name a1312053d307c482d88d2253ea14ee06-a7e4e06cafb4d3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T00:33:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T00:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-115-to-network-check-target-ip-10-0-132-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-115.ec2.internal uid: af05b0c1-6f57-466b-b9ed-386b7022fee2 resourceVersion: "44119" uid: 378dd0e0-580c-4e2d-ba81-451d4feb6b3a spec: sourcePod: network-check-source-8894fc9bd-jtsx5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T00:14:23Z" message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.508735ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:35:23Z" - latency: 2.049732ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:34:23Z" - latency: 2.010324ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:33:23Z" - latency: 2.131334ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:32:23Z" - latency: 1.960547ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:31:23Z" - latency: 2.163747ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:30:23Z" - latency: 1.885238ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:29:23Z" - latency: 2.155916ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:28:23Z" - latency: 1.819029ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:27:23Z" - latency: 2.36321ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:26:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T00:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-115-to-network-check-target-ip-10-0-136-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-115.ec2.internal uid: af05b0c1-6f57-466b-b9ed-386b7022fee2 resourceVersion: "44120" uid: a6def65c-b57d-43ab-99a1-f74a41fbee9f spec: sourcePod: network-check-source-8894fc9bd-jtsx5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T00:14:23Z" message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.41849ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:35:23Z" - latency: 2.293126ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:34:23Z" - latency: 2.136738ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:33:23Z" - latency: 2.304012ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:32:23Z" - latency: 2.172326ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:31:23Z" - latency: 2.218815ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:30:23Z" - latency: 2.183702ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:29:23Z" - latency: 2.176142ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:28:23Z" - latency: 2.38557ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:27:23Z" - latency: 2.340359ms message: 'network-check-target-ip-10-0-136-1: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:26:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T00:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-115-to-network-check-target-ip-10-0-143-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-115.ec2.internal uid: af05b0c1-6f57-466b-b9ed-386b7022fee2 resourceVersion: "44118" uid: c28c0960-b5ca-4307-9009-b682d51db8b8 spec: sourcePod: network-check-source-8894fc9bd-jtsx5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T00:14:23Z" message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.381645ms message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:35:23Z" - latency: 909.481µs message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:34:23Z" - latency: 880.729µs message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:33:23Z" - latency: 985.429µs message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:32:23Z" - latency: 1.241527ms message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:31:23Z" - latency: 832.073µs message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:30:23Z" - latency: 846.249µs message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:29:23Z" - latency: 915.663µs message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:28:23Z" - latency: 1.023321ms message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:27:23Z" - latency: 825.199µs message: 'network-check-target-ip-10-0-143-115: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:26:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T00:07:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-115-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-115.ec2.internal uid: af05b0c1-6f57-466b-b9ed-386b7022fee2 resourceVersion: "46694" uid: e21b4921-3fb4-449a-888f-408106aab0e3 spec: sourcePod: network-check-source-8894fc9bd-jtsx5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T00:13:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 809.567µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:37:23Z" - latency: 1.896297ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T00:37:23Z" - latency: 1.077454ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:36:23Z" - latency: 1.700181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T00:36:23Z" - latency: 986.043µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:35:23Z" - latency: 1.818969ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T00:35:23Z" - latency: 658.762µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:34:23Z" - latency: 1.977656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T00:34:23Z" - latency: 895.88µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T00:33:23Z" - latency: 1.577274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T00:33:23Z" kind: List metadata: resourceVersion: ""