apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-99.ec2.internal
      uid: fbbeeb8b-2e1f-447a-94d4-8636f63283ce
    resourceVersion: "188130"
    uid: d79fc070-7178-4769-a694-44a309be0803
  spec:
    sourcePod: network-check-source-6f78d59f99-d29md
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T04:05:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 885.863µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:36:29Z"
    - latency: 1.302496ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:35:29Z"
    - latency: 1.279553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:34:29Z"
    - latency: 1.204286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:33:29Z"
    - latency: 1.05579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:32:29Z"
    - latency: 842.099µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:31:29Z"
    - latency: 906.655µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:30:29Z"
    - latency: 1.199536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:29:29Z"
    - latency: 1.545367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:28:29Z"
    - latency: 1.078444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:27:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-99.ec2.internal
      uid: fbbeeb8b-2e1f-447a-94d4-8636f63283ce
    resourceVersion: "186527"
    uid: df2488a7-6ca3-4b99-b7a4-ccef366edfe0
  spec:
    sourcePod: network-check-source-6f78d59f99-d29md
    targetEndpoint: a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T04:04:29Z"
      message: 'load-balancer-api-external: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.749131ms
      message: 'load-balancer-api-external: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:34:29Z"
    - latency: 6.790408ms
      message: 'load-balancer-api-external: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:34:29Z"
    - latency: 18.729173ms
      message: 'load-balancer-api-external: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:33:29Z"
    - latency: 6.514348ms
      message: 'load-balancer-api-external: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:33:29Z"
    - latency: 16.858728ms
      message: 'load-balancer-api-external: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:32:29Z"
    - latency: 10.010058ms
      message: 'load-balancer-api-external: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:32:29Z"
    - latency: 16.809394ms
      message: 'load-balancer-api-external: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:31:29Z"
    - latency: 6.985605ms
      message: 'load-balancer-api-external: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:31:29Z"
    - latency: 17.229677ms
      message: 'load-balancer-api-external: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:30:29Z"
    - latency: 6.89243ms
      message: 'load-balancer-api-external: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-99.ec2.internal
      uid: fbbeeb8b-2e1f-447a-94d4-8636f63283ce
    resourceVersion: "186528"
    uid: c5f32381-066e-4ab7-b98e-abf3e90e9b50
  spec:
    sourcePod: network-check-source-6f78d59f99-d29md
    targetEndpoint: a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T04:04:29Z"
      message: 'load-balancer-api-internal: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.764559ms
      message: 'load-balancer-api-internal: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:34:29Z"
    - latency: 6.762598ms
      message: 'load-balancer-api-internal: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:34:29Z"
    - latency: 17.716124ms
      message: 'load-balancer-api-internal: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:33:29Z"
    - latency: 6.535509ms
      message: 'load-balancer-api-internal: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:33:29Z"
    - latency: 16.890586ms
      message: 'load-balancer-api-internal: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:32:29Z"
    - latency: 10.038849ms
      message: 'load-balancer-api-internal: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:32:29Z"
    - latency: 16.893252ms
      message: 'load-balancer-api-internal: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:31:29Z"
    - latency: 7.02227ms
      message: 'load-balancer-api-internal: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:31:29Z"
    - latency: 17.25153ms
      message: 'load-balancer-api-internal: tcp connection to a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:30:29Z"
    - latency: 6.836566ms
      message: 'load-balancer-api-internal: resolved host name a2f1c5d94666e4bd791993b5cb63eb77-f96c2d34da76a361.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:58:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-99-to-network-check-target-ip-10-0-138-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-99.ec2.internal
      uid: fbbeeb8b-2e1f-447a-94d4-8636f63283ce
    resourceVersion: "188232"
    uid: 9bcd99de-dc18-496d-ad22-2836fba430bc
  spec:
    sourcePod: network-check-source-6f78d59f99-d29md
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T04:05:37Z"
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.863416ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:36:37Z"
    - latency: 1.859516ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:35:37Z"
    - latency: 2.566726ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:34:37Z"
    - latency: 2.049631ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:33:37Z"
    - latency: 1.987393ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:32:37Z"
    - latency: 1.951406ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:31:37Z"
    - latency: 2.628807ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:30:37Z"
    - latency: 2.345665ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:29:37Z"
    - latency: 2.230236ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:28:37Z"
    - latency: 2.48357ms
      message: 'network-check-target-ip-10-0-138-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:27:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-99-to-network-check-target-ip-10-0-138-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-99.ec2.internal
      uid: fbbeeb8b-2e1f-447a-94d4-8636f63283ce
    resourceVersion: "188129"
    uid: 2199e011-d7cb-4bd3-9074-c987a48e6ac1
  spec:
    sourcePod: network-check-source-6f78d59f99-d29md
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T04:05:29Z"
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.913292ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:36:29Z"
    - latency: 2.334132ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:35:29Z"
    - latency: 1.93864ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:34:29Z"
    - latency: 1.878828ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:33:29Z"
    - latency: 2.334767ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:32:29Z"
    - latency: 2.014281ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:31:29Z"
    - latency: 1.995413ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:30:29Z"
    - latency: 2.75795ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:29:29Z"
    - latency: 2.209309ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:28:29Z"
    - latency: 1.722083ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:27:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-99-to-network-check-target-ip-10-0-139-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-99.ec2.internal
      uid: fbbeeb8b-2e1f-447a-94d4-8636f63283ce
    resourceVersion: "188128"
    uid: b6ec06e1-fc6d-46a9-bcd9-eef715436e82
  spec:
    sourcePod: network-check-source-6f78d59f99-d29md
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T04:05:29Z"
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055839ms
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:36:29Z"
    - latency: 947.985µs
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:35:29Z"
    - latency: 1.028433ms
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:34:29Z"
    - latency: 868.422µs
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:33:29Z"
    - latency: 1.07508ms
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:32:29Z"
    - latency: 867.74µs
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:31:29Z"
    - latency: 1.113188ms
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:30:29Z"
    - latency: 2.339335ms
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:29:29Z"
    - latency: 1.484684ms
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:28:29Z"
    - latency: 1.0662ms
      message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:27:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:58:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-99.ec2.internal
      uid: fbbeeb8b-2e1f-447a-94d4-8636f63283ce
    resourceVersion: "186526"
    uid: f3a24c8b-8441-4391-b583-84c79fad7158
  spec:
    sourcePod: network-check-source-6f78d59f99-d29md
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T04:04:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 828.806µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:34:29Z"
    - latency: 1.799467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:34:29Z"
    - latency: 986.658µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:33:29Z"
    - latency: 1.873261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:33:29Z"
    - latency: 1.275086ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:32:29Z"
    - latency: 1.961891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:32:29Z"
    - latency: 820.624µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:31:29Z"
    - latency: 1.932094ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:31:29Z"
    - latency: 894.024µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T05:30:29Z"
    - latency: 1.689422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T05:30:29Z"
kind: List
metadata:
  resourceVersion: ""