apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-156-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-156.ec2.internal
      uid: 4ef98db6-dd55-4463-8890-57eb9fb08583
    resourceVersion: "32048"
    uid: b03d14b4-501d-44a5-9b81-ced65cd90e2f
  spec:
    sourcePod: network-check-source-869dcfcdcd-cfhdz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.946µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 876.704µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 938.79µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 1.019052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 1.289622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:27:11Z"
    - latency: 886.353µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:26:11Z"
    - latency: 927.866µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:25:11Z"
    - latency: 1.29531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:24:11Z"
    - latency: 896.925µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:23:11Z"
    - latency: 796.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:22:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-156-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-156.ec2.internal
      uid: 4ef98db6-dd55-4463-8890-57eb9fb08583
    resourceVersion: "32050"
    uid: eb58f6db-d063-4b08-a69c-7029aa31446a
  spec:
    sourcePod: network-check-source-869dcfcdcd-cfhdz
    targetEndpoint: a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:55:11Z"
      message: 'load-balancer-api-external: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.774384ms
      message: 'load-balancer-api-external: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 8.660676ms
      message: 'load-balancer-api-external: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 4.444977ms
      message: 'load-balancer-api-external: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 8.409524ms
      message: 'load-balancer-api-external: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 5.035939ms
      message: 'load-balancer-api-external: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 8.362611ms
      message: 'load-balancer-api-external: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 5.996973ms
      message: 'load-balancer-api-external: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 8.023763ms
      message: 'load-balancer-api-external: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 7.445336ms
      message: 'load-balancer-api-external: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:27:11Z"
    - latency: 8.319596ms
      message: 'load-balancer-api-external: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:27:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-156-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-156.ec2.internal
      uid: 4ef98db6-dd55-4463-8890-57eb9fb08583
    resourceVersion: "32049"
    uid: f8f870d1-a1be-409d-bd90-e12539e68a2f
  spec:
    sourcePod: network-check-source-869dcfcdcd-cfhdz
    targetEndpoint: a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:55:11Z"
      message: 'load-balancer-api-internal: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.799905ms
      message: 'load-balancer-api-internal: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 8.688715ms
      message: 'load-balancer-api-internal: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 5.250517ms
      message: 'load-balancer-api-internal: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 8.501578ms
      message: 'load-balancer-api-internal: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 5.004658ms
      message: 'load-balancer-api-internal: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 8.460073ms
      message: 'load-balancer-api-internal: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 6.085266ms
      message: 'load-balancer-api-internal: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 7.978509ms
      message: 'load-balancer-api-internal: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 4.095677ms
      message: 'load-balancer-api-internal: tcp connection to a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:27:11Z"
    - latency: 8.393179ms
      message: 'load-balancer-api-internal: resolved host name a529781f569104ae98f6c50b1254152b-c5d65f233bce1181.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:27:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-156-to-network-check-target-ip-10-0-130-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-156.ec2.internal
      uid: 4ef98db6-dd55-4463-8890-57eb9fb08583
    resourceVersion: "32047"
    uid: 88afca9b-9e9b-4035-b22c-471413dccd6b
  spec:
    sourcePod: network-check-source-869dcfcdcd-cfhdz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:11Z"
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.499815ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 2.246466ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 2.262121ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 2.356595ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 2.500798ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:27:11Z"
    - latency: 2.250968ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:26:11Z"
    - latency: 2.313045ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:25:11Z"
    - latency: 2.28339ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:24:11Z"
    - latency: 2.291494ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:23:11Z"
    - latency: 2.303043ms
      message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:22:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-156-to-network-check-target-ip-10-0-131-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-156.ec2.internal
      uid: 4ef98db6-dd55-4463-8890-57eb9fb08583
    resourceVersion: "32045"
    uid: 0f5f6e7b-698b-436c-91b8-9294b1136b9e
  spec:
    sourcePod: network-check-source-869dcfcdcd-cfhdz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:11Z"
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.426393ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 2.069552ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 2.449144ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 2.328402ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 2.382373ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:27:11Z"
    - latency: 2.115512ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:26:11Z"
    - latency: 2.160682ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:25:11Z"
    - latency: 2.380573ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:24:11Z"
    - latency: 2.852857ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:23:11Z"
    - latency: 2.610791ms
      message: 'network-check-target-ip-10-0-131-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:22:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-156-to-network-check-target-ip-10-0-138-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-156.ec2.internal
      uid: 4ef98db6-dd55-4463-8890-57eb9fb08583
    resourceVersion: "32044"
    uid: 7581320b-5e04-413e-9ce4-b3bd1f77d20c
  spec:
    sourcePod: network-check-source-869dcfcdcd-cfhdz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:56:11Z"
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.463µs
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 1.27989ms
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 1.181596ms
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 819.751µs
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 1.497994ms
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:27:11Z"
    - latency: 755.044µs
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:26:11Z"
    - latency: 1.449624ms
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:25:11Z"
    - latency: 841.255µs
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:24:11Z"
    - latency: 982.599µs
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:23:11Z"
    - latency: 1.311906ms
      message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:22:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-156-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-156.ec2.internal
      uid: 4ef98db6-dd55-4463-8890-57eb9fb08583
    resourceVersion: "32046"
    uid: 9c9dd1b2-dd8a-4974-8f2f-fe90c22c621d
  spec:
    sourcePod: network-check-source-869dcfcdcd-cfhdz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:55:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 871.484µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 1.574383ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:31:11Z"
    - latency: 900.083µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 1.977711ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:30:11Z"
    - latency: 832.872µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 1.677664ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:29:11Z"
    - latency: 1.146098ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 1.640325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:28:11Z"
    - latency: 1.026828ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:27:11Z"
    - latency: 1.707524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:27:11Z"
kind: List
metadata:
  resourceVersion: ""