apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-211-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-211.ec2.internal
      uid: 6e42a327-39e6-4872-ba0a-96407cf73aa1
    resourceVersion: "39284"
    uid: 83c0e6e5-5c2e-4ced-9fd2-1f7426ae2557
  spec:
    sourcePod: network-check-source-7cbc45fddc-jxm6x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.053248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:13Z"
    - latency: 1.082812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:13Z"
    - latency: 1.467141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:13Z"
    - latency: 1.71843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:13Z"
    - latency: 1.046113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:13Z"
    - latency: 1.568156ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:13Z"
    - latency: 1.061055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:13Z"
    - latency: 1.10316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:13Z"
    - latency: 1.4367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:13Z"
    - latency: 1.397929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-211-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-211.ec2.internal
      uid: 6e42a327-39e6-4872-ba0a-96407cf73aa1
    resourceVersion: "41822"
    uid: 935ddff9-2e1a-4d12-9968-9298beb7d0fe
  spec:
    sourcePod: network-check-source-7cbc45fddc-jxm6x
    targetEndpoint: afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:05:13Z"
      message: 'load-balancer-api-external: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.646392ms
      message: 'load-balancer-api-external: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:53:13Z"
    - latency: 9.225845ms
      message: 'load-balancer-api-external: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:53:13Z"
    - latency: 6.195397ms
      message: 'load-balancer-api-external: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:52:13Z"
    - latency: 10.223637ms
      message: 'load-balancer-api-external: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:52:13Z"
    - latency: 6.351362ms
      message: 'load-balancer-api-external: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:51:13Z"
    - latency: 9.231044ms
      message: 'load-balancer-api-external: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:51:13Z"
    - latency: 4.942638ms
      message: 'load-balancer-api-external: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:50:13Z"
    - latency: 9.484379ms
      message: 'load-balancer-api-external: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:50:13Z"
    - latency: 5.466806ms
      message: 'load-balancer-api-external: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:49:13Z"
    - latency: 8.859369ms
      message: 'load-balancer-api-external: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:49:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-211-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-211.ec2.internal
      uid: 6e42a327-39e6-4872-ba0a-96407cf73aa1
    resourceVersion: "41821"
    uid: f76e5a90-7f3d-4d60-a592-c49a26b32a71
  spec:
    sourcePod: network-check-source-7cbc45fddc-jxm6x
    targetEndpoint: afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:05:13Z"
      message: 'load-balancer-api-internal: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.994386ms
      message: 'load-balancer-api-internal: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:53:13Z"
    - latency: 9.179839ms
      message: 'load-balancer-api-internal: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:53:13Z"
    - latency: 6.232757ms
      message: 'load-balancer-api-internal: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:52:13Z"
    - latency: 10.195084ms
      message: 'load-balancer-api-internal: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:52:13Z"
    - latency: 5.901722ms
      message: 'load-balancer-api-internal: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:51:13Z"
    - latency: 9.206895ms
      message: 'load-balancer-api-internal: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:51:13Z"
    - latency: 4.932647ms
      message: 'load-balancer-api-internal: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:50:13Z"
    - latency: 9.444324ms
      message: 'load-balancer-api-internal: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:50:13Z"
    - latency: 5.498913ms
      message: 'load-balancer-api-internal: tcp connection to afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:49:13Z"
    - latency: 8.836326ms
      message: 'load-balancer-api-internal: resolved host name afbea7622bd604a2db371513bf6746c3-47d570e514633519.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:49:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-211-to-network-check-target-ip-10-0-128-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-211.ec2.internal
      uid: 6e42a327-39e6-4872-ba0a-96407cf73aa1
    resourceVersion: "39281"
    uid: 9bdd72d2-96c3-4e30-acb3-adc155f0aa8e
  spec:
    sourcePod: network-check-source-7cbc45fddc-jxm6x
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:13Z"
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.001909ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:13Z"
    - latency: 1.142302ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:13Z"
    - latency: 2.204549ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:13Z"
    - latency: 1.008138ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:13Z"
    - latency: 1.036388ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:13Z"
    - latency: 1.633888ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:13Z"
    - latency: 936.601µs
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:13Z"
    - latency: 1.064089ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:13Z"
    - latency: 1.182076ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:13Z"
    - latency: 1.067906ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-211-to-network-check-target-ip-10-0-135-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-211.ec2.internal
      uid: 6e42a327-39e6-4872-ba0a-96407cf73aa1
    resourceVersion: "39282"
    uid: 0fe38b61-5904-4623-8cc5-0bab31843681
  spec:
    sourcePod: network-check-source-7cbc45fddc-jxm6x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:13Z"
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.341415ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:13Z"
    - latency: 2.181195ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:13Z"
    - latency: 1.90309ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:13Z"
    - latency: 2.519355ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:13Z"
    - latency: 1.995251ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:13Z"
    - latency: 2.338101ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:13Z"
    - latency: 2.32566ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:13Z"
    - latency: 2.226822ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:13Z"
    - latency: 2.258743ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:13Z"
    - latency: 2.41815ms
      message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-211-to-network-check-target-ip-10-0-142-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-211.ec2.internal
      uid: 6e42a327-39e6-4872-ba0a-96407cf73aa1
    resourceVersion: "39283"
    uid: 4cae12b3-6444-4925-98e3-118a2f557f6e
  spec:
    sourcePod: network-check-source-7cbc45fddc-jxm6x
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:13Z"
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.287475ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:48:13Z"
    - latency: 2.299561ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:13Z"
    - latency: 2.207809ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:13Z"
    - latency: 2.470869ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:13Z"
    - latency: 2.030786ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:13Z"
    - latency: 2.304226ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:13Z"
    - latency: 2.118609ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:13Z"
    - latency: 2.215193ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:13Z"
    - latency: 2.347844ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:13Z"
    - latency: 2.097019ms
      message: 'network-check-target-ip-10-0-142-18: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-211-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-211.ec2.internal
      uid: 6e42a327-39e6-4872-ba0a-96407cf73aa1
    resourceVersion: "41820"
    uid: f7b7e482-d378-401c-bcb6-9617b23c0923
  spec:
    sourcePod: network-check-source-7cbc45fddc-jxm6x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:05:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.34µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:53:13Z"
    - latency: 2.163473ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:53:13Z"
    - latency: 917.846µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:52:13Z"
    - latency: 2.100262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:52:13Z"
    - latency: 998.653µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:51:13Z"
    - latency: 1.914141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:51:13Z"
    - latency: 1.314927ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:50:13Z"
    - latency: 2.211643ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:50:13Z"
    - latency: 832.892µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:49:13Z"
    - latency: 2.39296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:49:13Z"
kind: List
metadata:
  resourceVersion: ""