apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:59:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 680674c4-c1a6-4c9a-9c08-0fc47fa76cda
    resourceVersion: "57830"
    uid: f5427503-368f-4f56-8f32-f79e9fd809b3
  spec:
    sourcePod: network-check-source-6f8b768455-t82dg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:06:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.776082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 1.187767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 2.602044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:10Z"
    - latency: 995.652µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:24:10Z"
    - latency: 976.951µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:23:10Z"
    - latency: 1.002072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:22:10Z"
    - latency: 859.246µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:21:10Z"
    - latency: 1.031874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:20:10Z"
    - latency: 1.31872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:19:10Z"
    - latency: 896.678µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:18:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:59:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 680674c4-c1a6-4c9a-9c08-0fc47fa76cda
    resourceVersion: "59648"
    uid: 88619d55-a465-408f-aed9-709138a28ae6
  spec:
    sourcePod: network-check-source-6f8b768455-t82dg
    targetEndpoint: ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:05:10Z"
      message: 'load-balancer-api-external: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.769131ms
      message: 'load-balancer-api-external: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:29:10Z"
    - latency: 6.831906ms
      message: 'load-balancer-api-external: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:29:10Z"
    - latency: 5.051809ms
      message: 'load-balancer-api-external: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:28:10Z"
    - latency: 6.784929ms
      message: 'load-balancer-api-external: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:28:10Z"
    - latency: 4.621058ms
      message: 'load-balancer-api-external: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 6.580644ms
      message: 'load-balancer-api-external: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 5.433032ms
      message: 'load-balancer-api-external: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 7.381137ms
      message: 'load-balancer-api-external: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 5.083115ms
      message: 'load-balancer-api-external: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:10Z"
    - latency: 17.187416ms
      message: 'load-balancer-api-external: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:25:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:59:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 680674c4-c1a6-4c9a-9c08-0fc47fa76cda
    resourceVersion: "59647"
    uid: 002c1391-652a-4fc8-a6eb-e5ce72c4f1e6
  spec:
    sourcePod: network-check-source-6f8b768455-t82dg
    targetEndpoint: ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:05:10Z"
      message: 'load-balancer-api-internal: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.742495ms
      message: 'load-balancer-api-internal: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:29:10Z"
    - latency: 6.879799ms
      message: 'load-balancer-api-internal: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:29:10Z"
    - latency: 5.436411ms
      message: 'load-balancer-api-internal: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:28:10Z"
    - latency: 6.674243ms
      message: 'load-balancer-api-internal: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:28:10Z"
    - latency: 4.348978ms
      message: 'load-balancer-api-internal: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 6.706799ms
      message: 'load-balancer-api-internal: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 6.069212ms
      message: 'load-balancer-api-internal: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 7.316944ms
      message: 'load-balancer-api-internal: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 5.084975ms
      message: 'load-balancer-api-internal: tcp connection to ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:10Z"
    - latency: 17.278836ms
      message: 'load-balancer-api-internal: resolved host name ae6d32bd643064e67901fc84697c890f-e8d5e798c9ff3168.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:25:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:59:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-ip-10-0-129-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 680674c4-c1a6-4c9a-9c08-0fc47fa76cda
    resourceVersion: "57827"
    uid: 993a5231-d697-43bb-9434-674b3213046b
  spec:
    sourcePod: network-check-source-6f8b768455-t82dg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:06:10Z"
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.114359ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 2.115429ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 2.189166ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:10Z"
    - latency: 2.113345ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:24:10Z"
    - latency: 2.123596ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:23:10Z"
    - latency: 2.219031ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:22:10Z"
    - latency: 1.641989ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:21:10Z"
    - latency: 2.242468ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:20:10Z"
    - latency: 2.156565ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:19:10Z"
    - latency: 1.935531ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:18:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:59:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-ip-10-0-136-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 680674c4-c1a6-4c9a-9c08-0fc47fa76cda
    resourceVersion: "57829"
    uid: 8354c66a-ba55-4a88-b547-589511e5d2d9
  spec:
    sourcePod: network-check-source-6f8b768455-t82dg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:06:10Z"
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020114ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 1.013212ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 3.267245ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:10Z"
    - latency: 1.371357ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:24:10Z"
    - latency: 1.116381ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:23:10Z"
    - latency: 1.523847ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:22:10Z"
    - latency: 1.15393ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:21:10Z"
    - latency: 1.395105ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:20:10Z"
    - latency: 1.042743ms
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:19:10Z"
    - latency: 976.122µs
      message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:18:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:59:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-ip-10-0-141-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 680674c4-c1a6-4c9a-9c08-0fc47fa76cda
    resourceVersion: "57828"
    uid: c4fb210e-9992-40b2-b72f-1e152249a5df
  spec:
    sourcePod: network-check-source-6f8b768455-t82dg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:06:10Z"
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.155092ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 2.035671ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 2.64532ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:10Z"
    - latency: 2.366211ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:24:10Z"
    - latency: 2.060821ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:23:10Z"
    - latency: 2.490275ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:22:10Z"
    - latency: 1.856197ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:21:10Z"
    - latency: 2.369658ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:20:10Z"
    - latency: 2.203161ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:19:10Z"
    - latency: 2.115388ms
      message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:18:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:59:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-96-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-96.ec2.internal
      uid: 680674c4-c1a6-4c9a-9c08-0fc47fa76cda
    resourceVersion: "59646"
    uid: c2cc98d3-3dcb-4324-b323-18e228480b66
  spec:
    sourcePod: network-check-source-6f8b768455-t82dg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:05:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.68µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:29:10Z"
    - latency: 2.174268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:29:10Z"
    - latency: 1.102764ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:28:10Z"
    - latency: 2.024668ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:28:10Z"
    - latency: 1.080373ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 1.84465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:27:10Z"
    - latency: 951.868µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 1.928805ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:26:10Z"
    - latency: 1.277051ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:10Z"
    - latency: 10.313228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:25:10Z"
kind: List
metadata:
  resourceVersion: ""