apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:34:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-40-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-40.ec2.internal
      uid: cd2b8dd3-06e0-4be6-a74e-75f76526709c
    resourceVersion: "55608"
    uid: a0d7ec6f-caa0-4a94-96e3-cf18e1984430
  spec:
    sourcePod: network-check-source-989f8b8dc-hx424
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:41:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.17027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 1.046976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 1.104897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 765.412µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:28Z"
    - latency: 1.182432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:05:28Z"
    - latency: 1.023347ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:04:28Z"
    - latency: 1.057812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:03:28Z"
    - latency: 892.935µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:02:28Z"
    - latency: 844.099µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:01:28Z"
    - latency: 1.019901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:00:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:34:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-40-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-40.ec2.internal
      uid: cd2b8dd3-06e0-4be6-a74e-75f76526709c
    resourceVersion: "56569"
    uid: 30e91db8-41f1-4868-8d8c-998737f1ca17
  spec:
    sourcePod: network-check-source-989f8b8dc-hx424
    targetEndpoint: a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:40:28Z"
      message: 'load-balancer-api-external: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.371943ms
      message: 'load-balancer-api-external: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:28Z"
    - latency: 11.565564ms
      message: 'load-balancer-api-external: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:10:28Z"
    - latency: 6.470188ms
      message: 'load-balancer-api-external: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 14.182185ms
      message: 'load-balancer-api-external: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 7.001566ms
      message: 'load-balancer-api-external: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 12.476521ms
      message: 'load-balancer-api-external: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 5.082174ms
      message: 'load-balancer-api-external: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 12.600779ms
      message: 'load-balancer-api-external: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 5.904766ms
      message: 'load-balancer-api-external: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:28Z"
    - latency: 10.217071ms
      message: 'load-balancer-api-external: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:06:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:34:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-40-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-40.ec2.internal
      uid: cd2b8dd3-06e0-4be6-a74e-75f76526709c
    resourceVersion: "56568"
    uid: 8d61fd7c-8621-46ae-b803-22d65573e944
  spec:
    sourcePod: network-check-source-989f8b8dc-hx424
    targetEndpoint: a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:40:28Z"
      message: 'load-balancer-api-internal: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.382557ms
      message: 'load-balancer-api-internal: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:28Z"
    - latency: 11.610785ms
      message: 'load-balancer-api-internal: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:10:28Z"
    - latency: 6.340872ms
      message: 'load-balancer-api-internal: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 14.105119ms
      message: 'load-balancer-api-internal: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 6.956214ms
      message: 'load-balancer-api-internal: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 12.544834ms
      message: 'load-balancer-api-internal: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 5.844621ms
      message: 'load-balancer-api-internal: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 12.615788ms
      message: 'load-balancer-api-internal: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 5.890677ms
      message: 'load-balancer-api-internal: tcp connection to a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:28Z"
    - latency: 10.077486ms
      message: 'load-balancer-api-internal: resolved host name a9f418da774044862908a87553263cf5-b0c8c8c4b9f37b72.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:06:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:34:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-40-to-network-check-target-ip-10-0-138-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-40.ec2.internal
      uid: cd2b8dd3-06e0-4be6-a74e-75f76526709c
    resourceVersion: "55605"
    uid: 1beec05d-b8ee-4836-8846-0b62da005932
  spec:
    sourcePod: network-check-source-989f8b8dc-hx424
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:41:28Z"
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.043904ms
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 1.431825ms
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 824.094µs
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 1.305922ms
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:28Z"
    - latency: 1.663204ms
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:05:28Z"
    - latency: 1.159845ms
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:04:28Z"
    - latency: 921.77µs
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:03:28Z"
    - latency: 1.12284ms
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:02:28Z"
    - latency: 1.098095ms
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:01:28Z"
    - latency: 1.339254ms
      message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:00:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:34:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-40-to-network-check-target-ip-10-0-142-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-40.ec2.internal
      uid: cd2b8dd3-06e0-4be6-a74e-75f76526709c
    resourceVersion: "55607"
    uid: ee0494fc-183f-4862-9060-6a05adcc08dd
  spec:
    sourcePod: network-check-source-989f8b8dc-hx424
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:41:28Z"
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.204357ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 2.609934ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 2.203314ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 2.103201ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:28Z"
    - latency: 2.526558ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:05:28Z"
    - latency: 2.360873ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:04:28Z"
    - latency: 2.254575ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:03:28Z"
    - latency: 2.29928ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:02:28Z"
    - latency: 1.930104ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:01:28Z"
    - latency: 2.203996ms
      message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:00:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:34:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-40-to-network-check-target-ip-10-0-143-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-40.ec2.internal
      uid: cd2b8dd3-06e0-4be6-a74e-75f76526709c
    resourceVersion: "55606"
    uid: f867c19f-0582-4c86-8d42-4c2233de6027
  spec:
    sourcePod: network-check-source-989f8b8dc-hx424
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:41:28Z"
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.559561ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 2.39899ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 2.47038ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 1.937145ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:28Z"
    - latency: 2.598068ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:05:28Z"
    - latency: 2.359217ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:04:28Z"
    - latency: 2.640349ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:03:28Z"
    - latency: 2.599483ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:02:28Z"
    - latency: 2.158626ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:01:28Z"
    - latency: 2.485993ms
      message: 'network-check-target-ip-10-0-143-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:00:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T19:34:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-40-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-40.ec2.internal
      uid: cd2b8dd3-06e0-4be6-a74e-75f76526709c
    resourceVersion: "56567"
    uid: 2ec59d01-8e1a-40ee-a27b-f954fd5dcc5d
  spec:
    sourcePod: network-check-source-989f8b8dc-hx424
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T19:40:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.519µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:10:28Z"
    - latency: 2.355754ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:10:28Z"
    - latency: 1.410351ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 2.095974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:09:28Z"
    - latency: 1.091985ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 1.84459ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:08:28Z"
    - latency: 1.263139ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 1.768884ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:07:28Z"
    - latency: 740.51µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T20:06:28Z"
    - latency: 1.6317ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T20:06:28Z"
kind: List
metadata:
  resourceVersion: ""