apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T02:03:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-184-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-184.ec2.internal
      uid: 6eb4d51f-902e-4331-ad47-463c0621bbdd
    resourceVersion: "55017"
    uid: fa8e1ff7-f6a0-49ae-a375-1ee924f1e0ca
  spec:
    sourcePod: network-check-source-989f8b8dc-l8gb2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T02:11:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.771µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 915.483µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 963.217µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 1.211376ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:36:00Z"
    - latency: 928.122µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:35:00Z"
    - latency: 1.182525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:34:00Z"
    - latency: 1.220653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:33:00Z"
    - latency: 878.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:32:00Z"
    - latency: 1.296123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:31:00Z"
    - latency: 901.478µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:30:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T02:03:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-184-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-184.ec2.internal
      uid: 6eb4d51f-902e-4331-ad47-463c0621bbdd
    resourceVersion: "56107"
    uid: 179e2307-a868-4c0a-bf74-c9fe490bf292
  spec:
    sourcePod: network-check-source-989f8b8dc-l8gb2
    targetEndpoint: aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T02:10:00Z"
      message: 'load-balancer-api-external: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.225765ms
      message: 'load-balancer-api-external: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:40:00Z"
    - latency: 7.359358ms
      message: 'load-balancer-api-external: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:40:00Z"
    - latency: 4.829755ms
      message: 'load-balancer-api-external: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 6.05436ms
      message: 'load-balancer-api-external: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 4.697968ms
      message: 'load-balancer-api-external: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 7.499838ms
      message: 'load-balancer-api-external: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 2.908776ms
      message: 'load-balancer-api-external: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 5.970103ms
      message: 'load-balancer-api-external: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 3.574578ms
      message: 'load-balancer-api-external: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:36:00Z"
    - latency: 8.51822ms
      message: 'load-balancer-api-external: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:36:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T02:03:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-184-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-184.ec2.internal
      uid: 6eb4d51f-902e-4331-ad47-463c0621bbdd
    resourceVersion: "56108"
    uid: d005e305-60b4-4a3b-94cf-de19e86536c8
  spec:
    sourcePod: network-check-source-989f8b8dc-l8gb2
    targetEndpoint: aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T02:10:00Z"
      message: 'load-balancer-api-internal: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.262561ms
      message: 'load-balancer-api-internal: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:40:00Z"
    - latency: 7.293591ms
      message: 'load-balancer-api-internal: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:40:00Z"
    - latency: 4.870485ms
      message: 'load-balancer-api-internal: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 6.135323ms
      message: 'load-balancer-api-internal: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 4.684635ms
      message: 'load-balancer-api-internal: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 7.56845ms
      message: 'load-balancer-api-internal: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 3.174863ms
      message: 'load-balancer-api-internal: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 6.018877ms
      message: 'load-balancer-api-internal: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 2.371697ms
      message: 'load-balancer-api-internal: tcp connection to aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:36:00Z"
    - latency: 8.55113ms
      message: 'load-balancer-api-internal: resolved host name aa9a1819ab1b844a1b10879a05e84552-f6e7448c748992fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:36:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T02:03:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-184-to-network-check-target-ip-10-0-130-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-184.ec2.internal
      uid: 6eb4d51f-902e-4331-ad47-463c0621bbdd
    resourceVersion: "55014"
    uid: 1e26938e-9357-4a22-bc23-d7a1d5029731
  spec:
    sourcePod: network-check-source-989f8b8dc-l8gb2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T02:11:00Z"
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.433912ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 1.003237ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 1.053316ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 1.006169ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:36:00Z"
    - latency: 1.140216ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:35:00Z"
    - latency: 1.010141ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:34:00Z"
    - latency: 838.433µs
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:33:00Z"
    - latency: 847.895µs
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:32:00Z"
    - latency: 1.349711ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:31:00Z"
    - latency: 884.993µs
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:30:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T02:03:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-184-to-network-check-target-ip-10-0-131-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-184.ec2.internal
      uid: 6eb4d51f-902e-4331-ad47-463c0621bbdd
    resourceVersion: "55016"
    uid: 23f0344d-610c-4679-b576-dba5e6dd88b0
  spec:
    sourcePod: network-check-source-989f8b8dc-l8gb2
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T02:11:00Z"
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.550511ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 2.271151ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 2.454903ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 2.563697ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:36:00Z"
    - latency: 2.147632ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:35:00Z"
    - latency: 2.6424ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:34:00Z"
    - latency: 2.308785ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:33:00Z"
    - latency: 2.456834ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:32:00Z"
    - latency: 2.184315ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:31:00Z"
    - latency: 2.38211ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:30:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T02:03:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-184-to-network-check-target-ip-10-0-137-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-184.ec2.internal
      uid: 6eb4d51f-902e-4331-ad47-463c0621bbdd
    resourceVersion: "55015"
    uid: 93242a1d-2321-4b89-b4f2-b5ee657baf0e
  spec:
    sourcePod: network-check-source-989f8b8dc-l8gb2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T02:11:00Z"
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.473864ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 2.209545ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 2.288253ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 2.243697ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:36:00Z"
    - latency: 2.016321ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:35:00Z"
    - latency: 2.328203ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:34:00Z"
    - latency: 2.504856ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:33:00Z"
    - latency: 2.272553ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:32:00Z"
    - latency: 2.055842ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:31:00Z"
    - latency: 2.031206ms
      message: 'network-check-target-ip-10-0-137-63: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:30:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T02:03:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-184-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-184.ec2.internal
      uid: 6eb4d51f-902e-4331-ad47-463c0621bbdd
    resourceVersion: "56106"
    uid: e911294b-e1f7-4d95-b47a-e5060f8119ff
  spec:
    sourcePod: network-check-source-989f8b8dc-l8gb2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T02:10:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.186151ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:40:00Z"
    - latency: 1.898639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:40:00Z"
    - latency: 972.592µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 1.90559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:39:00Z"
    - latency: 1.060689ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 1.713653ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:38:00Z"
    - latency: 845.574µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 1.803123ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:37:00Z"
    - latency: 935.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:36:00Z"
    - latency: 1.987592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:36:00Z"
kind: List
metadata:
  resourceVersion: ""