apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T14:18:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-214-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-214.ec2.internal
      uid: e56c2c66-e01d-4e91-ad2b-b1b88a2f42bd
    resourceVersion: "31455"
    uid: 1f768086-10c9-44a1-a47f-c43167cb7eea
  spec:
    sourcePod: network-check-source-dbd9cf844-5rvxq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T14:25:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.228325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:32:21Z"
    - latency: 729.274µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:31:21Z"
    - latency: 1.377527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 839.674µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 1.078512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 1.062924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 1.069982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:26:21Z"
    - latency: 1.086485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:25:21Z"
    - latency: 1.127152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:24:21Z"
    - latency: 876.81µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:23:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T14:18:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-214-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-214.ec2.internal
      uid: e56c2c66-e01d-4e91-ad2b-b1b88a2f42bd
    resourceVersion: "29585"
    uid: ce0a6d77-10bb-43bc-a8fe-75bf9a0f3ac8
  spec:
    sourcePod: network-check-source-dbd9cf844-5rvxq
    targetEndpoint: a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T14:24:21Z"
      message: 'load-balancer-api-external: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.766294ms
      message: 'load-balancer-api-external: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 6.775914ms
      message: 'load-balancer-api-external: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 4.636845ms
      message: 'load-balancer-api-external: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 6.608222ms
      message: 'load-balancer-api-external: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 6.398439ms
      message: 'load-balancer-api-external: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 6.572281ms
      message: 'load-balancer-api-external: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 5.819185ms
      message: 'load-balancer-api-external: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 6.554892ms
      message: 'load-balancer-api-external: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 4.073425ms
      message: 'load-balancer-api-external: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:26:21Z"
    - latency: 7.30291ms
      message: 'load-balancer-api-external: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:26:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T14:18:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-214-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-214.ec2.internal
      uid: e56c2c66-e01d-4e91-ad2b-b1b88a2f42bd
    resourceVersion: "29586"
    uid: ca0f22d8-eeca-4089-84af-c0464662912e
  spec:
    sourcePod: network-check-source-dbd9cf844-5rvxq
    targetEndpoint: a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T14:24:21Z"
      message: 'load-balancer-api-internal: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.781938ms
      message: 'load-balancer-api-internal: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 6.819508ms
      message: 'load-balancer-api-internal: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 3.726633ms
      message: 'load-balancer-api-internal: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 6.690641ms
      message: 'load-balancer-api-internal: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 6.363722ms
      message: 'load-balancer-api-internal: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 6.560618ms
      message: 'load-balancer-api-internal: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 5.332291ms
      message: 'load-balancer-api-internal: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 6.485103ms
      message: 'load-balancer-api-internal: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 4.819886ms
      message: 'load-balancer-api-internal: tcp connection to a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:26:21Z"
    - latency: 7.313017ms
      message: 'load-balancer-api-internal: resolved host name a6dedc38897964961806efd72184d7d7-f96b305555c0b8e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:26:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T14:18:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-214-to-network-check-target-ip-10-0-128-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-214.ec2.internal
      uid: e56c2c66-e01d-4e91-ad2b-b1b88a2f42bd
    resourceVersion: "31452"
    uid: 0e72a424-7d48-46c1-85ad-b729fa75dbf9
  spec:
    sourcePod: network-check-source-dbd9cf844-5rvxq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T14:25:21Z"
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.003456ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:32:21Z"
    - latency: 1.241725ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:31:21Z"
    - latency: 903.548µs
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 888.385µs
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 917.279µs
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 966.015µs
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 886.195µs
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:26:21Z"
    - latency: 957.44µs
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:25:21Z"
    - latency: 891.078µs
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:24:21Z"
    - latency: 966.663µs
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:23:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T14:18:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-214-to-network-check-target-ip-10-0-129-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-214.ec2.internal
      uid: e56c2c66-e01d-4e91-ad2b-b1b88a2f42bd
    resourceVersion: "31454"
    uid: 5e86aaf1-5a25-4fc5-8b99-944dc05a9b14
  spec:
    sourcePod: network-check-source-dbd9cf844-5rvxq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T14:25:21Z"
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.311334ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:32:21Z"
    - latency: 2.021052ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:31:21Z"
    - latency: 2.255111ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 2.046745ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 2.09442ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 2.161781ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 2.390918ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:26:21Z"
    - latency: 1.936001ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:25:21Z"
    - latency: 2.337325ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:24:21Z"
    - latency: 1.902468ms
      message: 'network-check-target-ip-10-0-129-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:23:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T14:18:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-214-to-network-check-target-ip-10-0-138-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-214.ec2.internal
      uid: e56c2c66-e01d-4e91-ad2b-b1b88a2f42bd
    resourceVersion: "31453"
    uid: 94b5bac8-cf56-4413-9a48-e07b9fac212a
  spec:
    sourcePod: network-check-source-dbd9cf844-5rvxq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T14:25:21Z"
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.849591ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:32:21Z"
    - latency: 1.651725ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:31:21Z"
    - latency: 1.855967ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 1.656043ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 1.801166ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 1.838879ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 2.486493ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:26:21Z"
    - latency: 1.587237ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:25:21Z"
    - latency: 1.931387ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:24:21Z"
    - latency: 2.051729ms
      message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:23:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T14:18:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-214-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-214.ec2.internal
      uid: e56c2c66-e01d-4e91-ad2b-b1b88a2f42bd
    resourceVersion: "29584"
    uid: 22de3182-ff03-444a-80c3-a4e47c4c5328
  spec:
    sourcePod: network-check-source-dbd9cf844-5rvxq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T14:24:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 873.592µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 1.676485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:30:21Z"
    - latency: 1.049572ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 1.742671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:29:21Z"
    - latency: 861.422µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 1.787426ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:28:21Z"
    - latency: 1.195301ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 1.69782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:27:21Z"
    - latency: 795.067µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T14:26:21Z"
    - latency: 2.448933ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T14:26:21Z"
kind: List
metadata:
  resourceVersion: ""