apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-31-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-31.ec2.internal
      uid: 2d9b1455-1741-4b04-b15a-bf57a089a9bc
    resourceVersion: "175327"
    uid: ef01d95e-80d9-4eae-b971-153bf807aa85
  spec:
    sourcePod: network-check-source-6f78d59f99-r7vrw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:11:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.187µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:14:33Z"
    - latency: 1.317507ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:13:33Z"
    - latency: 1.903663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:12:33Z"
    - latency: 1.595107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:11:33Z"
    - latency: 1.285152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 1.508266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 2.222417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 1.040007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 1.395719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:06:33Z"
    - latency: 2.337499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:05:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-31-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-31.ec2.internal
      uid: 2d9b1455-1741-4b04-b15a-bf57a089a9bc
    resourceVersion: "165728"
    uid: 02932a93-c2fb-4a8f-8782-a33c6e334959
  spec:
    sourcePod: network-check-source-6f78d59f99-r7vrw
    targetEndpoint: a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:10:33Z"
      message: 'load-balancer-api-external: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.275248ms
      message: 'load-balancer-api-external: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 7.464791ms
      message: 'load-balancer-api-external: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 16.800804ms
      message: 'load-balancer-api-external: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 9.994789ms
      message: 'load-balancer-api-external: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 16.810204ms
      message: 'load-balancer-api-external: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 8.197864ms
      message: 'load-balancer-api-external: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 24.514754ms
      message: 'load-balancer-api-external: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 11.341585ms
      message: 'load-balancer-api-external: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 18.932691ms
      message: 'load-balancer-api-external: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:06:33Z"
    - latency: 7.537ms
      message: 'load-balancer-api-external: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:06:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-31-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-31.ec2.internal
      uid: 2d9b1455-1741-4b04-b15a-bf57a089a9bc
    resourceVersion: "165729"
    uid: 0fbf5f70-c85a-4219-a1c0-5bb4adb2c789
  spec:
    sourcePod: network-check-source-6f78d59f99-r7vrw
    targetEndpoint: a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:10:33Z"
      message: 'load-balancer-api-internal: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.93332ms
      message: 'load-balancer-api-internal: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 7.4237ms
      message: 'load-balancer-api-internal: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 16.845856ms
      message: 'load-balancer-api-internal: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 10.131738ms
      message: 'load-balancer-api-internal: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 17.787833ms
      message: 'load-balancer-api-internal: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 8.137001ms
      message: 'load-balancer-api-internal: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 24.513466ms
      message: 'load-balancer-api-internal: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 11.424766ms
      message: 'load-balancer-api-internal: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 16.93424ms
      message: 'load-balancer-api-internal: tcp connection to a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:06:33Z"
    - latency: 7.553644ms
      message: 'load-balancer-api-internal: resolved host name a4189043bd6594b5b8d00975ba1e5c46-89d8f2ad3b9dedfb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:06:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-31-to-network-check-target-ip-10-0-130-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-31.ec2.internal
      uid: 2d9b1455-1741-4b04-b15a-bf57a089a9bc
    resourceVersion: "175326"
    uid: c57e8b36-f314-4916-8045-daf323dcc0cf
  spec:
    sourcePod: network-check-source-6f78d59f99-r7vrw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:11:33Z"
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.586617ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:14:33Z"
    - latency: 2.360419ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:13:33Z"
    - latency: 2.262841ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:12:33Z"
    - latency: 2.156505ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:11:33Z"
    - latency: 1.850956ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 2.347269ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 2.20892ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 2.01465ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 2.442246ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:06:33Z"
    - latency: 3.574746ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:05:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-31-to-network-check-target-ip-10-0-134-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-31.ec2.internal
      uid: 2d9b1455-1741-4b04-b15a-bf57a089a9bc
    resourceVersion: "175323"
    uid: 1c8c4e9f-03a6-459a-9c34-de49cf96e22c
  spec:
    sourcePod: network-check-source-6f78d59f99-r7vrw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:11:33Z"
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 901.119µs
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:14:33Z"
    - latency: 1.201377ms
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:13:33Z"
    - latency: 900.804µs
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:12:33Z"
    - latency: 987.998µs
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:11:33Z"
    - latency: 1.457269ms
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 999.927µs
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 2.819424ms
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 980.296µs
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 1.669156ms
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:06:33Z"
    - latency: 1.739761ms
      message: 'network-check-target-ip-10-0-134-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:05:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-31-to-network-check-target-ip-10-0-136-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-31.ec2.internal
      uid: 2d9b1455-1741-4b04-b15a-bf57a089a9bc
    resourceVersion: "175322"
    uid: 7e55b512-de6e-42be-a0b3-fa3974e07ca7
  spec:
    sourcePod: network-check-source-6f78d59f99-r7vrw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:11:33Z"
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.600405ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:14:33Z"
    - latency: 2.633189ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:13:33Z"
    - latency: 1.806565ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:12:33Z"
    - latency: 2.603408ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:11:33Z"
    - latency: 2.40708ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 2.355977ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 3.199668ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 1.970485ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 2.817898ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:06:33Z"
    - latency: 5.873236ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:05:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-31-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-31.ec2.internal
      uid: 2d9b1455-1741-4b04-b15a-bf57a089a9bc
    resourceVersion: "165724"
    uid: a42f25e8-8376-4995-a15c-5673a4d242fd
  spec:
    sourcePod: network-check-source-6f78d59f99-r7vrw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:10:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068961ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 2.158257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:10:33Z"
    - latency: 1.07085ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 2.590771ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:09:33Z"
    - latency: 1.213636ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 2.074261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:08:33Z"
    - latency: 1.108263ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 2.185787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:07:33Z"
    - latency: 1.191545ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:06:33Z"
    - latency: 2.424761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:06:33Z"
kind: List
metadata:
  resourceVersion: ""