apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T22:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-241-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-241.ec2.internal
      uid: 6954ed48-4309-415c-add2-be4b012a2997
    resourceVersion: "47818"
    uid: 1446c8d7-ab9b-429d-9e7e-20309a337d4e
  spec:
    sourcePod: network-check-source-869dcfcdcd-mzbjr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T22:23:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.273713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 811.214µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 934.312µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:42:46Z"
    - latency: 747.084µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:41:46Z"
    - latency: 1.324334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:40:46Z"
    - latency: 900.293µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:39:46Z"
    - latency: 972.199µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:38:46Z"
    - latency: 984.833µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:37:46Z"
    - latency: 1.478875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:36:46Z"
    - latency: 939.931µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:35:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T22:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-241-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-241.ec2.internal
      uid: 6954ed48-4309-415c-add2-be4b012a2997
    resourceVersion: "50399"
    uid: 2cc9c2ec-b436-4d79-815f-24934f4ca0b4
  spec:
    sourcePod: network-check-source-869dcfcdcd-mzbjr
    targetEndpoint: a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T22:22:46Z"
      message: 'load-balancer-api-external: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.256274ms
      message: 'load-balancer-api-external: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:46:46Z"
    - latency: 8.997792ms
      message: 'load-balancer-api-external: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:46:46Z"
    - latency: 5.379051ms
      message: 'load-balancer-api-external: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:45:46Z"
    - latency: 7.071367ms
      message: 'load-balancer-api-external: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:45:46Z"
    - latency: 5.361808ms
      message: 'load-balancer-api-external: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 7.175227ms
      message: 'load-balancer-api-external: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 4.413054ms
      message: 'load-balancer-api-external: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 7.03541ms
      message: 'load-balancer-api-external: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 5.26306ms
      message: 'load-balancer-api-external: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:42:46Z"
    - latency: 7.060409ms
      message: 'load-balancer-api-external: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:42:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T22:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-241-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-241.ec2.internal
      uid: 6954ed48-4309-415c-add2-be4b012a2997
    resourceVersion: "50400"
    uid: f456bac3-fe33-44ab-82be-68751f2b0898
  spec:
    sourcePod: network-check-source-869dcfcdcd-mzbjr
    targetEndpoint: a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T22:22:46Z"
      message: 'load-balancer-api-internal: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.315399ms
      message: 'load-balancer-api-internal: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:46:46Z"
    - latency: 8.92474ms
      message: 'load-balancer-api-internal: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:46:46Z"
    - latency: 5.343318ms
      message: 'load-balancer-api-internal: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:45:46Z"
    - latency: 7.175433ms
      message: 'load-balancer-api-internal: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:45:46Z"
    - latency: 5.301985ms
      message: 'load-balancer-api-internal: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 7.260661ms
      message: 'load-balancer-api-internal: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 4.73664ms
      message: 'load-balancer-api-internal: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 7.133776ms
      message: 'load-balancer-api-internal: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 5.232842ms
      message: 'load-balancer-api-internal: tcp connection to a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:42:46Z"
    - latency: 7.187653ms
      message: 'load-balancer-api-internal: resolved host name a9113b5ea0dfc42288981e4b8293d934-fec99fb4847ad9b7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:42:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T22:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-241-to-network-check-target-ip-10-0-132-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-241.ec2.internal
      uid: 6954ed48-4309-415c-add2-be4b012a2997
    resourceVersion: "47816"
    uid: 3ca42f1f-9ee9-47e6-8ab2-554cc223271c
  spec:
    sourcePod: network-check-source-869dcfcdcd-mzbjr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T22:23:46Z"
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.532162ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 2.408239ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 2.248406ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:42:46Z"
    - latency: 2.424974ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:41:46Z"
    - latency: 2.231769ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:40:46Z"
    - latency: 2.399644ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:39:46Z"
    - latency: 2.312239ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:38:46Z"
    - latency: 2.519662ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:37:46Z"
    - latency: 2.118787ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:36:46Z"
    - latency: 2.318666ms
      message: 'network-check-target-ip-10-0-132-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:35:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T22:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-241-to-network-check-target-ip-10-0-133-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-241.ec2.internal
      uid: 6954ed48-4309-415c-add2-be4b012a2997
    resourceVersion: "47817"
    uid: 133f3a67-16ae-452f-974f-b7ca34612930
  spec:
    sourcePod: network-check-source-869dcfcdcd-mzbjr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T22:23:46Z"
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.893996ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 2.281749ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 2.405523ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:42:46Z"
    - latency: 2.716971ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:41:46Z"
    - latency: 2.341298ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:40:46Z"
    - latency: 2.420676ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:39:46Z"
    - latency: 2.434715ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:38:46Z"
    - latency: 2.380238ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:37:46Z"
    - latency: 2.38258ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:36:46Z"
    - latency: 2.192116ms
      message: 'network-check-target-ip-10-0-133-179: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:35:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T22:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-241-to-network-check-target-ip-10-0-137-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-241.ec2.internal
      uid: 6954ed48-4309-415c-add2-be4b012a2997
    resourceVersion: "47815"
    uid: 688def61-e369-4727-8af2-adeb2c83796d
  spec:
    sourcePod: network-check-source-869dcfcdcd-mzbjr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T22:23:46Z"
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.595311ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 1.202607ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 1.059714ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:42:46Z"
    - latency: 1.465223ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:41:46Z"
    - latency: 1.515278ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:40:46Z"
    - latency: 927.831µs
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:39:46Z"
    - latency: 1.431781ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:38:46Z"
    - latency: 924.378µs
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:37:46Z"
    - latency: 779.465µs
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:36:46Z"
    - latency: 742.009µs
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:35:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T22:16:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-241-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-241.ec2.internal
      uid: 6954ed48-4309-415c-add2-be4b012a2997
    resourceVersion: "50398"
    uid: 8e382536-6086-4812-a229-a1f697a5ec08
  spec:
    sourcePod: network-check-source-869dcfcdcd-mzbjr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T22:22:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.479µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:46:46Z"
    - latency: 1.95783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:46:46Z"
    - latency: 1.484614ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:45:46Z"
    - latency: 1.720811ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:45:46Z"
    - latency: 1.337938ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 1.862546ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:44:46Z"
    - latency: 817.76µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 1.676209ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:43:46Z"
    - latency: 854.05µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:42:46Z"
    - latency: 1.765307ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:42:46Z"
kind: List
metadata:
  resourceVersion: ""