apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T00:13:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-35-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-35.ec2.internal
      uid: e966dcdb-16ef-4f49-9354-1b4ad56f9327
    resourceVersion: "78777"
    uid: d65a1a28-182b-4b02-8e57-fb34b2339fcd
  spec:
    sourcePod: network-check-source-65bdbbff45-9kpzt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T00:21:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.949µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:10:00Z"
    - latency: 854.466µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:09:00Z"
    - latency: 968.765µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 1.09955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 1.232413ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 942.907µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 834.524µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:04:00Z"
    - latency: 971.374µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:03:00Z"
    - latency: 938.255µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:02:00Z"
    - latency: 883.675µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:01:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T00:13:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-35-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-35.ec2.internal
      uid: e966dcdb-16ef-4f49-9354-1b4ad56f9327
    resourceVersion: "76729"
    uid: ce3b403b-c023-480c-9b06-842966e5b165
  spec:
    sourcePod: network-check-source-65bdbbff45-9kpzt
    targetEndpoint: a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T00:20:00Z"
      message: 'load-balancer-api-external: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.938452ms
      message: 'load-balancer-api-external: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 6.926876ms
      message: 'load-balancer-api-external: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 4.100952ms
      message: 'load-balancer-api-external: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 6.571577ms
      message: 'load-balancer-api-external: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 4.520727ms
      message: 'load-balancer-api-external: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 8.950493ms
      message: 'load-balancer-api-external: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 5.100042ms
      message: 'load-balancer-api-external: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 7.130847ms
      message: 'load-balancer-api-external: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 2.948052ms
      message: 'load-balancer-api-external: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:04:00Z"
    - latency: 6.326ms
      message: 'load-balancer-api-external: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:04:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T00:13:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-35-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-35.ec2.internal
      uid: e966dcdb-16ef-4f49-9354-1b4ad56f9327
    resourceVersion: "76730"
    uid: d79d184a-b450-47c9-a06b-b83f8e33633d
  spec:
    sourcePod: network-check-source-65bdbbff45-9kpzt
    targetEndpoint: a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T00:20:00Z"
      message: 'load-balancer-api-internal: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.921688ms
      message: 'load-balancer-api-internal: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 6.949499ms
      message: 'load-balancer-api-internal: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 4.691555ms
      message: 'load-balancer-api-internal: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 6.628109ms
      message: 'load-balancer-api-internal: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 4.513889ms
      message: 'load-balancer-api-internal: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 7.798783ms
      message: 'load-balancer-api-internal: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 5.035945ms
      message: 'load-balancer-api-internal: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 7.160153ms
      message: 'load-balancer-api-internal: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 2.911907ms
      message: 'load-balancer-api-internal: tcp connection to a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:04:00Z"
    - latency: 6.36443ms
      message: 'load-balancer-api-internal: resolved host name a8ea1818c1e484f7f93faff9ae391ac6-03b92b82430f4a06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:04:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T00:13:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-35-to-network-check-target-ip-10-0-129-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-35.ec2.internal
      uid: e966dcdb-16ef-4f49-9354-1b4ad56f9327
    resourceVersion: "78774"
    uid: 6cdd3d57-e2de-4380-81de-3dc802c678c0
  spec:
    sourcePod: network-check-source-65bdbbff45-9kpzt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T00:21:00Z"
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.180577ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:10:00Z"
    - latency: 974.228µs
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:09:00Z"
    - latency: 1.277499ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 1.263367ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 1.936072ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 951.435µs
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 1.003538ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:04:00Z"
    - latency: 1.045884ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:03:00Z"
    - latency: 933.372µs
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:02:00Z"
    - latency: 907.184µs
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:01:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T00:13:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-35-to-network-check-target-ip-10-0-134-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-35.ec2.internal
      uid: e966dcdb-16ef-4f49-9354-1b4ad56f9327
    resourceVersion: "78775"
    uid: dbe09b3d-490f-44a9-a724-98e3ab809bb8
  spec:
    sourcePod: network-check-source-65bdbbff45-9kpzt
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T00:21:00Z"
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.394396ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:10:00Z"
    - latency: 2.336819ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:09:00Z"
    - latency: 2.162871ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 2.006878ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 2.609576ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 2.504217ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 2.283726ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:04:00Z"
    - latency: 2.502736ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:03:00Z"
    - latency: 2.387526ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:02:00Z"
    - latency: 2.492841ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:01:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T00:13:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-35-to-network-check-target-ip-10-0-143-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-35.ec2.internal
      uid: e966dcdb-16ef-4f49-9354-1b4ad56f9327
    resourceVersion: "78776"
    uid: 9123f160-250c-4fd9-88a5-6605777fdf5b
  spec:
    sourcePod: network-check-source-65bdbbff45-9kpzt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T00:21:00Z"
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.582812ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:10:00Z"
    - latency: 2.434638ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:09:00Z"
    - latency: 2.315254ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 2.40354ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 2.557763ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 2.421492ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 2.106404ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:04:00Z"
    - latency: 2.571257ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:03:00Z"
    - latency: 2.492581ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:02:00Z"
    - latency: 2.42388ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:01:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T00:13:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-35-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-35.ec2.internal
      uid: e966dcdb-16ef-4f49-9354-1b4ad56f9327
    resourceVersion: "76728"
    uid: 755bb6f6-3091-436c-829e-38c2bd6339b5
  spec:
    sourcePod: network-check-source-65bdbbff45-9kpzt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T00:20:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.18627ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 1.910031ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:08:00Z"
    - latency: 857.94µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 1.671263ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:07:00Z"
    - latency: 1.041332ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 3.455418ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:06:00Z"
    - latency: 890.882µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 2.207158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:05:00Z"
    - latency: 909.864µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T01:04:00Z"
    - latency: 1.852002ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T01:04:00Z"
kind: List
metadata:
  resourceVersion: ""