apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:57:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: f7e70e9b-45e6-48bf-bcce-0cc4f1a6343d
    resourceVersion: "172842"
    uid: 758b8395-58fe-4799-8464-87b296f84935
  spec:
    sourcePod: network-check-source-6f78d59f99-d2vr7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T07:04:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.071941ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:07:53Z"
    - latency: 1.434823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:06:53Z"
    - latency: 6.34446ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:05:53Z"
    - latency: 1.140605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:04:53Z"
    - latency: 1.352803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:03:53Z"
    - latency: 1.446587ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:02:53Z"
    - latency: 2.228035ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:01:53Z"
    - latency: 1.30154ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:00:53Z"
    - latency: 1.217898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:59:53Z"
    - latency: 1.341873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:58:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:57:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: f7e70e9b-45e6-48bf-bcce-0cc4f1a6343d
    resourceVersion: "163375"
    uid: 12e40672-f486-48ba-bde0-dda31523e1b6
  spec:
    sourcePod: network-check-source-6f78d59f99-d2vr7
    targetEndpoint: af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T07:03:53Z"
      message: 'load-balancer-api-external: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.71567ms
      message: 'load-balancer-api-external: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:03:53Z"
    - latency: 6.605145ms
      message: 'load-balancer-api-external: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:03:53Z"
    - latency: 18.618335ms
      message: 'load-balancer-api-external: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:02:53Z"
    - latency: 8.628754ms
      message: 'load-balancer-api-external: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:02:53Z"
    - latency: 17.665973ms
      message: 'load-balancer-api-external: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:01:53Z"
    - latency: 7.854044ms
      message: 'load-balancer-api-external: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:01:53Z"
    - latency: 21.465012ms
      message: 'load-balancer-api-external: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:00:53Z"
    - latency: 6.979731ms
      message: 'load-balancer-api-external: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:00:53Z"
    - latency: 17.344967ms
      message: 'load-balancer-api-external: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:59:53Z"
    - latency: 7.016325ms
      message: 'load-balancer-api-external: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:59:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:57:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: f7e70e9b-45e6-48bf-bcce-0cc4f1a6343d
    resourceVersion: "163374"
    uid: ef1f2848-8ae7-4cfc-890c-1553a388d69c
  spec:
    sourcePod: network-check-source-6f78d59f99-d2vr7
    targetEndpoint: af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T07:03:53Z"
      message: 'load-balancer-api-internal: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.781524ms
      message: 'load-balancer-api-internal: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:03:53Z"
    - latency: 6.555034ms
      message: 'load-balancer-api-internal: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:03:53Z"
    - latency: 18.904046ms
      message: 'load-balancer-api-internal: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:02:53Z"
    - latency: 8.653885ms
      message: 'load-balancer-api-internal: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:02:53Z"
    - latency: 18.382227ms
      message: 'load-balancer-api-internal: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:01:53Z"
    - latency: 7.84121ms
      message: 'load-balancer-api-internal: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:01:53Z"
    - latency: 17.42234ms
      message: 'load-balancer-api-internal: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:00:53Z"
    - latency: 7.003547ms
      message: 'load-balancer-api-internal: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:00:53Z"
    - latency: 17.666368ms
      message: 'load-balancer-api-internal: tcp connection to af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:59:53Z"
    - latency: 6.952891ms
      message: 'load-balancer-api-internal: resolved host name af1c8b0fa23c34d7cb3f6c7795488755-b7ea0ad39a8b15e4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:59:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:57:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-network-check-target-ip-10-0-128-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: f7e70e9b-45e6-48bf-bcce-0cc4f1a6343d
    resourceVersion: "172944"
    uid: 5f758d89-ea41-43fb-bdaf-07a22102b089
  spec:
    sourcePod: network-check-source-6f78d59f99-d2vr7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T07:04:55Z"
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.21947ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:07:55Z"
    - latency: 2.526461ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:06:55Z"
    - latency: 2.207922ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:05:55Z"
    - latency: 2.576048ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:04:55Z"
    - latency: 2.013204ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:03:55Z"
    - latency: 2.508111ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:02:55Z"
    - latency: 2.202157ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:01:55Z"
    - latency: 1.223973ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:00:55Z"
    - latency: 2.753657ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:59:55Z"
    - latency: 2.980797ms
      message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:58:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:57:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-network-check-target-ip-10-0-132-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: f7e70e9b-45e6-48bf-bcce-0cc4f1a6343d
    resourceVersion: "172839"
    uid: 3a636172-0a3f-4203-bdc1-76a76d6c43c9
  spec:
    sourcePod: network-check-source-6f78d59f99-d2vr7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T07:04:53Z"
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.372993ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:07:53Z"
    - latency: 1.714857ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:06:53Z"
    - latency: 6.480534ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:05:53Z"
    - latency: 1.498012ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:04:53Z"
    - latency: 1.552513ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:03:53Z"
    - latency: 2.973723ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:02:53Z"
    - latency: 1.348624ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:01:53Z"
    - latency: 1.430193ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:00:53Z"
    - latency: 1.096309ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:59:53Z"
    - latency: 2.026003ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:58:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:57:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-network-check-target-ip-10-0-139-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: f7e70e9b-45e6-48bf-bcce-0cc4f1a6343d
    resourceVersion: "172840"
    uid: 95ad2b33-0cf5-4e90-a041-013a58bb6cc2
  spec:
    sourcePod: network-check-source-6f78d59f99-d2vr7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T07:04:53Z"
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.321984ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:07:53Z"
    - latency: 2.655693ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:06:53Z"
    - latency: 11.061434ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:05:53Z"
    - latency: 2.360277ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:04:53Z"
    - latency: 2.478441ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:03:53Z"
    - latency: 2.990059ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:02:53Z"
    - latency: 2.984805ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:01:53Z"
    - latency: 2.973814ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:00:53Z"
    - latency: 2.60691ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:59:53Z"
    - latency: 2.852741ms
      message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:58:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T06:57:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: f7e70e9b-45e6-48bf-bcce-0cc4f1a6343d
    resourceVersion: "163373"
    uid: 1ca9a9a3-8231-491a-80c3-2f2b831d1839
  spec:
    sourcePod: network-check-source-6f78d59f99-d2vr7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T07:03:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.07989ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:03:53Z"
    - latency: 2.006629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:03:53Z"
    - latency: 939.588µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:02:53Z"
    - latency: 3.823164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:02:53Z"
    - latency: 1.061524ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:01:53Z"
    - latency: 2.373677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:01:53Z"
    - latency: 2.669835ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T08:00:53Z"
    - latency: 2.171144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T08:00:53Z"
    - latency: 1.160564ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:59:53Z"
    - latency: 2.37535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T07:59:53Z"
kind: List
metadata:
  resourceVersion: ""