apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:38:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 54d9eea1-57c6-46cf-9f00-1572a811a48a
    resourceVersion: "70156"
    uid: 3d86bb2c-ecd0-4fbe-ad3e-dcfd7ff3e1a3
  spec:
    sourcePod: network-check-source-7d88cb55d8-xdqw5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:45:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.191022ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:27:18Z"
    - latency: 1.090324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:26:18Z"
    - latency: 1.141566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:25:18Z"
    - latency: 861.806µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:24:18Z"
    - latency: 1.08855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:23:18Z"
    - latency: 1.256284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:22:18Z"
    - latency: 997.839µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:21:18Z"
    - latency: 1.222992ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:20:18Z"
    - latency: 1.287685ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:19:18Z"
    - latency: 1.392699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:18:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:38:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 54d9eea1-57c6-46cf-9f00-1572a811a48a
    resourceVersion: "74987"
    uid: 09105df9-9799-4006-aa19-ac2bb186949c
  spec:
    sourcePod: network-check-source-7d88cb55d8-xdqw5
    targetEndpoint: abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:44:18Z"
      message: 'load-balancer-api-external: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.835493ms
      message: 'load-balancer-api-external: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:32:18Z"
    - latency: 8.137085ms
      message: 'load-balancer-api-external: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:32:18Z"
    - latency: 4.600181ms
      message: 'load-balancer-api-external: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:31:18Z"
    - latency: 11.065805ms
      message: 'load-balancer-api-external: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:31:18Z"
    - latency: 5.334132ms
      message: 'load-balancer-api-external: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:30:18Z"
    - latency: 8.666963ms
      message: 'load-balancer-api-external: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:30:18Z"
    - latency: 4.758353ms
      message: 'load-balancer-api-external: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:29:18Z"
    - latency: 9.021575ms
      message: 'load-balancer-api-external: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:29:18Z"
    - latency: 4.316813ms
      message: 'load-balancer-api-external: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:28:18Z"
    - latency: 8.336019ms
      message: 'load-balancer-api-external: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:28:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:38:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 54d9eea1-57c6-46cf-9f00-1572a811a48a
    resourceVersion: "74986"
    uid: 6d0f4ddc-73b0-48ec-beb4-fd9537c8728b
  spec:
    sourcePod: network-check-source-7d88cb55d8-xdqw5
    targetEndpoint: abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:44:18Z"
      message: 'load-balancer-api-internal: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.923228ms
      message: 'load-balancer-api-internal: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:32:18Z"
    - latency: 8.080061ms
      message: 'load-balancer-api-internal: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:32:18Z"
    - latency: 4.118337ms
      message: 'load-balancer-api-internal: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:31:18Z"
    - latency: 11.112551ms
      message: 'load-balancer-api-internal: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:31:18Z"
    - latency: 4.500413ms
      message: 'load-balancer-api-internal: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:30:18Z"
    - latency: 8.62831ms
      message: 'load-balancer-api-internal: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:30:18Z"
    - latency: 4.713976ms
      message: 'load-balancer-api-internal: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:29:18Z"
    - latency: 9.148445ms
      message: 'load-balancer-api-internal: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:29:18Z"
    - latency: 4.269264ms
      message: 'load-balancer-api-internal: tcp connection to abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:28:18Z"
    - latency: 8.297872ms
      message: 'load-balancer-api-internal: resolved host name abc3704723e7b46b3bc9f5610c6c5d4b-91ae6add1109e753.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:28:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:38:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-ip-10-0-128-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 54d9eea1-57c6-46cf-9f00-1572a811a48a
    resourceVersion: "70153"
    uid: 4f299d37-3e2e-4ef1-9a1c-c6661cb29068
  spec:
    sourcePod: network-check-source-7d88cb55d8-xdqw5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:45:18Z"
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.653061ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:27:18Z"
    - latency: 957.115µs
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:26:18Z"
    - latency: 1.048803ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:25:18Z"
    - latency: 1.014506ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:24:18Z"
    - latency: 1.731932ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:23:18Z"
    - latency: 1.328314ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:22:18Z"
    - latency: 1.576482ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:21:18Z"
    - latency: 987.909µs
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:20:18Z"
    - latency: 1.080178ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:19:18Z"
    - latency: 1.049007ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:18:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:38:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-ip-10-0-128-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 54d9eea1-57c6-46cf-9f00-1572a811a48a
    resourceVersion: "70155"
    uid: 69c9efb8-d353-4ae3-9ba0-e580dfb05edd
  spec:
    sourcePod: network-check-source-7d88cb55d8-xdqw5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:45:18Z"
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.391658ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:27:18Z"
    - latency: 1.866222ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:26:18Z"
    - latency: 2.311421ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:25:18Z"
    - latency: 1.79984ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:24:18Z"
    - latency: 2.225968ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:23:18Z"
    - latency: 2.232386ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:22:18Z"
    - latency: 2.371314ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:21:18Z"
    - latency: 2.445214ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:20:18Z"
    - latency: 2.428478ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:19:18Z"
    - latency: 2.679073ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:18:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:38:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-ip-10-0-130-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 54d9eea1-57c6-46cf-9f00-1572a811a48a
    resourceVersion: "70154"
    uid: 23c9057a-11c5-40fd-a30b-e3477fa7e548
  spec:
    sourcePod: network-check-source-7d88cb55d8-xdqw5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:45:18Z"
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.537303ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:27:18Z"
    - latency: 2.192091ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:26:18Z"
    - latency: 2.423986ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:25:18Z"
    - latency: 1.900403ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:24:18Z"
    - latency: 2.398051ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:23:18Z"
    - latency: 2.724924ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:22:18Z"
    - latency: 2.488175ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:21:18Z"
    - latency: 2.436493ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:20:18Z"
    - latency: 2.579333ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:19:18Z"
    - latency: 2.6907ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:18:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T19:38:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-255-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-255.ec2.internal
      uid: 54d9eea1-57c6-46cf-9f00-1572a811a48a
    resourceVersion: "74985"
    uid: 66842f60-d1ce-4e03-a3e0-15c2bac6fa92
  spec:
    sourcePod: network-check-source-7d88cb55d8-xdqw5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T19:44:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.983µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:32:18Z"
    - latency: 1.872246ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:32:18Z"
    - latency: 960.866µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:31:18Z"
    - latency: 1.994879ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:31:18Z"
    - latency: 955.256µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:30:18Z"
    - latency: 1.846353ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:30:18Z"
    - latency: 1.12962ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:29:18Z"
    - latency: 2.174334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:29:18Z"
    - latency: 959.834µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:28:18Z"
    - latency: 1.942102ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T20:28:18Z"
kind: List
metadata:
  resourceVersion: ""