apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-35-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-35.ec2.internal
      uid: 0d8834d5-7dec-4b0c-9920-403b5a5748ab
    resourceVersion: "48646"
    uid: 0a5cde2e-8f96-4306-b752-226299f08147
  spec:
    sourcePod: network-check-source-989f8b8dc-mtqzk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:39:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.006313ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 1.175079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 1.172084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 1.197648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:59Z"
    - latency: 988.133µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:59Z"
    - latency: 1.191207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:59Z"
    - latency: 1.154755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:59Z"
    - latency: 1.174451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:59Z"
    - latency: 1.098809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:59Z"
    - latency: 1.124563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-35-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-35.ec2.internal
      uid: 0d8834d5-7dec-4b0c-9920-403b5a5748ab
    resourceVersion: "49327"
    uid: 9394411b-0f25-4c3d-a559-237732bc9796
  spec:
    sourcePod: network-check-source-989f8b8dc-mtqzk
    targetEndpoint: a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:38:59Z"
      message: 'load-balancer-api-external: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.726075ms
      message: 'load-balancer-api-external: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:59Z"
    - latency: 8.994523ms
      message: 'load-balancer-api-external: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:59Z"
    - latency: 5.923876ms
      message: 'load-balancer-api-external: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 9.429806ms
      message: 'load-balancer-api-external: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 5.13781ms
      message: 'load-balancer-api-external: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 8.867398ms
      message: 'load-balancer-api-external: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 3.851319ms
      message: 'load-balancer-api-external: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 8.684017ms
      message: 'load-balancer-api-external: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 5.619273ms
      message: 'load-balancer-api-external: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:59Z"
    - latency: 8.724191ms
      message: 'load-balancer-api-external: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-35-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-35.ec2.internal
      uid: 0d8834d5-7dec-4b0c-9920-403b5a5748ab
    resourceVersion: "49331"
    uid: f64d356d-4ae2-4364-8e67-051972d5c607
  spec:
    sourcePod: network-check-source-989f8b8dc-mtqzk
    targetEndpoint: a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:38:59Z"
      message: 'load-balancer-api-internal: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.171321ms
      message: 'load-balancer-api-internal: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:59Z"
    - latency: 5.289174ms
      message: 'load-balancer-api-internal: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:59Z"
    - latency: 6.197374ms
      message: 'load-balancer-api-internal: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 2.737704ms
      message: 'load-balancer-api-internal: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 2.480821ms
      message: 'load-balancer-api-internal: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 2.875208ms
      message: 'load-balancer-api-internal: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 5.082785ms
      message: 'load-balancer-api-internal: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 5.214329ms
      message: 'load-balancer-api-internal: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 4.558438ms
      message: 'load-balancer-api-internal: tcp connection to a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:59Z"
    - latency: 2.57667ms
      message: 'load-balancer-api-internal: resolved host name a1001293894be405898c003abcd1c266-fdf8e22a806cc7ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-35-to-network-check-target-ip-10-0-128-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-35.ec2.internal
      uid: 0d8834d5-7dec-4b0c-9920-403b5a5748ab
    resourceVersion: "48654"
    uid: 25cfdfc4-41f6-4d8f-b388-2c1cebc966a0
  spec:
    sourcePod: network-check-source-989f8b8dc-mtqzk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:39:59Z"
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 705.167µs
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 1.849481ms
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 664.551µs
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 1.703511ms
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:59Z"
    - latency: 1.639948ms
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:59Z"
    - latency: 686.123µs
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:59Z"
    - latency: 1.803225ms
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:59Z"
    - latency: 700.47µs
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:59Z"
    - latency: 681.644µs
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:59Z"
    - latency: 635.668µs
      message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-35-to-network-check-target-ip-10-0-131-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-35.ec2.internal
      uid: 0d8834d5-7dec-4b0c-9920-403b5a5748ab
    resourceVersion: "48651"
    uid: 5dbf3916-c03e-493f-b9cc-e9843b7ca9dc
  spec:
    sourcePod: network-check-source-989f8b8dc-mtqzk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:39:59Z"
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 659.854µs
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 967.684µs
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 937.922µs
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 852.941µs
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:59Z"
    - latency: 901.327µs
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:59Z"
    - latency: 920.804µs
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:59Z"
    - latency: 822.573µs
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:59Z"
    - latency: 1.012218ms
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:59Z"
    - latency: 857.577µs
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:59Z"
    - latency: 895.253µs
      message: 'network-check-target-ip-10-0-131-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-35-to-network-check-target-ip-10-0-140-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-35.ec2.internal
      uid: 0d8834d5-7dec-4b0c-9920-403b5a5748ab
    resourceVersion: "48652"
    uid: 877486b0-e092-4fcb-a407-b282ea32c80c
  spec:
    sourcePod: network-check-source-989f8b8dc-mtqzk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:39:59Z"
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.921363ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 744.708µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 2.145522ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 660.301µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:59Z"
    - latency: 658.68µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:59Z"
    - latency: 2.147327ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:59Z"
    - latency: 2.210114ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:59Z"
    - latency: 2.147082ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:59Z"
    - latency: 1.838673ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:59Z"
    - latency: 2.162456ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:32:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-35-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-35.ec2.internal
      uid: 0d8834d5-7dec-4b0c-9920-403b5a5748ab
    resourceVersion: "49330"
    uid: b4c3a081-882e-458f-b242-0dab6f08c418
  spec:
    sourcePod: network-check-source-989f8b8dc-mtqzk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:38:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.1366ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:59Z"
    - latency: 523.048µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:59Z"
    - latency: 1.763901ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 583.129µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:59Z"
    - latency: 2.379414ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 583.236µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:59Z"
    - latency: 2.025134ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 519.188µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:59Z"
    - latency: 1.80652ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:59Z"
    - latency: 1.016197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:59Z"
kind: List
metadata:
  resourceVersion: ""