apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-47-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-47.ec2.internal
      uid: 7bbd91f2-06cf-4e5d-93be-78696c2e35b3
    resourceVersion: "63376"
    uid: 4d1220f4-b1e0-4551-ba08-72e767ce150f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-chbv4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:32:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 1.240101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 1.111825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 939.135µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 1.716949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:39Z"
    - latency: 960.821µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:02:39Z"
    - latency: 1.217894ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:01:39Z"
    - latency: 1.241109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:00:39Z"
    - latency: 1.234232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:59:39Z"
    - latency: 1.131728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:58:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-47-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-47.ec2.internal
      uid: 7bbd91f2-06cf-4e5d-93be-78696c2e35b3
    resourceVersion: "63379"
    uid: 58cce359-c3a9-4016-aa32-2744ebe5da7f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-chbv4
    targetEndpoint: a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:31:39Z"
      message: 'load-balancer-api-external: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.831855ms
      message: 'load-balancer-api-external: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 7.636679ms
      message: 'load-balancer-api-external: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 4.733747ms
      message: 'load-balancer-api-external: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 6.929608ms
      message: 'load-balancer-api-external: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 5.116614ms
      message: 'load-balancer-api-external: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 7.726786ms
      message: 'load-balancer-api-external: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 3.500862ms
      message: 'load-balancer-api-external: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 7.14544ms
      message: 'load-balancer-api-external: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 4.751982ms
      message: 'load-balancer-api-external: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:39Z"
    - latency: 6.696281ms
      message: 'load-balancer-api-external: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:03:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-47-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-47.ec2.internal
      uid: 7bbd91f2-06cf-4e5d-93be-78696c2e35b3
    resourceVersion: "63378"
    uid: 4fb60420-958e-4f83-82ad-350f0705a7d2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-chbv4
    targetEndpoint: a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:31:39Z"
      message: 'load-balancer-api-internal: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.858169ms
      message: 'load-balancer-api-internal: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 7.617576ms
      message: 'load-balancer-api-internal: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 5.355297ms
      message: 'load-balancer-api-internal: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 6.946256ms
      message: 'load-balancer-api-internal: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 5.110069ms
      message: 'load-balancer-api-internal: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 7.83638ms
      message: 'load-balancer-api-internal: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 5.074729ms
      message: 'load-balancer-api-internal: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 7.073357ms
      message: 'load-balancer-api-internal: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 4.84328ms
      message: 'load-balancer-api-internal: tcp connection to a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:39Z"
    - latency: 6.671504ms
      message: 'load-balancer-api-internal: resolved host name a98698c1ecbe3442d888ed3b69459859-2903918b4080fa42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:03:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-47-to-network-check-target-ip-10-0-133-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-47.ec2.internal
      uid: 7bbd91f2-06cf-4e5d-93be-78696c2e35b3
    resourceVersion: "63374"
    uid: 46b1719c-c3b4-4ef7-8710-ad6bf8aaaf3c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-chbv4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:32:39Z"
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.172569ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 1.006333ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 971.924µs
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 1.077327ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 1.139489ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:39Z"
    - latency: 1.013798ms
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:02:39Z"
    - latency: 931.699µs
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:01:39Z"
    - latency: 997.744µs
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:00:39Z"
    - latency: 921.768µs
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:59:39Z"
    - latency: 838.867µs
      message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:58:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-47-to-network-check-target-ip-10-0-138-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-47.ec2.internal
      uid: 7bbd91f2-06cf-4e5d-93be-78696c2e35b3
    resourceVersion: "63375"
    uid: 85af293b-999a-4149-b99b-07c0549a9767
  spec:
    sourcePod: network-check-source-7bc5b6bf85-chbv4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:32:39Z"
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.038384ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 2.587562ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 2.338861ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 2.251891ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 2.370249ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:39Z"
    - latency: 2.135303ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:02:39Z"
    - latency: 2.999448ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:01:39Z"
    - latency: 2.413313ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:00:39Z"
    - latency: 2.224473ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:59:39Z"
    - latency: 2.467308ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:58:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-47-to-network-check-target-ip-10-0-142-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-47.ec2.internal
      uid: 7bbd91f2-06cf-4e5d-93be-78696c2e35b3
    resourceVersion: "63373"
    uid: 6d7ebb9f-0f1a-4b5c-9492-566fa51c43c5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-chbv4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:32:39Z"
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.00875ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 1.916267ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 2.546331ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 2.23273ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 2.033557ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:39Z"
    - latency: 2.032931ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:02:39Z"
    - latency: 2.210805ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:01:39Z"
    - latency: 2.043745ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:00:39Z"
    - latency: 1.847668ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:59:39Z"
    - latency: 2.524434ms
      message: 'network-check-target-ip-10-0-142-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:58:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-47-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-47.ec2.internal
      uid: 7bbd91f2-06cf-4e5d-93be-78696c2e35b3
    resourceVersion: "63377"
    uid: 3a2fc6da-e525-4fdf-9b32-545cffc8781e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-chbv4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:31:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 719.737µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 2.07826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:07:39Z"
    - latency: 936.002µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 2.08071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:06:39Z"
    - latency: 996.608µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 1.909034ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:05:39Z"
    - latency: 945.582µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 1.661463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:04:39Z"
    - latency: 974.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:39Z"
    - latency: 1.849438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:03:39Z"
kind: List
metadata:
  resourceVersion: ""