apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-227-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-227.ec2.internal uid: 263b75bd-ca3a-4696-8d2e-1700a4ad5742 resourceVersion: "39906" uid: eb57375d-6e0f-4c42-b786-2ca62fb4b1a8 spec: sourcePod: network-check-source-7f44b6dd87-7b6rg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T11:28:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 716.411µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:17:24Z" - latency: 1.013598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:16:24Z" - latency: 1.176945ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:15:24Z" - latency: 1.09473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:14:24Z" - latency: 913.337µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:13:24Z" - latency: 1.348233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:12:24Z" - latency: 994.439µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:11:24Z" - latency: 1.062466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:10:24Z" - latency: 1.143799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:09:24Z" - latency: 1.426558ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-227-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-227.ec2.internal uid: 263b75bd-ca3a-4696-8d2e-1700a4ad5742 resourceVersion: "38963" uid: 45d249e1-0302-4f96-8a13-16f42c76623f spec: sourcePod: network-check-source-7f44b6dd87-7b6rg targetEndpoint: a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T11:27:24Z" message: 'load-balancer-api-external: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.940431ms message: 'load-balancer-api-external: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:15:24Z" - latency: 6.258819ms message: 'load-balancer-api-external: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:15:24Z" - latency: 4.661473ms message: 'load-balancer-api-external: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:14:24Z" - latency: 7.371522ms message: 'load-balancer-api-external: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:14:24Z" - latency: 5.779186ms message: 'load-balancer-api-external: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:13:24Z" - latency: 6.710445ms message: 'load-balancer-api-external: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:13:24Z" - latency: 5.366687ms message: 'load-balancer-api-external: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:12:24Z" - latency: 7.731946ms message: 'load-balancer-api-external: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:12:24Z" - latency: 4.980477ms message: 'load-balancer-api-external: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:11:24Z" - latency: 14.204188ms message: 'load-balancer-api-external: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:11:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-227-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-227.ec2.internal uid: 263b75bd-ca3a-4696-8d2e-1700a4ad5742 resourceVersion: "38964" uid: afb2c85b-3833-46d3-a2b9-0a7483e42375 spec: sourcePod: network-check-source-7f44b6dd87-7b6rg targetEndpoint: a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T11:27:24Z" message: 'load-balancer-api-internal: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.940986ms message: 'load-balancer-api-internal: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:15:24Z" - latency: 6.187273ms message: 'load-balancer-api-internal: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:15:24Z" - latency: 4.617191ms message: 'load-balancer-api-internal: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:14:24Z" - latency: 7.408625ms message: 'load-balancer-api-internal: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:14:24Z" - latency: 4.608552ms message: 'load-balancer-api-internal: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:13:24Z" - latency: 6.629443ms message: 'load-balancer-api-internal: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:13:24Z" - latency: 5.94874ms message: 'load-balancer-api-internal: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:12:24Z" - latency: 7.672073ms message: 'load-balancer-api-internal: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:12:24Z" - latency: 5.016645ms message: 'load-balancer-api-internal: tcp connection to a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:11:24Z" - latency: 14.330622ms message: 'load-balancer-api-internal: resolved host name a445d36c272c04776ad6c1424393a1bb-c978b6f068c4c4ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:11:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-227-to-network-check-target-ip-10-0-136-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-227.ec2.internal uid: 263b75bd-ca3a-4696-8d2e-1700a4ad5742 resourceVersion: "39904" uid: 441c9d88-19a9-4593-98a6-ce5d4445558e spec: sourcePod: network-check-source-7f44b6dd87-7b6rg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T11:28:24Z" message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 778.502µs message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:17:24Z" - latency: 770.505µs message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:16:24Z" - latency: 884.862µs message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:15:24Z" - latency: 941.073µs message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:14:24Z" - latency: 830.743µs message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:13:24Z" - latency: 777.092µs message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:12:24Z" - latency: 1.054241ms message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:11:24Z" - latency: 791.227µs message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:10:24Z" - latency: 697.272µs message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:09:24Z" - latency: 974.393µs message: 'network-check-target-ip-10-0-136-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-227-to-network-check-target-ip-10-0-141-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-227.ec2.internal uid: 263b75bd-ca3a-4696-8d2e-1700a4ad5742 resourceVersion: "39905" uid: f3ee1b29-2836-49cb-96ec-83a4c8649305 spec: sourcePod: network-check-source-7f44b6dd87-7b6rg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-25T11:28:24Z" message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.144232ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:17:24Z" - latency: 2.131941ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:16:24Z" - latency: 2.024975ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:15:24Z" - latency: 1.924752ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:14:24Z" - latency: 1.818428ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:13:24Z" - latency: 1.820632ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:12:24Z" - latency: 1.959898ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:11:24Z" - latency: 1.867044ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:10:24Z" - latency: 1.922963ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:09:24Z" - latency: 2.262886ms message: 'network-check-target-ip-10-0-141-158: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-227-to-network-check-target-ip-10-0-143-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-227.ec2.internal uid: 263b75bd-ca3a-4696-8d2e-1700a4ad5742 resourceVersion: "39903" uid: fd973ac1-c1a7-4ab3-a39b-16175e74b290 spec: sourcePod: network-check-source-7f44b6dd87-7b6rg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T11:28:24Z" message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.788304ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:17:24Z" - latency: 2.134287ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:16:24Z" - latency: 1.713354ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:15:24Z" - latency: 1.764527ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:14:24Z" - latency: 1.869424ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:13:24Z" - latency: 1.702628ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:12:24Z" - latency: 1.962068ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:11:24Z" - latency: 1.778014ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:10:24Z" - latency: 1.555915ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:09:24Z" - latency: 1.89323ms message: 'network-check-target-ip-10-0-143-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-227-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-227.ec2.internal uid: 263b75bd-ca3a-4696-8d2e-1700a4ad5742 resourceVersion: "38962" uid: a575bebb-fb2d-488a-bda5-3b6e20134ffc spec: sourcePod: network-check-source-7f44b6dd87-7b6rg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T11:27:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 770.452µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:15:24Z" - latency: 1.68724ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:15:24Z" - latency: 825.205µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:14:24Z" - latency: 1.887767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:14:24Z" - latency: 766.083µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:13:24Z" - latency: 1.699693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:13:24Z" - latency: 897.759µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:12:24Z" - latency: 1.751162ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:12:24Z" - latency: 766.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:11:24Z" - latency: 1.866327ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:11:24Z" kind: List metadata: resourceVersion: ""