apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T00:15:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-188-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-188.ec2.internal
      uid: 53067105-96e1-40ad-a8f6-c2ba13848372
    resourceVersion: "54657"
    uid: 3c5e70a2-b7df-4bdc-97c7-a81616ebb7b9
  spec:
    sourcePod: network-check-source-989f8b8dc-j5gqz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T00:22:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.178938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 831.596µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 922.714µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 1.11809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:47:57Z"
    - latency: 1.35892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:46:57Z"
    - latency: 962.459µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:45:57Z"
    - latency: 1.052505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:44:57Z"
    - latency: 983.315µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:43:57Z"
    - latency: 1.153613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:42:57Z"
    - latency: 861.099µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:41:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T00:15:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-188-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-188.ec2.internal
      uid: 53067105-96e1-40ad-a8f6-c2ba13848372
    resourceVersion: "55500"
    uid: 2d4409ad-fe55-4718-8671-b982d8aeceae
  spec:
    sourcePod: network-check-source-989f8b8dc-j5gqz
    targetEndpoint: a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T00:21:57Z"
      message: 'load-balancer-api-external: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.808171ms
      message: 'load-balancer-api-external: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:51:57Z"
    - latency: 8.744384ms
      message: 'load-balancer-api-external: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:51:57Z"
    - latency: 3.205024ms
      message: 'load-balancer-api-external: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 8.84526ms
      message: 'load-balancer-api-external: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 5.842936ms
      message: 'load-balancer-api-external: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 8.890629ms
      message: 'load-balancer-api-external: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 4.606091ms
      message: 'load-balancer-api-external: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 9.624953ms
      message: 'load-balancer-api-external: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 5.28732ms
      message: 'load-balancer-api-external: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:47:57Z"
    - latency: 6.551382ms
      message: 'load-balancer-api-external: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:47:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T00:15:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-188-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-188.ec2.internal
      uid: 53067105-96e1-40ad-a8f6-c2ba13848372
    resourceVersion: "55501"
    uid: fb46aa45-3756-495d-9340-86f4e960c0bf
  spec:
    sourcePod: network-check-source-989f8b8dc-j5gqz
    targetEndpoint: a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T00:21:57Z"
      message: 'load-balancer-api-internal: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.262941ms
      message: 'load-balancer-api-internal: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:51:57Z"
    - latency: 8.650969ms
      message: 'load-balancer-api-internal: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:51:57Z"
    - latency: 3.494863ms
      message: 'load-balancer-api-internal: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 8.786108ms
      message: 'load-balancer-api-internal: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 5.319079ms
      message: 'load-balancer-api-internal: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 8.959687ms
      message: 'load-balancer-api-internal: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 4.636631ms
      message: 'load-balancer-api-internal: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 9.693584ms
      message: 'load-balancer-api-internal: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 5.304182ms
      message: 'load-balancer-api-internal: tcp connection to a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:47:57Z"
    - latency: 6.595658ms
      message: 'load-balancer-api-internal: resolved host name a73a028e491a74e118d81cefad53a239-2bb21ee60da058a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:47:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T00:15:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-188-to-network-check-target-ip-10-0-130-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-188.ec2.internal
      uid: 53067105-96e1-40ad-a8f6-c2ba13848372
    resourceVersion: "54656"
    uid: 56ec2906-ae6e-4b52-8556-9e8601a62178
  spec:
    sourcePod: network-check-source-989f8b8dc-j5gqz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T00:22:57Z"
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.285734ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 1.952533ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 2.172654ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 2.300857ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:47:57Z"
    - latency: 2.185096ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:46:57Z"
    - latency: 2.154733ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:45:57Z"
    - latency: 2.239663ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:44:57Z"
    - latency: 2.249718ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:43:57Z"
    - latency: 2.388514ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:42:57Z"
    - latency: 2.287319ms
      message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:41:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T00:15:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-188-to-network-check-target-ip-10-0-142-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-188.ec2.internal
      uid: 53067105-96e1-40ad-a8f6-c2ba13848372
    resourceVersion: "54654"
    uid: e1b51f82-ab46-45c9-b418-755be433dcb6
  spec:
    sourcePod: network-check-source-989f8b8dc-j5gqz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T00:22:57Z"
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072865ms
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 1.086571ms
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 1.121541ms
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 995.988µs
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:47:57Z"
    - latency: 943.833µs
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:46:57Z"
    - latency: 1.156558ms
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:45:57Z"
    - latency: 934.783µs
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:44:57Z"
    - latency: 1.412826ms
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:43:57Z"
    - latency: 886.816µs
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:42:57Z"
    - latency: 814.747µs
      message: 'network-check-target-ip-10-0-142-188: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:41:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T00:15:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-188-to-network-check-target-ip-10-0-142-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-188.ec2.internal
      uid: 53067105-96e1-40ad-a8f6-c2ba13848372
    resourceVersion: "54655"
    uid: 6661cf12-3f2c-4b98-8dfd-3d6a57d215ef
  spec:
    sourcePod: network-check-source-989f8b8dc-j5gqz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T00:22:57Z"
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.037631ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 1.756347ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 1.896894ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 1.939984ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:47:57Z"
    - latency: 1.965822ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:46:57Z"
    - latency: 1.775255ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:45:57Z"
    - latency: 2.098385ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:44:57Z"
    - latency: 2.291085ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:43:57Z"
    - latency: 1.95984ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:42:57Z"
    - latency: 1.975393ms
      message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:41:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T00:15:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-188-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-188.ec2.internal
      uid: 53067105-96e1-40ad-a8f6-c2ba13848372
    resourceVersion: "55499"
    uid: b336aa43-87d1-41d8-90c2-eddf938d9bd5
  spec:
    sourcePod: network-check-source-989f8b8dc-j5gqz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T00:21:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.372546ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:51:57Z"
    - latency: 1.908828ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:51:57Z"
    - latency: 1.043516ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 1.859494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:50:57Z"
    - latency: 828.759µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 1.92864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:49:57Z"
    - latency: 1.133132ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 1.827635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:48:57Z"
    - latency: 981.891µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T00:47:57Z"
    - latency: 1.683133ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T00:47:57Z"
kind: List
metadata:
  resourceVersion: ""