apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-85-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-85.ec2.internal
      uid: ace307d5-23ae-4ad6-be99-699f94c5b4f5
    resourceVersion: "38139"
    uid: 246b6597-33b5-4f44-8664-db25d73f2067
  spec:
    sourcePod: network-check-source-8894fc9bd-452lr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:48:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.233µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:44:52Z"
    - latency: 1.199572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:43:52Z"
    - latency: 1.330259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:42:52Z"
    - latency: 1.060243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 1.113084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 808.228µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 759.204µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 1.285001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:37:52Z"
    - latency: 922.771µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:36:52Z"
    - latency: 1.006651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-85-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-85.ec2.internal
      uid: ace307d5-23ae-4ad6-be99-699f94c5b4f5
    resourceVersion: "36921"
    uid: ceaf0d1c-42af-40b2-8273-f2e03d197dc1
  spec:
    sourcePod: network-check-source-8894fc9bd-452lr
    targetEndpoint: ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:47:52Z"
      message: 'load-balancer-api-external: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.919206ms
      message: 'load-balancer-api-external: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 6.542115ms
      message: 'load-balancer-api-external: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 5.454252ms
      message: 'load-balancer-api-external: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 7.449669ms
      message: 'load-balancer-api-external: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 4.409851ms
      message: 'load-balancer-api-external: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 17.150114ms
      message: 'load-balancer-api-external: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 5.876658ms
      message: 'load-balancer-api-external: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 9.052692ms
      message: 'load-balancer-api-external: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 5.615877ms
      message: 'load-balancer-api-external: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:37:52Z"
    - latency: 10.62842ms
      message: 'load-balancer-api-external: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:37:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-85-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-85.ec2.internal
      uid: ace307d5-23ae-4ad6-be99-699f94c5b4f5
    resourceVersion: "36920"
    uid: 2b6fee9d-7ba0-4d95-b3f2-a66aacb13091
  spec:
    sourcePod: network-check-source-8894fc9bd-452lr
    targetEndpoint: ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:47:52Z"
      message: 'load-balancer-api-internal: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.910363ms
      message: 'load-balancer-api-internal: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 6.574103ms
      message: 'load-balancer-api-internal: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 5.205602ms
      message: 'load-balancer-api-internal: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 7.405111ms
      message: 'load-balancer-api-internal: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 4.398745ms
      message: 'load-balancer-api-internal: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 17.098353ms
      message: 'load-balancer-api-internal: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 4.941925ms
      message: 'load-balancer-api-internal: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 9.003623ms
      message: 'load-balancer-api-internal: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 5.426629ms
      message: 'load-balancer-api-internal: tcp connection to ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:37:52Z"
    - latency: 10.646131ms
      message: 'load-balancer-api-internal: resolved host name ab529ce1a2d38443a8d8fd8296197706-bf87a9218e9e9494.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:37:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-85-to-network-check-target-ip-10-0-131-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-85.ec2.internal
      uid: ace307d5-23ae-4ad6-be99-699f94c5b4f5
    resourceVersion: "38137"
    uid: 7b6c1aa4-7f38-4858-8bab-459693a7df9c
  spec:
    sourcePod: network-check-source-8894fc9bd-452lr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:48:52Z"
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.062718ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:44:52Z"
    - latency: 2.194462ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:43:52Z"
    - latency: 2.692506ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:42:52Z"
    - latency: 2.20136ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 2.52826ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 2.035286ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 1.813255ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 2.473385ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:37:52Z"
    - latency: 2.243869ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:36:52Z"
    - latency: 2.235799ms
      message: 'network-check-target-ip-10-0-131-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-85-to-network-check-target-ip-10-0-131-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-85.ec2.internal
      uid: ace307d5-23ae-4ad6-be99-699f94c5b4f5
    resourceVersion: "38136"
    uid: 024d17f7-63c0-44d0-9023-25cbd02e60b1
  spec:
    sourcePod: network-check-source-8894fc9bd-452lr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:48:52Z"
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.019595ms
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:44:52Z"
    - latency: 828.838µs
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:43:52Z"
    - latency: 825.995µs
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:42:52Z"
    - latency: 794.816µs
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 962.137µs
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 768.484µs
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 1.119974ms
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 1.147222ms
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:37:52Z"
    - latency: 1.278837ms
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:36:52Z"
    - latency: 863.781µs
      message: 'network-check-target-ip-10-0-131-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-85-to-network-check-target-ip-10-0-134-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-85.ec2.internal
      uid: ace307d5-23ae-4ad6-be99-699f94c5b4f5
    resourceVersion: "38138"
    uid: f7fcf050-8cb8-4fbf-a951-eb67bb85e38f
  spec:
    sourcePod: network-check-source-8894fc9bd-452lr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:48:52Z"
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.206286ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:44:52Z"
    - latency: 2.440506ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:43:52Z"
    - latency: 2.255217ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:42:52Z"
    - latency: 1.802816ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 2.427126ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 2.259854ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 2.380466ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 2.02249ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:37:52Z"
    - latency: 2.046347ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:36:52Z"
    - latency: 2.04356ms
      message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T18:41:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-85-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-85.ec2.internal
      uid: ace307d5-23ae-4ad6-be99-699f94c5b4f5
    resourceVersion: "36919"
    uid: bcdc72a9-53ef-4144-bb3a-4269388c1b2a
  spec:
    sourcePod: network-check-source-8894fc9bd-452lr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T18:47:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.250984ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 1.666845ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:41:52Z"
    - latency: 736.35µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 1.731282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:40:52Z"
    - latency: 1.027795ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 1.664111ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:39:52Z"
    - latency: 1.139095ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 1.54685ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:38:52Z"
    - latency: 1.395537ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:37:52Z"
    - latency: 1.914477ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:37:52Z"
kind: List
metadata:
  resourceVersion: ""