apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-225-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-225.ec2.internal
      uid: 3e0ab7f1-cbe5-4e4f-90a7-22db46367abb
    resourceVersion: "53513"
    uid: dc8e3753-d21d-4cff-96d5-ce402eec08b7
  spec:
    sourcePod: network-check-source-989f8b8dc-862fp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.199908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 782.945µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 1.324069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 905.01µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:02:30Z"
    - latency: 1.178533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:01:30Z"
    - latency: 1.213793ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:00:30Z"
    - latency: 860.471µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:59:30Z"
    - latency: 984.527µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:58:30Z"
    - latency: 1.003434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:57:30Z"
    - latency: 832.517µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:56:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-225-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-225.ec2.internal
      uid: 3e0ab7f1-cbe5-4e4f-90a7-22db46367abb
    resourceVersion: "54333"
    uid: 7690cc91-8f74-42ef-8a64-384446a99848
  spec:
    sourcePod: network-check-source-989f8b8dc-862fp
    targetEndpoint: a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:36:30Z"
      message: 'load-balancer-api-external: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.918253ms
      message: 'load-balancer-api-external: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:06:30Z"
    - latency: 10.95252ms
      message: 'load-balancer-api-external: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:06:30Z"
    - latency: 5.266879ms
      message: 'load-balancer-api-external: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 7.651644ms
      message: 'load-balancer-api-external: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 5.849026ms
      message: 'load-balancer-api-external: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 7.408945ms
      message: 'load-balancer-api-external: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 5.460505ms
      message: 'load-balancer-api-external: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 7.412081ms
      message: 'load-balancer-api-external: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 4.941055ms
      message: 'load-balancer-api-external: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:02:30Z"
    - latency: 6.498034ms
      message: 'load-balancer-api-external: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-225-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-225.ec2.internal
      uid: 3e0ab7f1-cbe5-4e4f-90a7-22db46367abb
    resourceVersion: "54332"
    uid: 628f883e-d10b-4034-b993-3ba1b7ec77da
  spec:
    sourcePod: network-check-source-989f8b8dc-862fp
    targetEndpoint: a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:36:30Z"
      message: 'load-balancer-api-internal: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.011236ms
      message: 'load-balancer-api-internal: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:06:30Z"
    - latency: 10.896029ms
      message: 'load-balancer-api-internal: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:06:30Z"
    - latency: 5.616089ms
      message: 'load-balancer-api-internal: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 7.70167ms
      message: 'load-balancer-api-internal: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 5.286155ms
      message: 'load-balancer-api-internal: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 7.369678ms
      message: 'load-balancer-api-internal: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 5.3734ms
      message: 'load-balancer-api-internal: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 7.561467ms
      message: 'load-balancer-api-internal: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 5.457763ms
      message: 'load-balancer-api-internal: tcp connection to a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:02:30Z"
    - latency: 6.58205ms
      message: 'load-balancer-api-internal: resolved host name a0bb93a5ede4b4d1c8c1dcef6ceddb3f-78c70dc25cbb9e2d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-225-to-network-check-target-ip-10-0-129-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-225.ec2.internal
      uid: 3e0ab7f1-cbe5-4e4f-90a7-22db46367abb
    resourceVersion: "53510"
    uid: b77f7cf3-75ca-4209-8e3f-740cbc3b9f57
  spec:
    sourcePod: network-check-source-989f8b8dc-862fp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:30Z"
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.293959ms
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 894.692µs
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 1.628102ms
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 959.381µs
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:02:30Z"
    - latency: 1.215154ms
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:01:30Z"
    - latency: 966.127µs
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:00:30Z"
    - latency: 1.561253ms
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:59:30Z"
    - latency: 943.322µs
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:58:30Z"
    - latency: 824.456µs
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:57:30Z"
    - latency: 934.354µs
      message: 'network-check-target-ip-10-0-129-225: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:56:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-225-to-network-check-target-ip-10-0-141-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-225.ec2.internal
      uid: 3e0ab7f1-cbe5-4e4f-90a7-22db46367abb
    resourceVersion: "53512"
    uid: 8f04f037-a7e7-4580-8c9a-299add81c248
  spec:
    sourcePod: network-check-source-989f8b8dc-862fp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:30Z"
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.618366ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 2.179052ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 2.703681ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 2.600706ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:02:30Z"
    - latency: 8.569383ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:01:30Z"
    - latency: 2.431341ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:00:30Z"
    - latency: 2.43715ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:59:30Z"
    - latency: 2.34495ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:58:30Z"
    - latency: 2.311192ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:57:30Z"
    - latency: 2.543545ms
      message: 'network-check-target-ip-10-0-141-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:56:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-225-to-network-check-target-ip-10-0-142-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-225.ec2.internal
      uid: 3e0ab7f1-cbe5-4e4f-90a7-22db46367abb
    resourceVersion: "53511"
    uid: 7b44b8fc-f7da-46b8-baaa-7c4302d59610
  spec:
    sourcePod: network-check-source-989f8b8dc-862fp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:30Z"
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.271183ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 2.397709ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 2.563682ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 2.439458ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:02:30Z"
    - latency: 4.630069ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:01:30Z"
    - latency: 2.168091ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:00:30Z"
    - latency: 2.046313ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:59:30Z"
    - latency: 2.249863ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:58:30Z"
    - latency: 2.266999ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:57:30Z"
    - latency: 2.458063ms
      message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:56:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-225-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-225.ec2.internal
      uid: 3e0ab7f1-cbe5-4e4f-90a7-22db46367abb
    resourceVersion: "54331"
    uid: 4da6d017-36f1-42bf-9776-b07cc81b6209
  spec:
    sourcePod: network-check-source-989f8b8dc-862fp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:36:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.136025ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:06:30Z"
    - latency: 1.807955ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:06:30Z"
    - latency: 1.051734ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 1.968338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:05:30Z"
    - latency: 979.032µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 1.729668ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:04:30Z"
    - latency: 920.457µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 1.9658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:03:30Z"
    - latency: 1.125826ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T16:02:30Z"
    - latency: 1.566923ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T16:02:30Z"
kind: List
metadata:
  resourceVersion: ""