apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:37:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: e70e1020-b05c-4073-8aff-8cb6b61bb1f2
    resourceVersion: "65984"
    uid: 5760ec01-6f92-4533-9817-4fffe01609d4
  spec:
    sourcePod: network-check-source-6f8b768455-bzbwp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:44:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.122344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 878.395µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 998.911µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 1.101376ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:09:20Z"
    - latency: 1.230356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:08:20Z"
    - latency: 1.074278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:07:20Z"
    - latency: 1.152198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:06:20Z"
    - latency: 1.904572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:05:20Z"
    - latency: 1.302629ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:04:20Z"
    - latency: 1.265435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:03:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:37:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: e70e1020-b05c-4073-8aff-8cb6b61bb1f2
    resourceVersion: "66616"
    uid: 7e54bd8b-eac3-44eb-94bf-71875008ad58
  spec:
    sourcePod: network-check-source-6f8b768455-bzbwp
    targetEndpoint: a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:43:20Z"
      message: 'load-balancer-api-external: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.251111ms
      message: 'load-balancer-api-external: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:13:20Z"
    - latency: 9.772613ms
      message: 'load-balancer-api-external: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:13:20Z"
    - latency: 5.216362ms
      message: 'load-balancer-api-external: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 9.006876ms
      message: 'load-balancer-api-external: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 4.575286ms
      message: 'load-balancer-api-external: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 10.10583ms
      message: 'load-balancer-api-external: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 5.195111ms
      message: 'load-balancer-api-external: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 10.337343ms
      message: 'load-balancer-api-external: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 5.140639ms
      message: 'load-balancer-api-external: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:09:20Z"
    - latency: 9.195516ms
      message: 'load-balancer-api-external: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:09:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:37:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: e70e1020-b05c-4073-8aff-8cb6b61bb1f2
    resourceVersion: "66615"
    uid: 5db74a63-7c5d-4c02-8717-a7202c8b5d2f
  spec:
    sourcePod: network-check-source-6f8b768455-bzbwp
    targetEndpoint: a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:43:20Z"
      message: 'load-balancer-api-internal: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.873971ms
      message: 'load-balancer-api-internal: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:13:20Z"
    - latency: 9.847797ms
      message: 'load-balancer-api-internal: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:13:20Z"
    - latency: 5.593775ms
      message: 'load-balancer-api-internal: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 9.095318ms
      message: 'load-balancer-api-internal: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 4.570574ms
      message: 'load-balancer-api-internal: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 10.049471ms
      message: 'load-balancer-api-internal: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 5.225574ms
      message: 'load-balancer-api-internal: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 10.280023ms
      message: 'load-balancer-api-internal: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 5.13554ms
      message: 'load-balancer-api-internal: tcp connection to a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:09:20Z"
    - latency: 9.280826ms
      message: 'load-balancer-api-internal: resolved host name a81d04b6e212e45a2ad8ed776893f263-1f5e7d9a43960ec6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:09:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:37:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-network-check-target-ip-10-0-131-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: e70e1020-b05c-4073-8aff-8cb6b61bb1f2
    resourceVersion: "65982"
    uid: 214c66ed-5cb7-4f1d-9a06-4b33d47b3e60
  spec:
    sourcePod: network-check-source-6f8b768455-bzbwp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:44:20Z"
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.227877ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 2.424268ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 1.838305ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 2.130316ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:09:20Z"
    - latency: 2.313199ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:08:20Z"
    - latency: 2.499887ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:07:20Z"
    - latency: 2.416282ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:06:20Z"
    - latency: 2.581485ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:05:20Z"
    - latency: 2.799253ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:04:20Z"
    - latency: 2.575651ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:03:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:37:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-network-check-target-ip-10-0-134-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: e70e1020-b05c-4073-8aff-8cb6b61bb1f2
    resourceVersion: "65981"
    uid: ad57c617-4f1d-4257-9c1c-d521448965e9
  spec:
    sourcePod: network-check-source-6f8b768455-bzbwp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:44:20Z"
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.103512ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 1.163675ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 1.025458ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 783.215µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:09:20Z"
    - latency: 926.868µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:08:20Z"
    - latency: 1.237292ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:07:20Z"
    - latency: 956.885µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:06:20Z"
    - latency: 893.119µs
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:05:20Z"
    - latency: 1.912428ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:04:20Z"
    - latency: 1.90333ms
      message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:03:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:37:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-network-check-target-ip-10-0-136-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: e70e1020-b05c-4073-8aff-8cb6b61bb1f2
    resourceVersion: "65983"
    uid: 9de2bda3-ac8b-47b2-a391-d57e9315be95
  spec:
    sourcePod: network-check-source-6f8b768455-bzbwp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:44:20Z"
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.413635ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 2.388489ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 2.384866ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 2.295322ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:09:20Z"
    - latency: 2.453198ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:08:20Z"
    - latency: 2.176219ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:07:20Z"
    - latency: 2.275035ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:06:20Z"
    - latency: 2.462526ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:05:20Z"
    - latency: 2.719985ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:04:20Z"
    - latency: 2.428546ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:03:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T00:37:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-152-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-152.ec2.internal
      uid: e70e1020-b05c-4073-8aff-8cb6b61bb1f2
    resourceVersion: "66614"
    uid: f40697f6-e526-4d5f-b3dd-d2082a456ccf
  spec:
    sourcePod: network-check-source-6f8b768455-bzbwp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T00:43:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.362384ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:13:20Z"
    - latency: 1.915338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:13:20Z"
    - latency: 903.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 2.229049ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:12:20Z"
    - latency: 1.082941ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 2.165568ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:11:20Z"
    - latency: 1.091962ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 1.666312ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:10:20Z"
    - latency: 931.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T01:09:20Z"
    - latency: 2.169839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T01:09:20Z"
kind: List
metadata:
  resourceVersion: ""