apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T10:33:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.ec2.internal
      uid: 4128cab7-cbb9-49b0-b877-9fbd2baa5cde
    resourceVersion: "54808"
    uid: 8cdb679f-d14e-46cf-a095-5b9b812632a8
  spec:
    sourcePod: network-check-source-685456655f-hggvk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T10:40:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.18971ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 1.51226ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 1.361793ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:59:43Z"
    - latency: 1.213112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:58:43Z"
    - latency: 1.155377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:57:43Z"
    - latency: 1.567635ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:56:43Z"
    - latency: 942.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:55:43Z"
    - latency: 1.220654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:54:43Z"
    - latency: 1.181738ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:53:43Z"
    - latency: 1.324151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T10:33:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.ec2.internal
      uid: 4128cab7-cbb9-49b0-b877-9fbd2baa5cde
    resourceVersion: "56323"
    uid: ca7ca995-30a6-4b2a-bed5-e290879702cf
  spec:
    sourcePod: network-check-source-685456655f-hggvk
    targetEndpoint: ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T10:39:43Z"
      message: 'load-balancer-api-external: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.45714ms
      message: 'load-balancer-api-external: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:03:43Z"
    - latency: 7.66361ms
      message: 'load-balancer-api-external: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:03:43Z"
    - latency: 4.617117ms
      message: 'load-balancer-api-external: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:02:43Z"
    - latency: 8.947487ms
      message: 'load-balancer-api-external: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:02:43Z"
    - latency: 6.521627ms
      message: 'load-balancer-api-external: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 10.175754ms
      message: 'load-balancer-api-external: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 6.004659ms
      message: 'load-balancer-api-external: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 9.035512ms
      message: 'load-balancer-api-external: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 11.13786ms
      message: 'load-balancer-api-external: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:59:43Z"
    - latency: 8.753975ms
      message: 'load-balancer-api-external: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:59:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T10:33:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.ec2.internal
      uid: 4128cab7-cbb9-49b0-b877-9fbd2baa5cde
    resourceVersion: "56322"
    uid: 7c13730f-b7fa-4400-85f2-7d849bca7c2a
  spec:
    sourcePod: network-check-source-685456655f-hggvk
    targetEndpoint: ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T10:39:43Z"
      message: 'load-balancer-api-internal: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.278466ms
      message: 'load-balancer-api-internal: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:03:43Z"
    - latency: 7.767785ms
      message: 'load-balancer-api-internal: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:03:43Z"
    - latency: 4.623073ms
      message: 'load-balancer-api-internal: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:02:43Z"
    - latency: 8.8353ms
      message: 'load-balancer-api-internal: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:02:43Z"
    - latency: 5.215625ms
      message: 'load-balancer-api-internal: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 10.294746ms
      message: 'load-balancer-api-internal: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 6.050553ms
      message: 'load-balancer-api-internal: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 8.956073ms
      message: 'load-balancer-api-internal: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 5.498705ms
      message: 'load-balancer-api-internal: tcp connection to ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:59:43Z"
    - latency: 8.854847ms
      message: 'load-balancer-api-internal: resolved host name ad377230a2c934df8b812a20853d8514-ff62b1bd50b515b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:59:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T10:33:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-128-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.ec2.internal
      uid: 4128cab7-cbb9-49b0-b877-9fbd2baa5cde
    resourceVersion: "54807"
    uid: 8a708475-fd2d-4bd7-b145-79307b1af734
  spec:
    sourcePod: network-check-source-685456655f-hggvk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T10:40:43Z"
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.434292ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 2.211547ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 2.296842ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:59:43Z"
    - latency: 2.652445ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:58:43Z"
    - latency: 2.545699ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:57:43Z"
    - latency: 2.684786ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:56:43Z"
    - latency: 2.530933ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:55:43Z"
    - latency: 2.227584ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:54:43Z"
    - latency: 2.290518ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:53:43Z"
    - latency: 2.405724ms
      message: 'network-check-target-ip-10-0-128-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T10:33:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-131-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.ec2.internal
      uid: 4128cab7-cbb9-49b0-b877-9fbd2baa5cde
    resourceVersion: "54805"
    uid: 739edfeb-f401-4d2b-995f-7dde89d8bcc5
  spec:
    sourcePod: network-check-source-685456655f-hggvk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T10:40:43Z"
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.316081ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 1.282478ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 910.036µs
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:59:43Z"
    - latency: 1.816289ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:58:43Z"
    - latency: 1.00687ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:57:43Z"
    - latency: 868.642µs
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:56:43Z"
    - latency: 974.93µs
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:55:43Z"
    - latency: 918.558µs
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:54:43Z"
    - latency: 901.664µs
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:53:43Z"
    - latency: 1.085791ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T10:33:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-139-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.ec2.internal
      uid: 4128cab7-cbb9-49b0-b877-9fbd2baa5cde
    resourceVersion: "54806"
    uid: 370d7d78-f9c2-4269-a0e7-8c7a660da079
  spec:
    sourcePod: network-check-source-685456655f-hggvk
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T10:40:43Z"
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.420167ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 2.749589ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 2.00947ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:59:43Z"
    - latency: 2.16956ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:58:43Z"
    - latency: 2.496438ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:57:43Z"
    - latency: 3.183245ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:56:43Z"
    - latency: 2.251911ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:55:43Z"
    - latency: 2.240403ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:54:43Z"
    - latency: 2.592029ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:53:43Z"
    - latency: 2.476818ms
      message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:52:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T10:33:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-250-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-250.ec2.internal
      uid: 4128cab7-cbb9-49b0-b877-9fbd2baa5cde
    resourceVersion: "56321"
    uid: 5771d776-329d-4187-aefa-0a84f94b7b74
  spec:
    sourcePod: network-check-source-685456655f-hggvk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T10:39:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.435µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:03:43Z"
    - latency: 1.761615ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:03:43Z"
    - latency: 965.637µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:02:43Z"
    - latency: 1.844446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:02:43Z"
    - latency: 912.989µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 2.078918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:01:43Z"
    - latency: 914.43µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 2.079899ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T11:00:43Z"
    - latency: 814.906µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:59:43Z"
    - latency: 3.024031ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:59:43Z"
kind: List
metadata:
  resourceVersion: ""