apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:26:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.ec2.internal
      uid: 645174ad-0c68-421c-96fa-b8c1dc44a21e
    resourceVersion: "23542"
    uid: 9866d8c0-a810-4daf-bacd-f9ffdc188ea5
  spec:
    sourcePod: network-check-source-685456655f-9lvzs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:33:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.082877ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:33:24Z"
    - latency: 1.325425ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 867.373µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 904.248µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 1.751621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 1.005457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:24Z"
    - latency: 1.037122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:26:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.ec2.internal
      uid: 645174ad-0c68-421c-96fa-b8c1dc44a21e
    resourceVersion: "22388"
    uid: 7f07dc2a-e16c-49c4-b0cb-e0224ab2390a
  spec:
    sourcePod: network-check-source-685456655f-9lvzs
    targetEndpoint: a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:32:24Z"
      message: 'load-balancer-api-external: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.481725ms
      message: 'load-balancer-api-external: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 8.741752ms
      message: 'load-balancer-api-external: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 3.490246ms
      message: 'load-balancer-api-external: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 8.711159ms
      message: 'load-balancer-api-external: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 4.141058ms
      message: 'load-balancer-api-external: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 8.44721ms
      message: 'load-balancer-api-external: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 4.923449ms
      message: 'load-balancer-api-external: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 9.405226ms
      message: 'load-balancer-api-external: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 4.794772ms
      message: 'load-balancer-api-external: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:24Z"
    - latency: 8.94904ms
      message: 'load-balancer-api-external: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:28:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:26:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.ec2.internal
      uid: 645174ad-0c68-421c-96fa-b8c1dc44a21e
    resourceVersion: "22389"
    uid: a37b85d9-5b29-4a17-ab91-6277f8ff58e9
  spec:
    sourcePod: network-check-source-685456655f-9lvzs
    targetEndpoint: a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:32:24Z"
      message: 'load-balancer-api-internal: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.507827ms
      message: 'load-balancer-api-internal: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 8.692132ms
      message: 'load-balancer-api-internal: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 3.39445ms
      message: 'load-balancer-api-internal: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 8.629195ms
      message: 'load-balancer-api-internal: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 4.172281ms
      message: 'load-balancer-api-internal: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 8.330633ms
      message: 'load-balancer-api-internal: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 5.254508ms
      message: 'load-balancer-api-internal: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 9.359003ms
      message: 'load-balancer-api-internal: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 3.585686ms
      message: 'load-balancer-api-internal: tcp connection to a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:24Z"
    - latency: 8.79172ms
      message: 'load-balancer-api-internal: resolved host name a32173f9247c24f5d925c3ee28a8e9f9-5c1007bc797c67d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:28:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:26:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-network-check-target-ip-10-0-133-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.ec2.internal
      uid: 645174ad-0c68-421c-96fa-b8c1dc44a21e
    resourceVersion: "23539"
    uid: b87e889a-93f1-42bc-91db-3e0b1cd532ae
  spec:
    sourcePod: network-check-source-685456655f-9lvzs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:33:24Z"
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.142738ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:33:24Z"
    - latency: 2.094435ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 2.328367ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 2.018066ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 1.847343ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 2.451587ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:24Z"
    - latency: 2.258051ms
      message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:26:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-network-check-target-ip-10-0-136-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.ec2.internal
      uid: 645174ad-0c68-421c-96fa-b8c1dc44a21e
    resourceVersion: "23540"
    uid: e9486bd1-9c31-486b-8633-b2b00b496a72
  spec:
    sourcePod: network-check-source-685456655f-9lvzs
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:33:24Z"
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.520327ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:33:24Z"
    - latency: 2.4911ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 1.999769ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 1.974388ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 1.862744ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 2.440995ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:24Z"
    - latency: 2.159662ms
      message: 'network-check-target-ip-10-0-136-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:26:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-network-check-target-ip-10-0-141-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.ec2.internal
      uid: 645174ad-0c68-421c-96fa-b8c1dc44a21e
    resourceVersion: "23538"
    uid: 61522d9d-8f97-4643-ac1f-4cd8564cb7fd
  spec:
    sourcePod: network-check-source-685456655f-9lvzs
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:33:24Z"
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.286481ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:33:24Z"
    - latency: 1.59046ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 1.492215ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 890.144µs
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 900.658µs
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 1.14267ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:24Z"
    - latency: 1.975603ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:27:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:26:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.ec2.internal
      uid: 645174ad-0c68-421c-96fa-b8c1dc44a21e
    resourceVersion: "22387"
    uid: 477a7744-cd58-4c4f-9c95-8beb8c39ecf5
  spec:
    sourcePod: network-check-source-685456655f-9lvzs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:32:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 952.882µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 2.366339ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:32:24Z"
    - latency: 1.169652ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 2.232655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:31:24Z"
    - latency: 802.481µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 1.91794ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:30:24Z"
    - latency: 876.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 2.619881ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:29:24Z"
    - latency: 1.305049ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:28:24Z"
    - latency: 1.855257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:28:24Z"
kind: List
metadata:
  resourceVersion: ""