apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:07:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-14-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-14.ec2.internal
      uid: 43b0c4e9-18c8-423b-8dec-b1a25db6a046
    resourceVersion: "56803"
    uid: da1e4113-516d-4cb6-94aa-3a39ca13ce1a
  spec:
    sourcePod: network-check-source-6f8b768455-whm76
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:14:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.197µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 982.197µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 1.249704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 919.226µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:39:49Z"
    - latency: 1.158128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:38:49Z"
    - latency: 1.759689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:37:49Z"
    - latency: 977.297µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:36:49Z"
    - latency: 966.535µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:35:49Z"
    - latency: 1.050088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:34:49Z"
    - latency: 1.010573ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:33:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-14-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-14.ec2.internal
      uid: 43b0c4e9-18c8-423b-8dec-b1a25db6a046
    resourceVersion: "57745"
    uid: 523bf55e-7c43-45aa-bfb0-f6c0239792d0
  spec:
    sourcePod: network-check-source-6f8b768455-whm76
    targetEndpoint: aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:13:49Z"
      message: 'load-balancer-api-external: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.678304ms
      message: 'load-balancer-api-external: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:43:49Z"
    - latency: 6.505584ms
      message: 'load-balancer-api-external: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:43:49Z"
    - latency: 5.360879ms
      message: 'load-balancer-api-external: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 9.556595ms
      message: 'load-balancer-api-external: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 4.93151ms
      message: 'load-balancer-api-external: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 10.667729ms
      message: 'load-balancer-api-external: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 7.399651ms
      message: 'load-balancer-api-external: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 7.121914ms
      message: 'load-balancer-api-external: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 5.545272ms
      message: 'load-balancer-api-external: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:39:49Z"
    - latency: 6.937908ms
      message: 'load-balancer-api-external: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:39:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-14-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-14.ec2.internal
      uid: 43b0c4e9-18c8-423b-8dec-b1a25db6a046
    resourceVersion: "57746"
    uid: 20061b30-92d7-44fe-8d9a-52d956ecf9d9
  spec:
    sourcePod: network-check-source-6f8b768455-whm76
    targetEndpoint: aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:13:49Z"
      message: 'load-balancer-api-internal: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.712083ms
      message: 'load-balancer-api-internal: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:43:49Z"
    - latency: 6.404801ms
      message: 'load-balancer-api-internal: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:43:49Z"
    - latency: 4.840271ms
      message: 'load-balancer-api-internal: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 9.596509ms
      message: 'load-balancer-api-internal: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 4.94477ms
      message: 'load-balancer-api-internal: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 10.579415ms
      message: 'load-balancer-api-internal: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 3.537467ms
      message: 'load-balancer-api-internal: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 7.22819ms
      message: 'load-balancer-api-internal: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 5.588566ms
      message: 'load-balancer-api-internal: tcp connection to aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:39:49Z"
    - latency: 6.831989ms
      message: 'load-balancer-api-internal: resolved host name aebf72fcd55634690b223453614c4244-31c980ab636d2fff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:39:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-14-to-network-check-target-ip-10-0-136-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-14.ec2.internal
      uid: 43b0c4e9-18c8-423b-8dec-b1a25db6a046
    resourceVersion: "56800"
    uid: 88bf147e-862c-4edf-aa84-637fc5f43392
  spec:
    sourcePod: network-check-source-6f8b768455-whm76
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:14:49Z"
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.232125ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 963.047µs
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 1.106702ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 968.141µs
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:39:49Z"
    - latency: 1.40858ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:38:49Z"
    - latency: 2.240234ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:37:49Z"
    - latency: 976.269µs
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:36:49Z"
    - latency: 1.068575ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:35:49Z"
    - latency: 927.29µs
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:34:49Z"
    - latency: 1.194696ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:33:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-14-to-network-check-target-ip-10-0-142-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-14.ec2.internal
      uid: 43b0c4e9-18c8-423b-8dec-b1a25db6a046
    resourceVersion: "56801"
    uid: 493efc7f-fad2-466a-9779-a90b903b99d0
  spec:
    sourcePod: network-check-source-6f8b768455-whm76
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:14:49Z"
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.164166ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 3.692334ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 2.461553ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 2.575083ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:39:49Z"
    - latency: 2.329011ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:38:49Z"
    - latency: 1.992494ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:37:49Z"
    - latency: 1.922646ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:36:49Z"
    - latency: 1.939829ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:35:49Z"
    - latency: 2.138666ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:34:49Z"
    - latency: 2.192827ms
      message: 'network-check-target-ip-10-0-142-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:33:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-14-to-network-check-target-ip-10-0-143-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-14.ec2.internal
      uid: 43b0c4e9-18c8-423b-8dec-b1a25db6a046
    resourceVersion: "56802"
    uid: b655979a-9f60-46e1-be7c-9a7d6377ef2d
  spec:
    sourcePod: network-check-source-6f8b768455-whm76
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:14:49Z"
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.483775ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 2.612992ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 2.540063ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 2.351897ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:39:49Z"
    - latency: 2.405357ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:38:49Z"
    - latency: 2.05607ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:37:49Z"
    - latency: 2.314758ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:36:49Z"
    - latency: 2.356781ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:35:49Z"
    - latency: 2.227097ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:34:49Z"
    - latency: 2.368474ms
      message: 'network-check-target-ip-10-0-143-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:33:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-14-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-14.ec2.internal
      uid: 43b0c4e9-18c8-423b-8dec-b1a25db6a046
    resourceVersion: "57744"
    uid: 3187610d-4923-4e3f-baec-a8f77ee4980f
  spec:
    sourcePod: network-check-source-6f8b768455-whm76
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:13:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.27µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:43:49Z"
    - latency: 1.822618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:43:49Z"
    - latency: 1.122699ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 2.173839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:42:49Z"
    - latency: 1.694537ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 1.96471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:41:49Z"
    - latency: 841.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 1.80408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:40:49Z"
    - latency: 1.112494ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:39:49Z"
    - latency: 1.746978ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:39:49Z"
kind: List
metadata:
  resourceVersion: ""