apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: 9e677590-74dd-422f-8dd7-8df041ad6498
    resourceVersion: "51444"
    uid: bfd4ea17-a5cb-4edf-a00a-2aed7f828044
  spec:
    sourcePod: network-check-source-989f8b8dc-bb8gt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:20:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.302426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 987.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 1.26918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 1.025529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:06Z"
    - latency: 1.101599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:06Z"
    - latency: 730.878µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:06Z"
    - latency: 1.155275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:06Z"
    - latency: 1.348571ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:06Z"
    - latency: 811.591µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:06Z"
    - latency: 1.334257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: 9e677590-74dd-422f-8dd7-8df041ad6498
    resourceVersion: "52313"
    uid: f512bbdb-1cf4-40f3-b813-a0af9c2df3ef
  spec:
    sourcePod: network-check-source-989f8b8dc-bb8gt
    targetEndpoint: a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:19:06Z"
      message: 'load-balancer-api-external: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.130774ms
      message: 'load-balancer-api-external: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:06Z"
    - latency: 8.941822ms
      message: 'load-balancer-api-external: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:49:06Z"
    - latency: 3.816932ms
      message: 'load-balancer-api-external: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 8.900391ms
      message: 'load-balancer-api-external: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 5.594821ms
      message: 'load-balancer-api-external: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 8.637679ms
      message: 'load-balancer-api-external: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 4.928955ms
      message: 'load-balancer-api-external: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 9.394024ms
      message: 'load-balancer-api-external: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 4.882603ms
      message: 'load-balancer-api-external: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:06Z"
    - latency: 8.525503ms
      message: 'load-balancer-api-external: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: 9e677590-74dd-422f-8dd7-8df041ad6498
    resourceVersion: "52312"
    uid: 4c5a4d2a-39cf-4dc5-b51b-f4904881a882
  spec:
    sourcePod: network-check-source-989f8b8dc-bb8gt
    targetEndpoint: a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:19:06Z"
      message: 'load-balancer-api-internal: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.248983ms
      message: 'load-balancer-api-internal: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:06Z"
    - latency: 8.835567ms
      message: 'load-balancer-api-internal: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:49:06Z"
    - latency: 5.63352ms
      message: 'load-balancer-api-internal: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 8.845806ms
      message: 'load-balancer-api-internal: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 3.493221ms
      message: 'load-balancer-api-internal: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 8.695826ms
      message: 'load-balancer-api-internal: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 4.873093ms
      message: 'load-balancer-api-internal: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 9.333985ms
      message: 'load-balancer-api-internal: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 4.912963ms
      message: 'load-balancer-api-internal: tcp connection to a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:06Z"
    - latency: 8.509268ms
      message: 'load-balancer-api-internal: resolved host name a222d379bd82d4b8d94201e0815a06f4-c29cc58d05ce0064.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-network-check-target-ip-10-0-130-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: 9e677590-74dd-422f-8dd7-8df041ad6498
    resourceVersion: "51442"
    uid: d1806521-d45e-4d2e-90a8-10b1d3107929
  spec:
    sourcePod: network-check-source-989f8b8dc-bb8gt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:20:06Z"
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.151914ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 2.277103ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 2.591748ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 2.278732ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:06Z"
    - latency: 2.220882ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:06Z"
    - latency: 1.93886ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:06Z"
    - latency: 1.824057ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:06Z"
    - latency: 1.825119ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:06Z"
    - latency: 2.331802ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:06Z"
    - latency: 2.451709ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-network-check-target-ip-10-0-139-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: 9e677590-74dd-422f-8dd7-8df041ad6498
    resourceVersion: "51443"
    uid: 76be5584-77d0-46e0-acea-47862324d642
  spec:
    sourcePod: network-check-source-989f8b8dc-bb8gt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:20:06Z"
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.373795ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 2.137846ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 2.808456ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 2.104789ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:06Z"
    - latency: 2.362953ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:06Z"
    - latency: 2.148811ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:06Z"
    - latency: 2.390044ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:06Z"
    - latency: 1.985123ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:06Z"
    - latency: 2.395336ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:06Z"
    - latency: 2.765494ms
      message: 'network-check-target-ip-10-0-139-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-network-check-target-ip-10-0-142-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: 9e677590-74dd-422f-8dd7-8df041ad6498
    resourceVersion: "51441"
    uid: 0a87ddd5-fef5-482e-9356-73868b33278b
  spec:
    sourcePod: network-check-source-989f8b8dc-bb8gt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:20:06Z"
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016522ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 851.139µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 909.031µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 996.936µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:06Z"
    - latency: 830.872µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:06Z"
    - latency: 940.908µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:06Z"
    - latency: 892.926µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:06Z"
    - latency: 863.503µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:06Z"
    - latency: 751.616µs
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:06Z"
    - latency: 1.416211ms
      message: 'network-check-target-ip-10-0-142-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:13:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-233-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-233.ec2.internal
      uid: 9e677590-74dd-422f-8dd7-8df041ad6498
    resourceVersion: "52311"
    uid: b026eb96-436a-4612-8daf-4aa8285b1f59
  spec:
    sourcePod: network-check-source-989f8b8dc-bb8gt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:19:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.208µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:06Z"
    - latency: 1.826577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:49:06Z"
    - latency: 908.007µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 1.776957ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:48:06Z"
    - latency: 928.653µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 1.582332ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:47:06Z"
    - latency: 1.100296ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 1.675499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:46:06Z"
    - latency: 1.167457ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:06Z"
    - latency: 1.910996ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:45:06Z"
kind: List
metadata:
  resourceVersion: ""