apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:39:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-156-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-156.ec2.internal
      uid: 122f5fad-b7d0-4df4-9e1e-c29682d18439
    resourceVersion: "71583"
    uid: b7969003-9532-4c28-889d-a64a69a3a6ae
  spec:
    sourcePod: network-check-source-7d88cb55d8-x887q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:46:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.355148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 1.509312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 831.02µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 1.239513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 1.302071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:17:13Z"
    - latency: 1.198236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:16:13Z"
    - latency: 1.205137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:15:13Z"
    - latency: 921.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:14:13Z"
    - latency: 1.075267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:13:13Z"
    - latency: 1.032985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:12:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:39:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-156-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-156.ec2.internal
      uid: 122f5fad-b7d0-4df4-9e1e-c29682d18439
    resourceVersion: "71585"
    uid: 4cd1d009-34f1-4199-a573-e540a175fc7b
  spec:
    sourcePod: network-check-source-7d88cb55d8-x887q
    targetEndpoint: a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:45:13Z"
      message: 'load-balancer-api-external: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.61612ms
      message: 'load-balancer-api-external: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 8.493681ms
      message: 'load-balancer-api-external: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 8.368884ms
      message: 'load-balancer-api-external: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 8.818534ms
      message: 'load-balancer-api-external: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 4.513987ms
      message: 'load-balancer-api-external: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 7.14153ms
      message: 'load-balancer-api-external: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 4.407746ms
      message: 'load-balancer-api-external: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 7.806815ms
      message: 'load-balancer-api-external: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 5.289751ms
      message: 'load-balancer-api-external: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:17:13Z"
    - latency: 9.099842ms
      message: 'load-balancer-api-external: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:17:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:39:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-156-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-156.ec2.internal
      uid: 122f5fad-b7d0-4df4-9e1e-c29682d18439
    resourceVersion: "71584"
    uid: 5449e158-7d34-41b6-bcb1-48efab11fb50
  spec:
    sourcePod: network-check-source-7d88cb55d8-x887q
    targetEndpoint: a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:45:13Z"
      message: 'load-balancer-api-internal: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.605308ms
      message: 'load-balancer-api-internal: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 8.602285ms
      message: 'load-balancer-api-internal: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 8.355397ms
      message: 'load-balancer-api-internal: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 8.986675ms
      message: 'load-balancer-api-internal: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 4.484559ms
      message: 'load-balancer-api-internal: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 7.234805ms
      message: 'load-balancer-api-internal: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 4.460814ms
      message: 'load-balancer-api-internal: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 7.771773ms
      message: 'load-balancer-api-internal: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 5.576359ms
      message: 'load-balancer-api-internal: tcp connection to a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:17:13Z"
    - latency: 9.198976ms
      message: 'load-balancer-api-internal: resolved host name a28fe4b43910147f5928e88f2383e7d0-9ccd2f5314f45853.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:17:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:39:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-156-to-network-check-target-ip-10-0-132-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-156.ec2.internal
      uid: 122f5fad-b7d0-4df4-9e1e-c29682d18439
    resourceVersion: "71580"
    uid: 5ee78792-f94d-4f3c-bd67-3c7c34713a20
  spec:
    sourcePod: network-check-source-7d88cb55d8-x887q
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:46:13Z"
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.140632ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 2.129683ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 1.821878ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 2.096309ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 1.843764ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:17:13Z"
    - latency: 1.817986ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:16:13Z"
    - latency: 2.26682ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:15:13Z"
    - latency: 1.766692ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:14:13Z"
    - latency: 2.331176ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:13:13Z"
    - latency: 2.061569ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:12:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:39:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-156-to-network-check-target-ip-10-0-132-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-156.ec2.internal
      uid: 122f5fad-b7d0-4df4-9e1e-c29682d18439
    resourceVersion: "71579"
    uid: dafec8bb-c337-4c67-a38e-fd16d4217ab9
  spec:
    sourcePod: network-check-source-7d88cb55d8-x887q
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:46:13Z"
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.614319ms
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 1.731234ms
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 909.243µs
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 1.006191ms
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 1.024185ms
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:17:13Z"
    - latency: 915.811µs
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:16:13Z"
    - latency: 1.056629ms
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:15:13Z"
    - latency: 972.826µs
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:14:13Z"
    - latency: 1.043447ms
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:13:13Z"
    - latency: 1.287639ms
      message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:12:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:39:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-156-to-network-check-target-ip-10-0-135-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-156.ec2.internal
      uid: 122f5fad-b7d0-4df4-9e1e-c29682d18439
    resourceVersion: "71582"
    uid: aa6370c4-f6ad-4b29-a84a-632d539f36c8
  spec:
    sourcePod: network-check-source-7d88cb55d8-x887q
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:46:13Z"
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.813931ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 2.646449ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 2.230615ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 2.436408ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 2.235848ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:17:13Z"
    - latency: 2.537492ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:16:13Z"
    - latency: 2.823891ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:15:13Z"
    - latency: 2.362003ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:14:13Z"
    - latency: 2.38015ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:13:13Z"
    - latency: 2.174552ms
      message: 'network-check-target-ip-10-0-135-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:12:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T15:39:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-156-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-156.ec2.internal
      uid: 122f5fad-b7d0-4df4-9e1e-c29682d18439
    resourceVersion: "71581"
    uid: c12b8dfa-aeed-4f75-9eba-b15240a625ef
  spec:
    sourcePod: network-check-source-7d88cb55d8-x887q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T15:45:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.178896ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 1.930301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:21:13Z"
    - latency: 1.339098ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 1.758158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:20:13Z"
    - latency: 986.635µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 1.691842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:19:13Z"
    - latency: 1.024061ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 2.031118ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:18:13Z"
    - latency: 909.963µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T16:17:13Z"
    - latency: 1.845973ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T16:17:13Z"
kind: List
metadata:
  resourceVersion: ""