apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:43:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-35-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-35.ec2.internal
      uid: f64022aa-b716-4078-9888-dff0054c3fb0
    resourceVersion: "21963"
    uid: 0dfe592a-3363-4150-ace6-9aa227970353
  spec:
    sourcePod: network-check-source-56499946bc-h4jq8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:50:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.029µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:04:13Z"
    - latency: 1.009588ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:03:13Z"
    - latency: 850.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:02:13Z"
    - latency: 1.374184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 1.159864ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 877.163µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 1.057789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 1.059732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:13Z"
    - latency: 1.113891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:13Z"
    - latency: 1.156621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:55:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:43:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-35-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-35.ec2.internal
      uid: f64022aa-b716-4078-9888-dff0054c3fb0
    resourceVersion: "20474"
    uid: 8484a142-2bfd-4494-ba5c-237ddd6472b4
  spec:
    sourcePod: network-check-source-56499946bc-h4jq8
    targetEndpoint: ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:49:13Z"
      message: 'load-balancer-api-external: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.937696ms
      message: 'load-balancer-api-external: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 8.636248ms
      message: 'load-balancer-api-external: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 5.485314ms
      message: 'load-balancer-api-external: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 8.933505ms
      message: 'load-balancer-api-external: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 5.145448ms
      message: 'load-balancer-api-external: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 8.366961ms
      message: 'load-balancer-api-external: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 5.521004ms
      message: 'load-balancer-api-external: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 10.449868ms
      message: 'load-balancer-api-external: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 5.630718ms
      message: 'load-balancer-api-external: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:13Z"
    - latency: 9.644767ms
      message: 'load-balancer-api-external: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:57:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:43:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-35-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-35.ec2.internal
      uid: f64022aa-b716-4078-9888-dff0054c3fb0
    resourceVersion: "20475"
    uid: 0759479a-1617-47e4-9b2f-444014a5d782
  spec:
    sourcePod: network-check-source-56499946bc-h4jq8
    targetEndpoint: ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:49:13Z"
      message: 'load-balancer-api-internal: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.735534ms
      message: 'load-balancer-api-internal: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 8.706794ms
      message: 'load-balancer-api-internal: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 4.980491ms
      message: 'load-balancer-api-internal: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 8.843402ms
      message: 'load-balancer-api-internal: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 4.073284ms
      message: 'load-balancer-api-internal: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 8.403852ms
      message: 'load-balancer-api-internal: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 5.50055ms
      message: 'load-balancer-api-internal: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 10.359864ms
      message: 'load-balancer-api-internal: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 5.655984ms
      message: 'load-balancer-api-internal: tcp connection to ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:13Z"
    - latency: 9.619394ms
      message: 'load-balancer-api-internal: resolved host name ab709ebe6fc254d1289e195fda9318aa-72906e6e972e15c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:57:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:43:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-35-to-network-check-target-ip-10-0-128-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-35.ec2.internal
      uid: f64022aa-b716-4078-9888-dff0054c3fb0
    resourceVersion: "21961"
    uid: 6d190a8c-e027-4a3d-a274-44798142a911
  spec:
    sourcePod: network-check-source-56499946bc-h4jq8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:50:13Z"
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.280704ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:04:13Z"
    - latency: 2.100866ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:03:13Z"
    - latency: 2.439249ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:02:13Z"
    - latency: 2.149153ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 2.004095ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 1.972982ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 2.05149ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 1.999348ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:13Z"
    - latency: 2.257723ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:13Z"
    - latency: 2.358357ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:55:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:43:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-35-to-network-check-target-ip-10-0-136-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-35.ec2.internal
      uid: f64022aa-b716-4078-9888-dff0054c3fb0
    resourceVersion: "21960"
    uid: 4190ad38-1a3e-4607-9829-f87fc47eaa90
  spec:
    sourcePod: network-check-source-56499946bc-h4jq8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:50:13Z"
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.462081ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:04:13Z"
    - latency: 979.753µs
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:03:13Z"
    - latency: 1.035046ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:02:13Z"
    - latency: 1.046471ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 913.291µs
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 1.008018ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 833.152µs
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 1.275245ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:13Z"
    - latency: 1.026414ms
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:13Z"
    - latency: 839.89µs
      message: 'network-check-target-ip-10-0-136-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:55:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:43:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-35-to-network-check-target-ip-10-0-143-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-35.ec2.internal
      uid: f64022aa-b716-4078-9888-dff0054c3fb0
    resourceVersion: "21962"
    uid: 6c42831a-856d-4267-aa22-c6640f57f13c
  spec:
    sourcePod: network-check-source-56499946bc-h4jq8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:50:13Z"
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.234283ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:04:13Z"
    - latency: 2.10408ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:03:13Z"
    - latency: 2.100659ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:02:13Z"
    - latency: 2.452148ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 1.990071ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 2.517854ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 2.264687ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 1.954608ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:13Z"
    - latency: 2.065068ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:56:13Z"
    - latency: 1.977813ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:55:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T14:43:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-35-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-35.ec2.internal
      uid: f64022aa-b716-4078-9888-dff0054c3fb0
    resourceVersion: "20472"
    uid: f32a12c0-3853-4c47-ac4d-6a85247d862a
  spec:
    sourcePod: network-check-source-56499946bc-h4jq8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T14:49:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.271158ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 1.748778ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T15:01:13Z"
    - latency: 821.701µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 1.913625ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T15:00:13Z"
    - latency: 871.525µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 1.937063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:59:13Z"
    - latency: 806.093µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 2.400099ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:58:13Z"
    - latency: 1.156045ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T14:57:13Z"
    - latency: 1.838054ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T14:57:13Z"
kind: List
metadata:
  resourceVersion: ""