apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:08:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-55-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-55.ec2.internal
      uid: 91cb9c35-4679-470e-8722-16f513357e46
    resourceVersion: "71388"
    uid: 453c5a53-23a2-4de1-b41e-64ca4ab60ac2
  spec:
    sourcePod: network-check-source-7d88cb55d8-kvjsg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:15:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 981.908µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:57:52Z"
    - latency: 1.356701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 1.417423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 1.053683ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 1.069988ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 1.137631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:52:52Z"
    - latency: 998.282µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:51:52Z"
    - latency: 1.010817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:50:52Z"
    - latency: 1.073345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:49:52Z"
    - latency: 1.212222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:08:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-55-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-55.ec2.internal
      uid: 91cb9c35-4679-470e-8722-16f513357e46
    resourceVersion: "70357"
    uid: 42d0fd83-c102-44bc-8afc-e7bcdac2697a
  spec:
    sourcePod: network-check-source-7d88cb55d8-kvjsg
    targetEndpoint: ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:14:52Z"
      message: 'load-balancer-api-external: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.443766ms
      message: 'load-balancer-api-external: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 9.507243ms
      message: 'load-balancer-api-external: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 4.166663ms
      message: 'load-balancer-api-external: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 9.495434ms
      message: 'load-balancer-api-external: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 4.983506ms
      message: 'load-balancer-api-external: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 8.826639ms
      message: 'load-balancer-api-external: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 3.702927ms
      message: 'load-balancer-api-external: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 8.89132ms
      message: 'load-balancer-api-external: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 5.335301ms
      message: 'load-balancer-api-external: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:52:52Z"
    - latency: 8.615404ms
      message: 'load-balancer-api-external: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:52:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:08:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-55-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-55.ec2.internal
      uid: 91cb9c35-4679-470e-8722-16f513357e46
    resourceVersion: "70358"
    uid: 777dc57a-6afe-465a-bee7-3db4018a5676
  spec:
    sourcePod: network-check-source-7d88cb55d8-kvjsg
    targetEndpoint: ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:14:52Z"
      message: 'load-balancer-api-internal: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.45191ms
      message: 'load-balancer-api-internal: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 9.435769ms
      message: 'load-balancer-api-internal: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 4.17013ms
      message: 'load-balancer-api-internal: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 9.52451ms
      message: 'load-balancer-api-internal: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 4.961464ms
      message: 'load-balancer-api-internal: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 8.895656ms
      message: 'load-balancer-api-internal: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 3.654972ms
      message: 'load-balancer-api-internal: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 8.831587ms
      message: 'load-balancer-api-internal: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 5.268875ms
      message: 'load-balancer-api-internal: tcp connection to ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:52:52Z"
    - latency: 8.530418ms
      message: 'load-balancer-api-internal: resolved host name ac65f16a683e448828252c9f10c1ebe0-b069799182d2e218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:52:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:08:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-55-to-network-check-target-ip-10-0-133-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-55.ec2.internal
      uid: 91cb9c35-4679-470e-8722-16f513357e46
    resourceVersion: "71385"
    uid: 2620c100-b6eb-4793-b0c0-abd102a86790
  spec:
    sourcePod: network-check-source-7d88cb55d8-kvjsg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:15:52Z"
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.35226ms
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:57:52Z"
    - latency: 948.528µs
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 1.691187ms
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 1.418779ms
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 1.015454ms
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 1.575901ms
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:52:52Z"
    - latency: 765.746µs
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:51:52Z"
    - latency: 1.036249ms
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:50:52Z"
    - latency: 968.383µs
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:49:52Z"
    - latency: 1.045372ms
      message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:08:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-55-to-network-check-target-ip-10-0-135-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-55.ec2.internal
      uid: 91cb9c35-4679-470e-8722-16f513357e46
    resourceVersion: "71387"
    uid: ebc65c9b-fa7d-4f52-99ec-a4d6b7a80f0f
  spec:
    sourcePod: network-check-source-7d88cb55d8-kvjsg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:15:52Z"
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.342076ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:57:52Z"
    - latency: 2.013006ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 2.551525ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 2.196473ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 2.006107ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 2.039912ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:52:52Z"
    - latency: 2.166278ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:51:52Z"
    - latency: 2.329918ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:50:52Z"
    - latency: 2.202304ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:49:52Z"
    - latency: 2.486069ms
      message: 'network-check-target-ip-10-0-135-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:08:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-55-to-network-check-target-ip-10-0-137-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-55.ec2.internal
      uid: 91cb9c35-4679-470e-8722-16f513357e46
    resourceVersion: "71386"
    uid: 7dad4b22-19d7-4e80-b915-d2b2eb9891dc
  spec:
    sourcePod: network-check-source-7d88cb55d8-kvjsg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:15:52Z"
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.372852ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:57:52Z"
    - latency: 2.10653ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 2.208639ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 2.148555ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 2.151182ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 2.336928ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:52:52Z"
    - latency: 1.734526ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:51:52Z"
    - latency: 2.166396ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:50:52Z"
    - latency: 2.509068ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:49:52Z"
    - latency: 2.567121ms
      message: 'network-check-target-ip-10-0-137-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:48:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T00:08:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-55-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-55.ec2.internal
      uid: 91cb9c35-4679-470e-8722-16f513357e46
    resourceVersion: "70353"
    uid: c46b9549-e07d-4a11-804d-c570f0e9ccce
  spec:
    sourcePod: network-check-source-7d88cb55d8-kvjsg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T00:14:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 831.073µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 2.063903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:56:52Z"
    - latency: 959.006µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 1.943123ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:55:52Z"
    - latency: 1.002068ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 1.867376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:54:52Z"
    - latency: 1.121184ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 1.884888ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:53:52Z"
    - latency: 1.232086ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T00:52:52Z"
    - latency: 1.923474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T00:52:52Z"
kind: List
metadata:
  resourceVersion: ""