apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 47fbddb9-b4c7-476a-bec9-87e54e62895f
    resourceVersion: "35470"
    uid: 067890fb-96f6-4a46-b558-929c273ceac7
  spec:
    sourcePod: network-check-source-6f8b768455-bwcjv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.313085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:26Z"
    - latency: 983.757µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:26Z"
    - latency: 928.904µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:26Z"
    - latency: 943.721µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:26Z"
    - latency: 961.068µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:26Z"
    - latency: 924.541µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:26Z"
    - latency: 1.036721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:26Z"
    - latency: 938.31µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:26Z"
    - latency: 1.032227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:26Z"
    - latency: 1.061881ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 47fbddb9-b4c7-476a-bec9-87e54e62895f
    resourceVersion: "38871"
    uid: 9f28aeee-7d8b-4acd-b807-afcf091e4ca8
  spec:
    sourcePod: network-check-source-6f8b768455-bwcjv
    targetEndpoint: a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:26Z"
      message: 'load-balancer-api-external: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.817441ms
      message: 'load-balancer-api-external: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:26Z"
    - latency: 7.004373ms
      message: 'load-balancer-api-external: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:37:26Z"
    - latency: 4.510642ms
      message: 'load-balancer-api-external: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:26Z"
    - latency: 9.304157ms
      message: 'load-balancer-api-external: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:36:26Z"
    - latency: 19.095839ms
      message: 'load-balancer-api-external: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:26Z"
    - latency: 5.996456ms
      message: 'load-balancer-api-external: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:35:26Z"
    - latency: 5.803311ms
      message: 'load-balancer-api-external: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:26Z"
    - latency: 6.659409ms
      message: 'load-balancer-api-external: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:26Z"
    - latency: 5.429331ms
      message: 'load-balancer-api-external: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:26Z"
    - latency: 6.343536ms
      message: 'load-balancer-api-external: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 47fbddb9-b4c7-476a-bec9-87e54e62895f
    resourceVersion: "38870"
    uid: 753d546e-7b4e-45d3-95f9-bcf6a2142fc2
  spec:
    sourcePod: network-check-source-6f8b768455-bwcjv
    targetEndpoint: a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:26Z"
      message: 'load-balancer-api-internal: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.872206ms
      message: 'load-balancer-api-internal: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:26Z"
    - latency: 6.898308ms
      message: 'load-balancer-api-internal: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:37:26Z"
    - latency: 4.81306ms
      message: 'load-balancer-api-internal: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:26Z"
    - latency: 9.229138ms
      message: 'load-balancer-api-internal: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:36:26Z"
    - latency: 4.879618ms
      message: 'load-balancer-api-internal: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:26Z"
    - latency: 5.955941ms
      message: 'load-balancer-api-internal: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:35:26Z"
    - latency: 5.787587ms
      message: 'load-balancer-api-internal: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:26Z"
    - latency: 6.624637ms
      message: 'load-balancer-api-internal: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:26Z"
    - latency: 5.426622ms
      message: 'load-balancer-api-internal: tcp connection to a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:26Z"
    - latency: 6.301189ms
      message: 'load-balancer-api-internal: resolved host name a0549aa33c58a471899b1a559b8444c3-6b85319b34939204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-network-check-target-ip-10-0-135-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 47fbddb9-b4c7-476a-bec9-87e54e62895f
    resourceVersion: "35468"
    uid: 49b333f3-7830-4e92-8464-2e3c9355cc0b
  spec:
    sourcePod: network-check-source-6f8b768455-bwcjv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:26Z"
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.809095ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:26Z"
    - latency: 3.095766ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:26Z"
    - latency: 2.514948ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:26Z"
    - latency: 2.430863ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:26Z"
    - latency: 2.14035ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:26Z"
    - latency: 3.035544ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:26Z"
    - latency: 2.41362ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:26Z"
    - latency: 2.546643ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:26Z"
    - latency: 2.743865ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:26Z"
    - latency: 2.345677ms
      message: 'network-check-target-ip-10-0-135-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-network-check-target-ip-10-0-142-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 47fbddb9-b4c7-476a-bec9-87e54e62895f
    resourceVersion: "35466"
    uid: 42a042ee-ade5-439d-9798-11c1ba51db3b
  spec:
    sourcePod: network-check-source-6f8b768455-bwcjv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:26Z"
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.8652ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:26Z"
    - latency: 2.527852ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:26Z"
    - latency: 3.008476ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:26Z"
    - latency: 2.448573ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:26Z"
    - latency: 1.965991ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:26Z"
    - latency: 2.050073ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:26Z"
    - latency: 2.580317ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:26Z"
    - latency: 3.005282ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:26Z"
    - latency: 2.469881ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:26Z"
    - latency: 1.869343ms
      message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-network-check-target-ip-10-0-143-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 47fbddb9-b4c7-476a-bec9-87e54e62895f
    resourceVersion: "35467"
    uid: dcbb2109-9d3e-42d2-a74d-7bf6dddc4151
  spec:
    sourcePod: network-check-source-6f8b768455-bwcjv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:56:26Z"
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.569552ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:26Z"
    - latency: 944.714µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:26Z"
    - latency: 956.994µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:26Z"
    - latency: 964.821µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:26Z"
    - latency: 819.519µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:26Z"
    - latency: 1.326269ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:26Z"
    - latency: 897.889µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:26Z"
    - latency: 1.525627ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:26Z"
    - latency: 965.061µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:26Z"
    - latency: 1.480667ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 47fbddb9-b4c7-476a-bec9-87e54e62895f
    resourceVersion: "38869"
    uid: a61ffc95-f013-4943-a3a8-a399dd98bd47
  spec:
    sourcePod: network-check-source-6f8b768455-bwcjv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 984.041µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:37:26Z"
    - latency: 2.164934ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:37:26Z"
    - latency: 1.558515ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:36:26Z"
    - latency: 1.901587ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:36:26Z"
    - latency: 1.095548ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:35:26Z"
    - latency: 1.974275ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:35:26Z"
    - latency: 938.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:34:26Z"
    - latency: 1.528936ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:34:26Z"
    - latency: 877.608µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:26Z"
    - latency: 2.226019ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:26Z"
kind: List
metadata:
  resourceVersion: ""