apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:28:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-206-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-206.ec2.internal
      uid: fa0b8b75-344e-48ac-9cf6-7826dad3b4cb
    resourceVersion: "55122"
    uid: 3855d0e1-5df5-40a3-99e0-aa34160dfe3b
  spec:
    sourcePod: network-check-source-989f8b8dc-g9t4d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T23:35:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 963.376µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 1.063074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 912.949µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 892.529µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:00:59Z"
    - latency: 1.432396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:59:59Z"
    - latency: 1.00481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:58:59Z"
    - latency: 1.556531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:57:59Z"
    - latency: 1.481978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:56:59Z"
    - latency: 870.805µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:55:59Z"
    - latency: 942.656µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:28:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-206-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-206.ec2.internal
      uid: fa0b8b75-344e-48ac-9cf6-7826dad3b4cb
    resourceVersion: "56079"
    uid: a8c5ca05-bca6-404f-9cc7-a5dfc99c590f
  spec:
    sourcePod: network-check-source-989f8b8dc-g9t4d
    targetEndpoint: adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T23:34:59Z"
      message: 'load-balancer-api-external: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.691205ms
      message: 'load-balancer-api-external: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:04:59Z"
    - latency: 7.145876ms
      message: 'load-balancer-api-external: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:04:59Z"
    - latency: 5.093738ms
      message: 'load-balancer-api-external: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 9.870234ms
      message: 'load-balancer-api-external: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 3.665546ms
      message: 'load-balancer-api-external: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 8.757417ms
      message: 'load-balancer-api-external: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 4.206885ms
      message: 'load-balancer-api-external: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 7.683659ms
      message: 'load-balancer-api-external: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 5.483314ms
      message: 'load-balancer-api-external: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:00:59Z"
    - latency: 9.853838ms
      message: 'load-balancer-api-external: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:00:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:28:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-206-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-206.ec2.internal
      uid: fa0b8b75-344e-48ac-9cf6-7826dad3b4cb
    resourceVersion: "56080"
    uid: 3f90204b-c0bf-48d4-b5ca-9849c4313c3f
  spec:
    sourcePod: network-check-source-989f8b8dc-g9t4d
    targetEndpoint: adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T23:34:59Z"
      message: 'load-balancer-api-internal: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.72714ms
      message: 'load-balancer-api-internal: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:04:59Z"
    - latency: 7.098402ms
      message: 'load-balancer-api-internal: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:04:59Z"
    - latency: 5.142532ms
      message: 'load-balancer-api-internal: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 9.79911ms
      message: 'load-balancer-api-internal: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 3.59954ms
      message: 'load-balancer-api-internal: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 8.706354ms
      message: 'load-balancer-api-internal: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 4.213675ms
      message: 'load-balancer-api-internal: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 7.635083ms
      message: 'load-balancer-api-internal: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 4.438045ms
      message: 'load-balancer-api-internal: tcp connection to adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:00:59Z"
    - latency: 9.87477ms
      message: 'load-balancer-api-internal: resolved host name adb0a189913d641459e5a9a6c247aa50-e29c2aab603263ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:00:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:28:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-206-to-network-check-target-ip-10-0-135-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-206.ec2.internal
      uid: fa0b8b75-344e-48ac-9cf6-7826dad3b4cb
    resourceVersion: "55120"
    uid: 83e16639-fd5c-4f6c-a429-62532b4319d4
  spec:
    sourcePod: network-check-source-989f8b8dc-g9t4d
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T23:35:59Z"
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.213966ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 2.230583ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 2.030608ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 2.12988ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:00:59Z"
    - latency: 2.274054ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:59:59Z"
    - latency: 3.308998ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:58:59Z"
    - latency: 1.909319ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:57:59Z"
    - latency: 2.284102ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:56:59Z"
    - latency: 2.329756ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:55:59Z"
    - latency: 2.065826ms
      message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:28:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-206-to-network-check-target-ip-10-0-138-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-206.ec2.internal
      uid: fa0b8b75-344e-48ac-9cf6-7826dad3b4cb
    resourceVersion: "55121"
    uid: b99600eb-a00e-4a40-98e8-7a32bec55215
  spec:
    sourcePod: network-check-source-989f8b8dc-g9t4d
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T23:35:59Z"
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.119558ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 2.173136ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 2.202128ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 1.973824ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:00:59Z"
    - latency: 2.017579ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:59:59Z"
    - latency: 2.013185ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:58:59Z"
    - latency: 1.820207ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:57:59Z"
    - latency: 2.032431ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:56:59Z"
    - latency: 1.909025ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:55:59Z"
    - latency: 1.91215ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:28:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-206-to-network-check-target-ip-10-0-143-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-206.ec2.internal
      uid: fa0b8b75-344e-48ac-9cf6-7826dad3b4cb
    resourceVersion: "55119"
    uid: b5676fe3-81a8-40be-a672-4edac248fd30
  spec:
    sourcePod: network-check-source-989f8b8dc-g9t4d
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T23:35:59Z"
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.849µs
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 1.280284ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 1.784642ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 1.353826ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:00:59Z"
    - latency: 1.446331ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:59:59Z"
    - latency: 3.659107ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:58:59Z"
    - latency: 854.688µs
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:57:59Z"
    - latency: 888.67µs
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:56:59Z"
    - latency: 940.143µs
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:55:59Z"
    - latency: 1.117211ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:28:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-206-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-206.ec2.internal
      uid: fa0b8b75-344e-48ac-9cf6-7826dad3b4cb
    resourceVersion: "56077"
    uid: b6d551ec-2987-4eb7-87e5-56677bd30866
  spec:
    sourcePod: network-check-source-989f8b8dc-g9t4d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T23:34:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.017369ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:04:59Z"
    - latency: 1.777015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:04:59Z"
    - latency: 990.987µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 2.259301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:03:59Z"
    - latency: 1.026424ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 2.0701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:02:59Z"
    - latency: 1.248727ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 2.013591ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:01:59Z"
    - latency: 1.583481ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:00:59Z"
    - latency: 2.041897ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:00:59Z"
kind: List
metadata:
  resourceVersion: ""