apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:56:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 892b9a40-eeae-436d-99f5-525fba48a4b0
    resourceVersion: "72620"
    uid: 1e17d02a-ded1-4dcb-a166-ca3383d2b622
  spec:
    sourcePod: network-check-source-7d88cb55d8-thw6z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:03:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 914.761µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:45:04Z"
    - latency: 1.230949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 1.090659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 1.036716ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 1.111508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 941.572µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:04Z"
    - latency: 1.54129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:04Z"
    - latency: 1.082325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:04Z"
    - latency: 876.805µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:04Z"
    - latency: 1.011761ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:56:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 892b9a40-eeae-436d-99f5-525fba48a4b0
    resourceVersion: "71456"
    uid: 15a8f3a7-188b-4c72-a9ce-3ff588a3f9fb
  spec:
    sourcePod: network-check-source-7d88cb55d8-thw6z
    targetEndpoint: a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:02:04Z"
      message: 'load-balancer-api-external: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.373693ms
      message: 'load-balancer-api-external: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 7.199352ms
      message: 'load-balancer-api-external: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 6.119322ms
      message: 'load-balancer-api-external: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 7.472892ms
      message: 'load-balancer-api-external: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 4.616468ms
      message: 'load-balancer-api-external: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 7.111256ms
      message: 'load-balancer-api-external: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 4.562925ms
      message: 'load-balancer-api-external: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 6.89958ms
      message: 'load-balancer-api-external: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 6.129026ms
      message: 'load-balancer-api-external: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:04Z"
    - latency: 11.664032ms
      message: 'load-balancer-api-external: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:56:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 892b9a40-eeae-436d-99f5-525fba48a4b0
    resourceVersion: "71455"
    uid: 1aa8815b-4d34-4d9b-9ef2-43dbc0b9fea1
  spec:
    sourcePod: network-check-source-7d88cb55d8-thw6z
    targetEndpoint: a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:02:04Z"
      message: 'load-balancer-api-internal: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.906413ms
      message: 'load-balancer-api-internal: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 7.169032ms
      message: 'load-balancer-api-internal: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 6.169671ms
      message: 'load-balancer-api-internal: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 7.526252ms
      message: 'load-balancer-api-internal: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 3.891068ms
      message: 'load-balancer-api-internal: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 7.158643ms
      message: 'load-balancer-api-internal: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 4.559733ms
      message: 'load-balancer-api-internal: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 7.878058ms
      message: 'load-balancer-api-internal: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 6.093236ms
      message: 'load-balancer-api-internal: tcp connection to a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:04Z"
    - latency: 11.727034ms
      message: 'load-balancer-api-internal: resolved host name a7f22965a170145d880e34a66ed4e65b-6a195f0cb3f08939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:56:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-ip-10-0-131-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 892b9a40-eeae-436d-99f5-525fba48a4b0
    resourceVersion: "72618"
    uid: 1414cc76-d130-42c1-a6be-332a98a0b0a2
  spec:
    sourcePod: network-check-source-7d88cb55d8-thw6z
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:03:04Z"
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.42867ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:45:04Z"
    - latency: 1.409236ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 1.431376ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 876.687µs
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 1.050676ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 1.554727ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:04Z"
    - latency: 1.009997ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:04Z"
    - latency: 1.061112ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:04Z"
    - latency: 950.717µs
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:04Z"
    - latency: 1.794269ms
      message: 'network-check-target-ip-10-0-131-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:56:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-ip-10-0-131-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 892b9a40-eeae-436d-99f5-525fba48a4b0
    resourceVersion: "72619"
    uid: 9cb45da8-97da-4968-9dd1-ba212eb56ccc
  spec:
    sourcePod: network-check-source-7d88cb55d8-thw6z
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:03:04Z"
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.59896ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:45:04Z"
    - latency: 2.409501ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 3.021046ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 2.101645ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 2.37107ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 2.664919ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:04Z"
    - latency: 3.429454ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:04Z"
    - latency: 3.190402ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:04Z"
    - latency: 2.279338ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:04Z"
    - latency: 2.296432ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:56:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-ip-10-0-141-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 892b9a40-eeae-436d-99f5-525fba48a4b0
    resourceVersion: "72617"
    uid: 24570314-32ca-4563-bf3f-efe231030b8d
  spec:
    sourcePod: network-check-source-7d88cb55d8-thw6z
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:03:04Z"
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.125039ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:45:04Z"
    - latency: 2.262769ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 2.7501ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 2.264338ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 2.403204ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 2.259867ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:04Z"
    - latency: 2.5368ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:04Z"
    - latency: 2.038568ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:04Z"
    - latency: 2.10693ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:04Z"
    - latency: 2.380104ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:56:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-89-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-89.ec2.internal
      uid: 892b9a40-eeae-436d-99f5-525fba48a4b0
    resourceVersion: "71454"
    uid: bc00c52f-4dd2-4c6b-8f4e-6544e0f9f2df
  spec:
    sourcePod: network-check-source-7d88cb55d8-thw6z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:02:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.097µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 1.910783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:44:04Z"
    - latency: 920.441µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 1.959482ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:43:04Z"
    - latency: 1.057085ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 1.778547ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:42:04Z"
    - latency: 1.268511ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 1.929441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:41:04Z"
    - latency: 1.13849ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:04Z"
    - latency: 2.264918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:40:04Z"
kind: List
metadata:
  resourceVersion: ""