apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:54:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 0cf9a770-4c47-4fcf-b81f-b3c773b5a591
    resourceVersion: "32670"
    uid: 00db72a9-e5b5-4ae3-b385-c0607f7c9056
  spec:
    sourcePod: network-check-source-7bc5b6bf85-95wpk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:01:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109002ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 1.11677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 1.071922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 1.022162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 1.297079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:31Z"
    - latency: 1.184903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:31:31Z"
    - latency: 1.348942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:30:31Z"
    - latency: 984.831µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:29:31Z"
    - latency: 981.936µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:28:31Z"
    - latency: 990.494µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:27:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:54:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 0cf9a770-4c47-4fcf-b81f-b3c773b5a591
    resourceVersion: "32672"
    uid: 6bc1f0f6-93d6-46e9-8f57-4968fc5ac5c2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-95wpk
    targetEndpoint: aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:00:31Z"
      message: 'load-balancer-api-external: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.987133ms
      message: 'load-balancer-api-external: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 9.759861ms
      message: 'load-balancer-api-external: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 5.804767ms
      message: 'load-balancer-api-external: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 7.237437ms
      message: 'load-balancer-api-external: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 4.852756ms
      message: 'load-balancer-api-external: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 9.044628ms
      message: 'load-balancer-api-external: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 5.363353ms
      message: 'load-balancer-api-external: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 8.169944ms
      message: 'load-balancer-api-external: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 4.757086ms
      message: 'load-balancer-api-external: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:31Z"
    - latency: 7.276125ms
      message: 'load-balancer-api-external: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:32:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:54:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 0cf9a770-4c47-4fcf-b81f-b3c773b5a591
    resourceVersion: "32673"
    uid: 2ac6f012-e915-4283-b25f-33e9a358729e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-95wpk
    targetEndpoint: aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:00:31Z"
      message: 'load-balancer-api-internal: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.981528ms
      message: 'load-balancer-api-internal: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 9.792092ms
      message: 'load-balancer-api-internal: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 5.036682ms
      message: 'load-balancer-api-internal: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 7.062921ms
      message: 'load-balancer-api-internal: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 5.047681ms
      message: 'load-balancer-api-internal: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 9.144142ms
      message: 'load-balancer-api-internal: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 5.346461ms
      message: 'load-balancer-api-internal: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 8.064818ms
      message: 'load-balancer-api-internal: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 6.3479ms
      message: 'load-balancer-api-internal: tcp connection to aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:31Z"
    - latency: 7.249692ms
      message: 'load-balancer-api-internal: resolved host name aae486d52989c438c9f2a312bb88937b-f200103d0d91b5e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:32:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:54:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-network-check-target-ip-10-0-128-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 0cf9a770-4c47-4fcf-b81f-b3c773b5a591
    resourceVersion: "32667"
    uid: fae2b772-4459-4e17-bec5-ddabff0bb6b3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-95wpk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:01:31Z"
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.31923ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 1.990897ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 2.038434ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 1.912562ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 2.266104ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:31Z"
    - latency: 2.246362ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:31:31Z"
    - latency: 2.13201ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:30:31Z"
    - latency: 2.291203ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:29:31Z"
    - latency: 2.328201ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:28:31Z"
    - latency: 2.247813ms
      message: 'network-check-target-ip-10-0-128-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:27:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:54:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-network-check-target-ip-10-0-129-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 0cf9a770-4c47-4fcf-b81f-b3c773b5a591
    resourceVersion: "32666"
    uid: ebcfd3a7-d911-4210-be4f-cbf298854400
  spec:
    sourcePod: network-check-source-7bc5b6bf85-95wpk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:01:31Z"
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.89µs
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 918.06µs
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 1.047644ms
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 1.132209ms
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 1.822724ms
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:31Z"
    - latency: 954.425µs
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:31:31Z"
    - latency: 1.021559ms
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:30:31Z"
    - latency: 1.065419ms
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:29:31Z"
    - latency: 1.159079ms
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:28:31Z"
    - latency: 861.434µs
      message: 'network-check-target-ip-10-0-129-202: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:27:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:54:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-network-check-target-ip-10-0-131-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 0cf9a770-4c47-4fcf-b81f-b3c773b5a591
    resourceVersion: "32668"
    uid: b574dd8c-acdc-4c8e-a5ff-5d6b6477aa52
  spec:
    sourcePod: network-check-source-7bc5b6bf85-95wpk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:01:31Z"
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.264752ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 2.523256ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 2.242345ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 2.315176ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 2.159667ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:31Z"
    - latency: 2.098362ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:31:31Z"
    - latency: 2.373533ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:30:31Z"
    - latency: 2.271327ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:29:31Z"
    - latency: 2.274ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:28:31Z"
    - latency: 2.067634ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:27:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:54:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-202-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-202.ec2.internal
      uid: 0cf9a770-4c47-4fcf-b81f-b3c773b5a591
    resourceVersion: "32669"
    uid: 86f39f74-7072-4c95-ba6c-9bf5fa25cb03
  spec:
    sourcePod: network-check-source-7bc5b6bf85-95wpk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:00:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.716µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 2.093176ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:36:31Z"
    - latency: 836.888µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 2.158792ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:35:31Z"
    - latency: 948.64µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 1.756702ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:34:31Z"
    - latency: 961.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 1.831531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:33:31Z"
    - latency: 916.436µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:31Z"
    - latency: 1.968676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:32:31Z"
kind: List
metadata:
  resourceVersion: ""