apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:29:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: 81de6444-1ad6-4adf-a61d-e73ecde49025
    resourceVersion: "102964"
    uid: 1d2c7d90-93f2-4a9a-88da-68eba3ba97f1
  spec:
    sourcePod: network-check-source-7d88cb55d8-pzk4p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:36:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.748929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:07:39Z"
    - latency: 1.134291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:06:39Z"
    - latency: 1.197228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 929.156µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 1.357739ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 1.109962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 1.498593ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:01:39Z"
    - latency: 1.360776ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:00:39Z"
    - latency: 1.490828ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:59:39Z"
    - latency: 1.095753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:58:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:29:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: 81de6444-1ad6-4adf-a61d-e73ecde49025
    resourceVersion: "101650"
    uid: 45839d6f-6e9e-440c-90c8-fc428d41e41f
  spec:
    sourcePod: network-check-source-7d88cb55d8-pzk4p
    targetEndpoint: a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:35:39Z"
      message: 'load-balancer-api-external: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.406212ms
      message: 'load-balancer-api-external: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 6.435732ms
      message: 'load-balancer-api-external: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 4.529435ms
      message: 'load-balancer-api-external: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 6.794466ms
      message: 'load-balancer-api-external: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 4.086097ms
      message: 'load-balancer-api-external: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 6.330841ms
      message: 'load-balancer-api-external: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 4.8233ms
      message: 'load-balancer-api-external: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 7.897171ms
      message: 'load-balancer-api-external: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 4.261863ms
      message: 'load-balancer-api-external: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:01:39Z"
    - latency: 7.494281ms
      message: 'load-balancer-api-external: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:29:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: 81de6444-1ad6-4adf-a61d-e73ecde49025
    resourceVersion: "101651"
    uid: f7067c57-4a40-4847-b1ca-87bf2bba7019
  spec:
    sourcePod: network-check-source-7d88cb55d8-pzk4p
    targetEndpoint: a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:35:39Z"
      message: 'load-balancer-api-internal: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.419231ms
      message: 'load-balancer-api-internal: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 6.34915ms
      message: 'load-balancer-api-internal: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 4.502813ms
      message: 'load-balancer-api-internal: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 6.823711ms
      message: 'load-balancer-api-internal: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 4.075032ms
      message: 'load-balancer-api-internal: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 6.287888ms
      message: 'load-balancer-api-internal: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 4.161008ms
      message: 'load-balancer-api-internal: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 7.816151ms
      message: 'load-balancer-api-internal: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 4.901501ms
      message: 'load-balancer-api-internal: tcp connection to a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:01:39Z"
    - latency: 7.473344ms
      message: 'load-balancer-api-internal: resolved host name a16937a1f5987447cb9479e5e4ec6ffa-d8d381b5e676cd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:29:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-network-check-target-ip-10-0-138-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: 81de6444-1ad6-4adf-a61d-e73ecde49025
    resourceVersion: "102961"
    uid: 14f98528-2e5d-43f5-9086-fee8f619dc39
  spec:
    sourcePod: network-check-source-7d88cb55d8-pzk4p
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:36:39Z"
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.000864ms
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:07:39Z"
    - latency: 964.902µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:06:39Z"
    - latency: 897.859µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 1.126769ms
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 837.262µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 918.116µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 1.007768ms
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:01:39Z"
    - latency: 910.145µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:00:39Z"
    - latency: 1.256294ms
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:59:39Z"
    - latency: 983.354µs
      message: 'network-check-target-ip-10-0-138-218: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:58:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:29:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-network-check-target-ip-10-0-139-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: 81de6444-1ad6-4adf-a61d-e73ecde49025
    resourceVersion: "102963"
    uid: ca843dd9-dfe3-42b4-9759-8a12d5ddf9e4
  spec:
    sourcePod: network-check-source-7d88cb55d8-pzk4p
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:36:39Z"
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.976074ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:07:39Z"
    - latency: 2.20186ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:06:39Z"
    - latency: 2.237454ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 2.296552ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 2.24875ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 2.445493ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 2.431254ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:01:39Z"
    - latency: 2.316073ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:00:39Z"
    - latency: 2.838094ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:59:39Z"
    - latency: 2.044281ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:58:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:29:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-network-check-target-ip-10-0-140-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: 81de6444-1ad6-4adf-a61d-e73ecde49025
    resourceVersion: "102962"
    uid: 8ef03de7-ca70-440e-95c8-fe1db8f7cfe4
  spec:
    sourcePod: network-check-source-7d88cb55d8-pzk4p
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:36:39Z"
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.877425ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:07:39Z"
    - latency: 1.988013ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:06:39Z"
    - latency: 1.920531ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 1.978058ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 1.98983ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 1.946823ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 1.996598ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:01:39Z"
    - latency: 1.754259ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:00:39Z"
    - latency: 2.014109ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:59:39Z"
    - latency: 1.840935ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:58:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:29:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-218.ec2.internal
      uid: 81de6444-1ad6-4adf-a61d-e73ecde49025
    resourceVersion: "101649"
    uid: 4c2b81ed-50d0-4dd1-a606-e702d199240a
  spec:
    sourcePod: network-check-source-7d88cb55d8-pzk4p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:35:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.344µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 2.058128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:05:39Z"
    - latency: 926.929µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 1.923971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:04:39Z"
    - latency: 987.588µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 1.671978ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:03:39Z"
    - latency: 955.834µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 1.851767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:02:39Z"
    - latency: 996.753µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T03:01:39Z"
    - latency: 1.740649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T03:01:39Z"
kind: List
metadata:
  resourceVersion: ""