apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:16:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: cfa62fea-6a20-481f-a56c-6b681df573a2
    resourceVersion: "19330"
    uid: 9b14c741-7bbf-425e-a6c5-cb56d26a450a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-phrs9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:23:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 926.016µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 907.428µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:36:34Z"
    - latency: 890.668µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:35:34Z"
    - latency: 1.20992ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:34:34Z"
    - latency: 741.761µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:33:34Z"
    - latency: 1.223897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:32:34Z"
    - latency: 1.197194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:31:34Z"
    - latency: 1.058899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:30:34Z"
    - latency: 1.461525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:29:34Z"
    - latency: 1.186481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:28:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:16:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: cfa62fea-6a20-481f-a56c-6b681df573a2
    resourceVersion: "20655"
    uid: b7f7896e-23b4-4b74-ab54-08e0c2140790
  spec:
    sourcePod: network-check-source-7bc5b6bf85-phrs9
    targetEndpoint: ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:22:34Z"
      message: 'load-balancer-api-external: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.945271ms
      message: 'load-balancer-api-external: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:40:34Z"
    - latency: 6.903927ms
      message: 'load-balancer-api-external: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:40:34Z"
    - latency: 3.955847ms
      message: 'load-balancer-api-external: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:39:34Z"
    - latency: 6.016271ms
      message: 'load-balancer-api-external: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:39:34Z"
    - latency: 5.716491ms
      message: 'load-balancer-api-external: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:38:34Z"
    - latency: 8.949175ms
      message: 'load-balancer-api-external: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:38:34Z"
    - latency: 6.134217ms
      message: 'load-balancer-api-external: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 8.208852ms
      message: 'load-balancer-api-external: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 5.69492ms
      message: 'load-balancer-api-external: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:36:34Z"
    - latency: 6.270768ms
      message: 'load-balancer-api-external: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:36:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:16:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: cfa62fea-6a20-481f-a56c-6b681df573a2
    resourceVersion: "20656"
    uid: 972eef93-6218-4d74-b6fb-e853e89810f6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-phrs9
    targetEndpoint: ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:22:34Z"
      message: 'load-balancer-api-internal: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.882725ms
      message: 'load-balancer-api-internal: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:40:34Z"
    - latency: 6.888728ms
      message: 'load-balancer-api-internal: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:40:34Z"
    - latency: 5.327887ms
      message: 'load-balancer-api-internal: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:39:34Z"
    - latency: 5.843974ms
      message: 'load-balancer-api-internal: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:39:34Z"
    - latency: 3.813671ms
      message: 'load-balancer-api-internal: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:38:34Z"
    - latency: 8.914074ms
      message: 'load-balancer-api-internal: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:38:34Z"
    - latency: 6.18068ms
      message: 'load-balancer-api-internal: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 8.125324ms
      message: 'load-balancer-api-internal: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 4.295306ms
      message: 'load-balancer-api-internal: tcp connection to ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:36:34Z"
    - latency: 6.177529ms
      message: 'load-balancer-api-internal: resolved host name ae8b517e8fbe84ab18e7f53b1e50a0a7-d1dd11fbe3699cda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:36:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:16:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-ip-10-0-129-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: cfa62fea-6a20-481f-a56c-6b681df573a2
    resourceVersion: "19328"
    uid: cb251113-f9ae-4005-b1a3-309c9bb2ac47
  spec:
    sourcePod: network-check-source-7bc5b6bf85-phrs9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:23:34Z"
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.291688ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 1.921974ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:36:34Z"
    - latency: 1.937919ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:35:34Z"
    - latency: 1.98508ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:34:34Z"
    - latency: 2.46213ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:33:34Z"
    - latency: 2.00952ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:32:34Z"
    - latency: 2.305406ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:31:34Z"
    - latency: 2.395121ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:30:34Z"
    - latency: 2.368198ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:29:34Z"
    - latency: 2.110591ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:28:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:16:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-ip-10-0-142-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: cfa62fea-6a20-481f-a56c-6b681df573a2
    resourceVersion: "19327"
    uid: 18dacaff-0afe-4f3b-8dee-93d3ae9368df
  spec:
    sourcePod: network-check-source-7bc5b6bf85-phrs9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:23:34Z"
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.205µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 800.999µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:36:34Z"
    - latency: 845.236µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:35:34Z"
    - latency: 1.331867ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:34:34Z"
    - latency: 1.390815ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:33:34Z"
    - latency: 788.19µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:32:34Z"
    - latency: 890.143µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:31:34Z"
    - latency: 879.984µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:30:34Z"
    - latency: 918.452µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:29:34Z"
    - latency: 923.806µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:28:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:16:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-ip-10-0-142-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: cfa62fea-6a20-481f-a56c-6b681df573a2
    resourceVersion: "19329"
    uid: 8cd482e1-ce84-4419-b0f2-6188d55a5042
  spec:
    sourcePod: network-check-source-7bc5b6bf85-phrs9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:23:34Z"
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.063787ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 1.923949ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:36:34Z"
    - latency: 2.069474ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:35:34Z"
    - latency: 2.218514ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:34:34Z"
    - latency: 2.165114ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:33:34Z"
    - latency: 2.151399ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:32:34Z"
    - latency: 2.29303ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:31:34Z"
    - latency: 2.096876ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:30:34Z"
    - latency: 2.232329ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:29:34Z"
    - latency: 2.443636ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:28:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:16:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: cfa62fea-6a20-481f-a56c-6b681df573a2
    resourceVersion: "20654"
    uid: 546c3379-d680-4e30-9362-49dd43265ac1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-phrs9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:22:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 808.414µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:40:34Z"
    - latency: 1.734055ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:40:34Z"
    - latency: 1.006107ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:39:34Z"
    - latency: 1.648201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:39:34Z"
    - latency: 1.144243ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:38:34Z"
    - latency: 1.497748ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:38:34Z"
    - latency: 817.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 1.908567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:37:34Z"
    - latency: 937.843µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:36:34Z"
    - latency: 1.69063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:36:34Z"
kind: List
metadata:
  resourceVersion: ""