apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:19:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-134.ec2.internal uid: 87485dee-841d-48f4-9528-63db29ec0ccd resourceVersion: "62932" uid: 98b3661a-6a5f-4819-8e3c-c73eab4ceec2 spec: sourcePod: network-check-source-7bc5b6bf85-mb2nf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T19:26:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.005863ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:01:15Z" - latency: 1.169369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:15Z" - latency: 1.014666ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:15Z" - latency: 1.204573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:15Z" - latency: 1.118819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:15Z" - latency: 984.346µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:15Z" - latency: 1.159569ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:55:15Z" - latency: 935.816µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:54:15Z" - latency: 865.071µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:53:15Z" - latency: 1.174364ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:52:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:19:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-134.ec2.internal uid: 87485dee-841d-48f4-9528-63db29ec0ccd resourceVersion: "62933" uid: 44b6df47-5911-484e-a1f0-d5c1d8f3fd6a spec: sourcePod: network-check-source-7bc5b6bf85-mb2nf targetEndpoint: af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T19:25:15Z" message: 'load-balancer-api-external: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.043835ms message: 'load-balancer-api-external: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:01:15Z" - latency: 7.71041ms message: 'load-balancer-api-external: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T20:01:15Z" - latency: 3.917863ms message: 'load-balancer-api-external: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:15Z" - latency: 6.931396ms message: 'load-balancer-api-external: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T20:00:15Z" - latency: 4.663175ms message: 'load-balancer-api-external: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:15Z" - latency: 16.166235ms message: 'load-balancer-api-external: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:59:15Z" - latency: 5.258023ms message: 'load-balancer-api-external: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:15Z" - latency: 7.960296ms message: 'load-balancer-api-external: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:58:15Z" - latency: 4.213953ms message: 'load-balancer-api-external: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:15Z" - latency: 8.556146ms message: 'load-balancer-api-external: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:57:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:19:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-134.ec2.internal uid: 87485dee-841d-48f4-9528-63db29ec0ccd resourceVersion: "62934" uid: 59f7896c-fe70-4ea2-9a7e-f2fb1d5a6aa2 spec: sourcePod: network-check-source-7bc5b6bf85-mb2nf targetEndpoint: af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T19:25:15Z" message: 'load-balancer-api-internal: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.005972ms message: 'load-balancer-api-internal: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:01:15Z" - latency: 7.590095ms message: 'load-balancer-api-internal: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T20:01:15Z" - latency: 3.908381ms message: 'load-balancer-api-internal: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:15Z" - latency: 6.95673ms message: 'load-balancer-api-internal: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T20:00:15Z" - latency: 4.718729ms message: 'load-balancer-api-internal: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:15Z" - latency: 16.085795ms message: 'load-balancer-api-internal: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:59:15Z" - latency: 5.227131ms message: 'load-balancer-api-internal: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:15Z" - latency: 7.993212ms message: 'load-balancer-api-internal: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:58:15Z" - latency: 3.743285ms message: 'load-balancer-api-internal: tcp connection to af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:15Z" - latency: 8.651159ms message: 'load-balancer-api-internal: resolved host name af55ee5ca08234a58842476ade42ff6a-6944453fed9c15a5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T19:57:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:19:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-134-to-network-check-target-ip-10-0-133-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-134.ec2.internal uid: 87485dee-841d-48f4-9528-63db29ec0ccd resourceVersion: "62928" uid: 283f48e3-0d10-4eaa-85a9-d3930c3d93dc spec: sourcePod: network-check-source-7bc5b6bf85-mb2nf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T19:26:15Z" message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.019405ms message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:01:15Z" - latency: 835.785µs message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:15Z" - latency: 972.728µs message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:15Z" - latency: 970.292µs message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:15Z" - latency: 1.004505ms message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:15Z" - latency: 970.49µs message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:15Z" - latency: 1.520204ms message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:55:15Z" - latency: 1.414713ms message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:54:15Z" - latency: 1.132023ms message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:53:15Z" - latency: 964.915µs message: 'network-check-target-ip-10-0-133-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:52:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:19:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-134-to-network-check-target-ip-10-0-136-208 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-134.ec2.internal uid: 87485dee-841d-48f4-9528-63db29ec0ccd resourceVersion: "62930" uid: e8d43a60-d4bc-4b23-8dd7-f6ba086a5a3e spec: sourcePod: network-check-source-7bc5b6bf85-mb2nf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T19:26:15Z" message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.104558ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:01:15Z" - latency: 2.452723ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:15Z" - latency: 2.105654ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:15Z" - latency: 1.954107ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:15Z" - latency: 2.104298ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:15Z" - latency: 1.903294ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:15Z" - latency: 2.229919ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:55:15Z" - latency: 2.341398ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:54:15Z" - latency: 2.034182ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:53:15Z" - latency: 2.095514ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:52:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:19:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-134-to-network-check-target-ip-10-0-140-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-134.ec2.internal uid: 87485dee-841d-48f4-9528-63db29ec0ccd resourceVersion: "62929" uid: 58cca871-718c-4093-8a93-49b6e17529f6 spec: sourcePod: network-check-source-7bc5b6bf85-mb2nf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T19:26:15Z" message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.199626ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:01:15Z" - latency: 2.438518ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:15Z" - latency: 2.139225ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:15Z" - latency: 2.292439ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:15Z" - latency: 2.250267ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:15Z" - latency: 1.837498ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:56:15Z" - latency: 2.344601ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:55:15Z" - latency: 2.353806ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:54:15Z" - latency: 2.4932ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:53:15Z" - latency: 2.460933ms message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:52:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T19:19:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-134.ec2.internal uid: 87485dee-841d-48f4-9528-63db29ec0ccd resourceVersion: "62931" uid: d2c41bc4-dc52-4483-86b6-1bca7295ec01 spec: sourcePod: network-check-source-7bc5b6bf85-mb2nf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T19:25:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.102407ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:01:15Z" - latency: 1.999246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T20:01:15Z" - latency: 910.456µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T20:00:15Z" - latency: 1.928001ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T20:00:15Z" - latency: 1.134723ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:59:15Z" - latency: 1.688728ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T19:59:15Z" - latency: 893.288µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:58:15Z" - latency: 2.108601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T19:58:15Z" - latency: 1.24801ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T19:57:15Z" - latency: 1.782446ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T19:57:15Z" kind: List metadata: resourceVersion: ""