apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-160-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-160.ec2.internal
      uid: 431eeb89-34bd-4f32-ad51-33178cd786d6
    resourceVersion: "23488"
    uid: 9e13f4dc-c181-4463-9d07-94ac7d55fbf1
  spec:
    sourcePod: network-check-source-6f8b768455-d7n9n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:36:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.175µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:43:04Z"
    - latency: 989.69µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:42:04Z"
    - latency: 826.658µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 854.11µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 1.343009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 1.022461ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 855.982µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:37:04Z"
    - latency: 854.384µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:36:04Z"
    - latency: 1.216168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:35:04Z"
    - latency: 1.481411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:34:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-160-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-160.ec2.internal
      uid: 431eeb89-34bd-4f32-ad51-33178cd786d6
    resourceVersion: "22467"
    uid: ddf49ede-2738-462a-b529-f8471bc2a7ef
  spec:
    sourcePod: network-check-source-6f8b768455-d7n9n
    targetEndpoint: a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:35:04Z"
      message: 'load-balancer-api-external: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.886079ms
      message: 'load-balancer-api-external: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 8.514679ms
      message: 'load-balancer-api-external: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 5.00567ms
      message: 'load-balancer-api-external: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 8.523943ms
      message: 'load-balancer-api-external: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 5.209696ms
      message: 'load-balancer-api-external: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 7.693952ms
      message: 'load-balancer-api-external: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 5.010424ms
      message: 'load-balancer-api-external: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 7.777602ms
      message: 'load-balancer-api-external: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 4.141948ms
      message: 'load-balancer-api-external: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:37:04Z"
    - latency: 7.832009ms
      message: 'load-balancer-api-external: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:37:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-160-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-160.ec2.internal
      uid: 431eeb89-34bd-4f32-ad51-33178cd786d6
    resourceVersion: "22468"
    uid: 98f673c9-d28e-42ce-9658-fac1e5e2ee32
  spec:
    sourcePod: network-check-source-6f8b768455-d7n9n
    targetEndpoint: a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:35:04Z"
      message: 'load-balancer-api-internal: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.384537ms
      message: 'load-balancer-api-internal: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 8.554237ms
      message: 'load-balancer-api-internal: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 4.356178ms
      message: 'load-balancer-api-internal: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 8.556927ms
      message: 'load-balancer-api-internal: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 5.159142ms
      message: 'load-balancer-api-internal: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 7.72465ms
      message: 'load-balancer-api-internal: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 8.777581ms
      message: 'load-balancer-api-internal: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 7.813305ms
      message: 'load-balancer-api-internal: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 4.151396ms
      message: 'load-balancer-api-internal: tcp connection to a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:37:04Z"
    - latency: 7.851836ms
      message: 'load-balancer-api-internal: resolved host name a4367eb2924f84da38075372ad6eebce-60007d4ace3fd505.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:37:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-160-to-network-check-target-ip-10-0-131-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-160.ec2.internal
      uid: 431eeb89-34bd-4f32-ad51-33178cd786d6
    resourceVersion: "23486"
    uid: 746028b0-1dab-4b89-bb9e-d1020e848af4
  spec:
    sourcePod: network-check-source-6f8b768455-d7n9n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:36:04Z"
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.277095ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:43:04Z"
    - latency: 2.4121ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:42:04Z"
    - latency: 2.392321ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 2.441146ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 2.163462ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 2.782633ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 2.423481ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:37:04Z"
    - latency: 1.960845ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:36:04Z"
    - latency: 2.542764ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:35:04Z"
    - latency: 2.668169ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:34:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-160-to-network-check-target-ip-10-0-131-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-160.ec2.internal
      uid: 431eeb89-34bd-4f32-ad51-33178cd786d6
    resourceVersion: "23485"
    uid: 6b4c274e-6887-49bd-83a5-4fa957d938ce
  spec:
    sourcePod: network-check-source-6f8b768455-d7n9n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:36:04Z"
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 728.066µs
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:43:04Z"
    - latency: 785.738µs
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:42:04Z"
    - latency: 1.252099ms
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 1.33575ms
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 752.241µs
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 863.636µs
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 683.826µs
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:37:04Z"
    - latency: 787.174µs
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:36:04Z"
    - latency: 1.031296ms
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:35:04Z"
    - latency: 1.796777ms
      message: 'network-check-target-ip-10-0-131-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:34:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-160-to-network-check-target-ip-10-0-135-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-160.ec2.internal
      uid: 431eeb89-34bd-4f32-ad51-33178cd786d6
    resourceVersion: "23487"
    uid: d1c27d88-13c5-4fb8-8b98-d0fa196f8b96
  spec:
    sourcePod: network-check-source-6f8b768455-d7n9n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:36:04Z"
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.211419ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:43:04Z"
    - latency: 2.059669ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:42:04Z"
    - latency: 2.044844ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 2.278077ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 2.070585ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 2.325658ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 2.196305ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:37:04Z"
    - latency: 1.956322ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:36:04Z"
    - latency: 2.582644ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:35:04Z"
    - latency: 2.578697ms
      message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:34:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-160-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-160.ec2.internal
      uid: 431eeb89-34bd-4f32-ad51-33178cd786d6
    resourceVersion: "22466"
    uid: dbf81f55-166a-4e17-aa76-b327d709a4b6
  spec:
    sourcePod: network-check-source-6f8b768455-d7n9n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:35:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.819µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 1.862412ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:41:04Z"
    - latency: 932.408µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 1.722512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:40:04Z"
    - latency: 921.167µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 2.052759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:39:04Z"
    - latency: 1.018912ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 1.820243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:38:04Z"
    - latency: 1.134507ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T16:37:04Z"
    - latency: 1.774676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T16:37:04Z"
kind: List
metadata:
  resourceVersion: ""