apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:35:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-157-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-157.ec2.internal
      uid: 4f214a18-7907-403f-a222-3f90bc6370a6
    resourceVersion: "59402"
    uid: 0377e37a-a9ce-4dbc-bbf2-c392f788fd52
  spec:
    sourcePod: network-check-source-869dcfcdcd-pm898
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:42:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 805.326µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 1.413071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 1.276112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 1.258499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 996.135µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:04Z"
    - latency: 1.099023ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:12:04Z"
    - latency: 1.196218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:11:04Z"
    - latency: 1.875755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:10:04Z"
    - latency: 1.036141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:09:04Z"
    - latency: 1.250097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:08:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:35:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-157-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-157.ec2.internal
      uid: 4f214a18-7907-403f-a222-3f90bc6370a6
    resourceVersion: "59403"
    uid: 0f907d0b-6103-4025-b07d-c37ed8d2a607
  spec:
    sourcePod: network-check-source-869dcfcdcd-pm898
    targetEndpoint: a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:41:04Z"
      message: 'load-balancer-api-external: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.995642ms
      message: 'load-balancer-api-external: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 7.084202ms
      message: 'load-balancer-api-external: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 3.345174ms
      message: 'load-balancer-api-external: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 8.063073ms
      message: 'load-balancer-api-external: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 3.527927ms
      message: 'load-balancer-api-external: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 8.229742ms
      message: 'load-balancer-api-external: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 4.800442ms
      message: 'load-balancer-api-external: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 6.789331ms
      message: 'load-balancer-api-external: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 4.718781ms
      message: 'load-balancer-api-external: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:04Z"
    - latency: 7.082289ms
      message: 'load-balancer-api-external: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:13:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:35:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-157-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-157.ec2.internal
      uid: 4f214a18-7907-403f-a222-3f90bc6370a6
    resourceVersion: "59404"
    uid: 9bc4c6c9-c1a1-496f-8933-0140485a7ea3
  spec:
    sourcePod: network-check-source-869dcfcdcd-pm898
    targetEndpoint: a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:41:04Z"
      message: 'load-balancer-api-internal: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.931453ms
      message: 'load-balancer-api-internal: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 7.131828ms
      message: 'load-balancer-api-internal: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 3.352156ms
      message: 'load-balancer-api-internal: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 8.1471ms
      message: 'load-balancer-api-internal: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 4.226556ms
      message: 'load-balancer-api-internal: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 8.304328ms
      message: 'load-balancer-api-internal: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 3.523149ms
      message: 'load-balancer-api-internal: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 6.875244ms
      message: 'load-balancer-api-internal: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 4.024653ms
      message: 'load-balancer-api-internal: tcp connection to a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:04Z"
    - latency: 7.057169ms
      message: 'load-balancer-api-internal: resolved host name a411a86cbab6b42c2bd71619d40c50ac-6bf3a4937386013d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:13:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:35:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-157-to-network-check-target-ip-10-0-131-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-157.ec2.internal
      uid: 4f214a18-7907-403f-a222-3f90bc6370a6
    resourceVersion: "59398"
    uid: 7329f93b-a376-4b00-a6a7-4fafbc9c0a77
  spec:
    sourcePod: network-check-source-869dcfcdcd-pm898
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:42:04Z"
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.864µs
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 856.591µs
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 1.174337ms
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 1.252226ms
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 1.418855ms
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:04Z"
    - latency: 1.289716ms
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:12:04Z"
    - latency: 915.287µs
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:11:04Z"
    - latency: 1.085256ms
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:10:04Z"
    - latency: 921.341µs
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:09:04Z"
    - latency: 1.506439ms
      message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:08:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:35:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-157-to-network-check-target-ip-10-0-136-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-157.ec2.internal
      uid: 4f214a18-7907-403f-a222-3f90bc6370a6
    resourceVersion: "59399"
    uid: 583e0afe-3308-4e0c-8a87-c281e137521c
  spec:
    sourcePod: network-check-source-869dcfcdcd-pm898
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:42:04Z"
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.170085ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 2.047999ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 2.125003ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 2.404826ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 2.229529ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:04Z"
    - latency: 2.318893ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:12:04Z"
    - latency: 2.166747ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:11:04Z"
    - latency: 2.381594ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:10:04Z"
    - latency: 2.356225ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:09:04Z"
    - latency: 2.212202ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:08:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:35:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-157-to-network-check-target-ip-10-0-140-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-157.ec2.internal
      uid: 4f214a18-7907-403f-a222-3f90bc6370a6
    resourceVersion: "59401"
    uid: 46a84959-ad43-4e4b-8c0a-12f4c97f2d6c
  spec:
    sourcePod: network-check-source-869dcfcdcd-pm898
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:42:04Z"
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.354898ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 2.093966ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 2.0928ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 2.456746ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 2.556285ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:04Z"
    - latency: 2.428123ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:12:04Z"
    - latency: 2.168469ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:11:04Z"
    - latency: 3.003264ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:10:04Z"
    - latency: 2.585199ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:09:04Z"
    - latency: 2.693079ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:08:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:35:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-157-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-157.ec2.internal
      uid: 4f214a18-7907-403f-a222-3f90bc6370a6
    resourceVersion: "59400"
    uid: 0a596cbe-4f83-4654-8030-1bd251e198cd
  spec:
    sourcePod: network-check-source-869dcfcdcd-pm898
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:41:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.966µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 1.672302ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:17:04Z"
    - latency: 931.452µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 2.196975ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:16:04Z"
    - latency: 838.794µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 1.710608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:15:04Z"
    - latency: 911.804µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 1.650257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:14:04Z"
    - latency: 878.8µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:04Z"
    - latency: 1.585889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:13:04Z"
kind: List
metadata:
  resourceVersion: ""