apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-119-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-119.ec2.internal
      uid: 41ccf547-bc7d-4a18-ad22-c561a25a93dd
    resourceVersion: "55447"
    uid: dbac762a-e596-48d3-8c60-bd4a969c5b27
  spec:
    sourcePod: network-check-source-869dcfcdcd-m9ntg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:45:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.111204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 1.052841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 1.17228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 1.020438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:10:41Z"
    - latency: 1.109753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:09:41Z"
    - latency: 1.156585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:41Z"
    - latency: 1.173435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:41Z"
    - latency: 1.180303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:41Z"
    - latency: 1.062427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:41Z"
    - latency: 954.192µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:04:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-119-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-119.ec2.internal
      uid: 41ccf547-bc7d-4a18-ad22-c561a25a93dd
    resourceVersion: "56373"
    uid: d764670c-d1ab-4c06-a094-8754436c8002
  spec:
    sourcePod: network-check-source-869dcfcdcd-m9ntg
    targetEndpoint: a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:44:41Z"
      message: 'load-balancer-api-external: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.70952ms
      message: 'load-balancer-api-external: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:14:41Z"
    - latency: 9.648836ms
      message: 'load-balancer-api-external: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:14:41Z"
    - latency: 4.57148ms
      message: 'load-balancer-api-external: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 17.736042ms
      message: 'load-balancer-api-external: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 3.845899ms
      message: 'load-balancer-api-external: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 9.362383ms
      message: 'load-balancer-api-external: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 3.799748ms
      message: 'load-balancer-api-external: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 9.074914ms
      message: 'load-balancer-api-external: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 4.100906ms
      message: 'load-balancer-api-external: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:10:41Z"
    - latency: 13.584465ms
      message: 'load-balancer-api-external: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:10:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-119-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-119.ec2.internal
      uid: 41ccf547-bc7d-4a18-ad22-c561a25a93dd
    resourceVersion: "56374"
    uid: 2d46284a-fe43-47d8-8e25-0b6caf9ab1c5
  spec:
    sourcePod: network-check-source-869dcfcdcd-m9ntg
    targetEndpoint: a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:44:41Z"
      message: 'load-balancer-api-internal: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.740481ms
      message: 'load-balancer-api-internal: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:14:41Z"
    - latency: 9.608083ms
      message: 'load-balancer-api-internal: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:14:41Z"
    - latency: 4.612966ms
      message: 'load-balancer-api-internal: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 17.773835ms
      message: 'load-balancer-api-internal: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 3.896789ms
      message: 'load-balancer-api-internal: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 9.342267ms
      message: 'load-balancer-api-internal: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 3.91008ms
      message: 'load-balancer-api-internal: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 9.253568ms
      message: 'load-balancer-api-internal: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 3.937314ms
      message: 'load-balancer-api-internal: tcp connection to a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:10:41Z"
    - latency: 13.619972ms
      message: 'load-balancer-api-internal: resolved host name a5b8522b7cb6746f091f0682124f709d-71637aab3f57ea58.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:10:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-119-to-network-check-target-ip-10-0-128-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-119.ec2.internal
      uid: 41ccf547-bc7d-4a18-ad22-c561a25a93dd
    resourceVersion: "55446"
    uid: 987a602a-74a0-4f33-b0b1-21eee937e6b9
  spec:
    sourcePod: network-check-source-869dcfcdcd-m9ntg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:45:41Z"
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.362078ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 2.392437ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 2.241192ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 2.659519ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:10:41Z"
    - latency: 2.160209ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:09:41Z"
    - latency: 2.495021ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:41Z"
    - latency: 2.589157ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:41Z"
    - latency: 2.205655ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:41Z"
    - latency: 2.340538ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:41Z"
    - latency: 2.036095ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:04:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-119-to-network-check-target-ip-10-0-133-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-119.ec2.internal
      uid: 41ccf547-bc7d-4a18-ad22-c561a25a93dd
    resourceVersion: "55444"
    uid: 6ae1f07f-3ea5-4896-94ee-0abe225a4148
  spec:
    sourcePod: network-check-source-869dcfcdcd-m9ntg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:45:41Z"
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.237µs
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 994.685µs
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 1.121702ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 1.077517ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:10:41Z"
    - latency: 1.040083ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:09:41Z"
    - latency: 900.026µs
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:41Z"
    - latency: 1.448498ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:41Z"
    - latency: 1.345756ms
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:41Z"
    - latency: 941.62µs
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:41Z"
    - latency: 877.255µs
      message: 'network-check-target-ip-10-0-133-119: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:04:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-119-to-network-check-target-ip-10-0-133-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-119.ec2.internal
      uid: 41ccf547-bc7d-4a18-ad22-c561a25a93dd
    resourceVersion: "55445"
    uid: cf30bb5e-f4e0-4020-8133-bb191ff1312b
  spec:
    sourcePod: network-check-source-869dcfcdcd-m9ntg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:45:41Z"
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.471275ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 2.172388ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 2.168062ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 2.566057ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:10:41Z"
    - latency: 2.079831ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:09:41Z"
    - latency: 2.860576ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:08:41Z"
    - latency: 2.207178ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:07:41Z"
    - latency: 2.371163ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:06:41Z"
    - latency: 1.770387ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:05:41Z"
    - latency: 2.27669ms
      message: 'network-check-target-ip-10-0-133-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:04:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T23:38:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-119-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-119.ec2.internal
      uid: 41ccf547-bc7d-4a18-ad22-c561a25a93dd
    resourceVersion: "56372"
    uid: baa1a3ea-2e29-4648-b08f-357db53d1c91
  spec:
    sourcePod: network-check-source-869dcfcdcd-m9ntg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T23:44:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.988µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:14:41Z"
    - latency: 1.795092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:14:41Z"
    - latency: 981.15µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 1.944206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:13:41Z"
    - latency: 1.07735ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 2.156484ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:12:41Z"
    - latency: 1.404615ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 1.777315ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:11:41Z"
    - latency: 910.826µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T00:10:41Z"
    - latency: 1.83907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T00:10:41Z"
kind: List
metadata:
  resourceVersion: ""