apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: ac4f4d8c-d836-4dde-a750-4eea464772aa
    resourceVersion: "19276"
    uid: df4b684f-11b0-49fc-9556-d1b49ede537e
  spec:
    sourcePod: network-check-source-7d88cb55d8-l2rp9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:00:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.315µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 1.259663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:13:10Z"
    - latency: 1.04478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:12:10Z"
    - latency: 933.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:11:10Z"
    - latency: 1.090931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:10:10Z"
    - latency: 986.882µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:09:10Z"
    - latency: 1.050177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:08:10Z"
    - latency: 895.709µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:10Z"
    - latency: 1.039879ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:10Z"
    - latency: 1.113968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: ac4f4d8c-d836-4dde-a750-4eea464772aa
    resourceVersion: "20467"
    uid: 136645df-5ff9-4213-9812-ce4b6f9f8e38
  spec:
    sourcePod: network-check-source-7d88cb55d8-l2rp9
    targetEndpoint: a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:59:10Z"
      message: 'load-balancer-api-external: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 28.438873ms
      message: 'load-balancer-api-external: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:17:10Z"
    - latency: 8.894959ms
      message: 'load-balancer-api-external: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:17:10Z"
    - latency: 5.471446ms
      message: 'load-balancer-api-external: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:16:10Z"
    - latency: 8.278337ms
      message: 'load-balancer-api-external: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:16:10Z"
    - latency: 7.213081ms
      message: 'load-balancer-api-external: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:15:10Z"
    - latency: 9.087037ms
      message: 'load-balancer-api-external: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:15:10Z"
    - latency: 4.60891ms
      message: 'load-balancer-api-external: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 12.889852ms
      message: 'load-balancer-api-external: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 5.013033ms
      message: 'load-balancer-api-external: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:13:10Z"
    - latency: 8.092775ms
      message: 'load-balancer-api-external: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:13:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: ac4f4d8c-d836-4dde-a750-4eea464772aa
    resourceVersion: "20466"
    uid: 54576df6-2334-4d34-b2ba-85487a8ffcaf
  spec:
    sourcePod: network-check-source-7d88cb55d8-l2rp9
    targetEndpoint: a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:59:10Z"
      message: 'load-balancer-api-internal: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 28.339846ms
      message: 'load-balancer-api-internal: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:17:10Z"
    - latency: 8.910687ms
      message: 'load-balancer-api-internal: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:17:10Z"
    - latency: 5.62085ms
      message: 'load-balancer-api-internal: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:16:10Z"
    - latency: 8.361173ms
      message: 'load-balancer-api-internal: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:16:10Z"
    - latency: 5.857212ms
      message: 'load-balancer-api-internal: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:15:10Z"
    - latency: 9.120761ms
      message: 'load-balancer-api-internal: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:15:10Z"
    - latency: 3.583453ms
      message: 'load-balancer-api-internal: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 12.793277ms
      message: 'load-balancer-api-internal: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 3.801932ms
      message: 'load-balancer-api-internal: tcp connection to a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:13:10Z"
    - latency: 8.067318ms
      message: 'load-balancer-api-internal: resolved host name a68c9ea55150445c0a835a2d7db3d50f-fb619251f1fb6104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:13:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-ip-10-0-128-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: ac4f4d8c-d836-4dde-a750-4eea464772aa
    resourceVersion: "19273"
    uid: 61bab32e-33a6-4e0b-8620-2b156be8da14
  spec:
    sourcePod: network-check-source-7d88cb55d8-l2rp9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:00:10Z"
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.240326ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 2.286035ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:13:10Z"
    - latency: 2.119285ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:12:10Z"
    - latency: 2.288056ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:11:10Z"
    - latency: 2.000607ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:10:10Z"
    - latency: 2.059461ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:09:10Z"
    - latency: 2.491982ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:08:10Z"
    - latency: 2.622591ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:10Z"
    - latency: 2.275597ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:10Z"
    - latency: 2.206115ms
      message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-ip-10-0-129-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: ac4f4d8c-d836-4dde-a750-4eea464772aa
    resourceVersion: "19274"
    uid: 1725392e-450b-40b7-84c8-786953c761b7
  spec:
    sourcePod: network-check-source-7d88cb55d8-l2rp9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:00:10Z"
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.447586ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 750.373µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:13:10Z"
    - latency: 1.258643ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:12:10Z"
    - latency: 1.137009ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:11:10Z"
    - latency: 707.405µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:10:10Z"
    - latency: 1.302798ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:09:10Z"
    - latency: 966.403µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:08:10Z"
    - latency: 927.101µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:10Z"
    - latency: 1.114984ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:10Z"
    - latency: 896.513µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-ip-10-0-134-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: ac4f4d8c-d836-4dde-a750-4eea464772aa
    resourceVersion: "19275"
    uid: 48201f6d-9978-44c4-837d-7596671b73ff
  spec:
    sourcePod: network-check-source-7d88cb55d8-l2rp9
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:00:10Z"
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.45624ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 2.240823ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:13:10Z"
    - latency: 2.136668ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:12:10Z"
    - latency: 2.284915ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:11:10Z"
    - latency: 2.277967ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:10:10Z"
    - latency: 2.222313ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:09:10Z"
    - latency: 2.409493ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:08:10Z"
    - latency: 2.121969ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:07:10Z"
    - latency: 2.186123ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:10Z"
    - latency: 2.344187ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: ac4f4d8c-d836-4dde-a750-4eea464772aa
    resourceVersion: "20465"
    uid: 18749dfb-4b7b-408e-8f9b-03364ae6523c
  spec:
    sourcePod: network-check-source-7d88cb55d8-l2rp9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:59:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 916.586µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:17:10Z"
    - latency: 1.654388ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:17:10Z"
    - latency: 877.226µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:16:10Z"
    - latency: 1.646513ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:16:10Z"
    - latency: 1.092614ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:15:10Z"
    - latency: 1.961214ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:15:10Z"
    - latency: 885.551µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 2.479369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:14:10Z"
    - latency: 889.085µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:13:10Z"
    - latency: 1.610148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:13:10Z"
kind: List
metadata:
  resourceVersion: ""