apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-192-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-192.ec2.internal
      uid: 1656c317-5667-4d17-a455-c25a77a16edf
    resourceVersion: "53547"
    uid: a38da556-0ff7-4c2b-a855-c125a20e764e
  spec:
    sourcePod: network-check-source-989f8b8dc-mlpj4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:08:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.732835ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 975.535µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 1.212291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 967.999µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:58Z"
    - latency: 1.270445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:32:58Z"
    - latency: 1.433973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:58Z"
    - latency: 1.493039ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:58Z"
    - latency: 1.256393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:58Z"
    - latency: 1.224373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:58Z"
    - latency: 1.154628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-192-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-192.ec2.internal
      uid: 1656c317-5667-4d17-a455-c25a77a16edf
    resourceVersion: "54566"
    uid: b728f5b1-942f-4740-ad99-4b95a4609807
  spec:
    sourcePod: network-check-source-989f8b8dc-mlpj4
    targetEndpoint: aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:07:58Z"
      message: 'load-balancer-api-external: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.079488ms
      message: 'load-balancer-api-external: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:37:58Z"
    - latency: 8.102754ms
      message: 'load-balancer-api-external: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:37:58Z"
    - latency: 6.476941ms
      message: 'load-balancer-api-external: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 8.363817ms
      message: 'load-balancer-api-external: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 4.183836ms
      message: 'load-balancer-api-external: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 8.323897ms
      message: 'load-balancer-api-external: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 4.011511ms
      message: 'load-balancer-api-external: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 7.398274ms
      message: 'load-balancer-api-external: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 6.259474ms
      message: 'load-balancer-api-external: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:58Z"
    - latency: 6.961873ms
      message: 'load-balancer-api-external: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:33:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-192-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-192.ec2.internal
      uid: 1656c317-5667-4d17-a455-c25a77a16edf
    resourceVersion: "54567"
    uid: 891b80cc-012b-4ec2-a4fa-4a7b23e186d6
  spec:
    sourcePod: network-check-source-989f8b8dc-mlpj4
    targetEndpoint: aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:07:58Z"
      message: 'load-balancer-api-internal: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.037539ms
      message: 'load-balancer-api-internal: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:37:58Z"
    - latency: 8.077835ms
      message: 'load-balancer-api-internal: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:37:58Z"
    - latency: 4.666159ms
      message: 'load-balancer-api-internal: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 8.401491ms
      message: 'load-balancer-api-internal: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 4.644759ms
      message: 'load-balancer-api-internal: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 8.067394ms
      message: 'load-balancer-api-internal: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 4.044244ms
      message: 'load-balancer-api-internal: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 7.458107ms
      message: 'load-balancer-api-internal: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 6.258323ms
      message: 'load-balancer-api-internal: tcp connection to aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:58Z"
    - latency: 7.043206ms
      message: 'load-balancer-api-internal: resolved host name aeaa90bff18d041d3abb48db3593c58c-74d874662ed22b1d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:33:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-192-to-network-check-target-ip-10-0-128-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-192.ec2.internal
      uid: 1656c317-5667-4d17-a455-c25a77a16edf
    resourceVersion: "53546"
    uid: 48d70ee5-183e-4753-a307-8cffe5e98282
  spec:
    sourcePod: network-check-source-989f8b8dc-mlpj4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:08:58Z"
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.226255ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 1.949706ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 2.260694ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 1.960165ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:58Z"
    - latency: 2.370326ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:32:58Z"
    - latency: 1.819212ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:58Z"
    - latency: 1.947383ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:58Z"
    - latency: 1.912118ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:58Z"
    - latency: 1.811149ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:58Z"
    - latency: 2.110616ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-192-to-network-check-target-ip-10-0-136-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-192.ec2.internal
      uid: 1656c317-5667-4d17-a455-c25a77a16edf
    resourceVersion: "53545"
    uid: a7cef8fa-453a-469b-82d2-4eb335c4e947
  spec:
    sourcePod: network-check-source-989f8b8dc-mlpj4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:08:58Z"
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.236577ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 2.454641ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 2.207346ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 1.957409ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:58Z"
    - latency: 2.935726ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:32:58Z"
    - latency: 2.184414ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:58Z"
    - latency: 1.882309ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:58Z"
    - latency: 2.083698ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:58Z"
    - latency: 1.739284ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:58Z"
    - latency: 2.407084ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-192-to-network-check-target-ip-10-0-140-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-192.ec2.internal
      uid: 1656c317-5667-4d17-a455-c25a77a16edf
    resourceVersion: "53544"
    uid: cab9e4d3-c817-40c5-a9f3-48515ac84d86
  spec:
    sourcePod: network-check-source-989f8b8dc-mlpj4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:08:58Z"
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.336877ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 986.352µs
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 1.162553ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 994.256µs
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:58Z"
    - latency: 1.92523ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:32:58Z"
    - latency: 855.006µs
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:31:58Z"
    - latency: 1.320123ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:30:58Z"
    - latency: 1.429371ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:29:58Z"
    - latency: 828.447µs
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:28:58Z"
    - latency: 798.178µs
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:27:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:01:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-192-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-192.ec2.internal
      uid: 1656c317-5667-4d17-a455-c25a77a16edf
    resourceVersion: "54565"
    uid: 1f19c81e-1ad2-44de-b950-c7a82f083b3a
  spec:
    sourcePod: network-check-source-989f8b8dc-mlpj4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:07:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 772.761µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:37:58Z"
    - latency: 2.167032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:37:58Z"
    - latency: 1.200658ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 2.292495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:36:58Z"
    - latency: 913.741µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 2.521442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:35:58Z"
    - latency: 951.251µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 2.310917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:34:58Z"
    - latency: 845.397µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:33:58Z"
    - latency: 2.31144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:33:58Z"
kind: List
metadata:
  resourceVersion: ""