apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:08:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: c29e5ca9-f2fe-4497-89d1-fb349036ac62
    resourceVersion: "58875"
    uid: 28c0ce2b-a35f-4d03-a16f-020a23f9083e
  spec:
    sourcePod: network-check-source-6f8b768455-vpwmx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:15:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.0916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 948.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 948.763µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:34:46Z"
    - latency: 1.03802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:33:46Z"
    - latency: 1.206209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:32:46Z"
    - latency: 1.155027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:31:46Z"
    - latency: 1.510112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:30:46Z"
    - latency: 952.171µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:29:46Z"
    - latency: 1.195346ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:28:46Z"
    - latency: 1.410109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:27:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:08:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: c29e5ca9-f2fe-4497-89d1-fb349036ac62
    resourceVersion: "60755"
    uid: 3b2b4e4a-40a9-4ed9-8513-694451510787
  spec:
    sourcePod: network-check-source-6f8b768455-vpwmx
    targetEndpoint: abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:14:46Z"
      message: 'load-balancer-api-external: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.857711ms
      message: 'load-balancer-api-external: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:38:46Z"
    - latency: 8.524937ms
      message: 'load-balancer-api-external: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:38:46Z"
    - latency: 3.596703ms
      message: 'load-balancer-api-external: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:37:46Z"
    - latency: 6.714481ms
      message: 'load-balancer-api-external: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:37:46Z"
    - latency: 5.928375ms
      message: 'load-balancer-api-external: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 8.183824ms
      message: 'load-balancer-api-external: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 4.243301ms
      message: 'load-balancer-api-external: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 7.206895ms
      message: 'load-balancer-api-external: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 4.731672ms
      message: 'load-balancer-api-external: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:34:46Z"
    - latency: 7.421921ms
      message: 'load-balancer-api-external: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:34:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:08:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: c29e5ca9-f2fe-4497-89d1-fb349036ac62
    resourceVersion: "60754"
    uid: 1b6e7d54-22e9-403f-abd4-0d6d6827988d
  spec:
    sourcePod: network-check-source-6f8b768455-vpwmx
    targetEndpoint: abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:14:46Z"
      message: 'load-balancer-api-internal: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.512205ms
      message: 'load-balancer-api-internal: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:38:46Z"
    - latency: 8.506996ms
      message: 'load-balancer-api-internal: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:38:46Z"
    - latency: 3.615671ms
      message: 'load-balancer-api-internal: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:37:46Z"
    - latency: 6.758814ms
      message: 'load-balancer-api-internal: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:37:46Z"
    - latency: 6.272985ms
      message: 'load-balancer-api-internal: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 8.137879ms
      message: 'load-balancer-api-internal: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 5.299774ms
      message: 'load-balancer-api-internal: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 7.075063ms
      message: 'load-balancer-api-internal: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 4.102029ms
      message: 'load-balancer-api-internal: tcp connection to abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:34:46Z"
    - latency: 7.378073ms
      message: 'load-balancer-api-internal: resolved host name abfa11ae3a2f244b893ad8bad3f5c6dd-982e3ecfdcd7f171.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:34:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:08:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-network-check-target-ip-10-0-129-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: c29e5ca9-f2fe-4497-89d1-fb349036ac62
    resourceVersion: "58872"
    uid: 56a85c41-d66a-447a-91f3-ccb673019738
  spec:
    sourcePod: network-check-source-6f8b768455-vpwmx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:15:46Z"
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.012898ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 1.18353ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 963.302µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:34:46Z"
    - latency: 980.649µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:33:46Z"
    - latency: 939.058µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:32:46Z"
    - latency: 954.14µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:31:46Z"
    - latency: 1.340175ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:30:46Z"
    - latency: 906.191µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:29:46Z"
    - latency: 1.169131ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:28:46Z"
    - latency: 1.037676ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:27:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:08:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-network-check-target-ip-10-0-137-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: c29e5ca9-f2fe-4497-89d1-fb349036ac62
    resourceVersion: "58873"
    uid: 3b8326c5-efc0-4397-852f-add30e2da85a
  spec:
    sourcePod: network-check-source-6f8b768455-vpwmx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:15:46Z"
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.946912ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 1.773887ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 1.499131ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:34:46Z"
    - latency: 2.067286ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:33:46Z"
    - latency: 2.280917ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:32:46Z"
    - latency: 2.176267ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:31:46Z"
    - latency: 1.97411ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:30:46Z"
    - latency: 1.683893ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:29:46Z"
    - latency: 2.144369ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:28:46Z"
    - latency: 2.665546ms
      message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:27:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:08:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-network-check-target-ip-10-0-142-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: c29e5ca9-f2fe-4497-89d1-fb349036ac62
    resourceVersion: "58874"
    uid: 56faa5ae-4304-46eb-92aa-cc14466d3096
  spec:
    sourcePod: network-check-source-6f8b768455-vpwmx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:15:46Z"
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.223931ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 1.960674ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 2.197879ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:34:46Z"
    - latency: 2.251793ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:33:46Z"
    - latency: 2.189832ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:32:46Z"
    - latency: 2.240198ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:31:46Z"
    - latency: 2.387621ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:30:46Z"
    - latency: 2.226146ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:29:46Z"
    - latency: 2.254864ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:28:46Z"
    - latency: 2.248719ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:27:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:08:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: c29e5ca9-f2fe-4497-89d1-fb349036ac62
    resourceVersion: "60753"
    uid: b4a851c4-8732-4a64-94f7-ffa065482bb2
  spec:
    sourcePod: network-check-source-6f8b768455-vpwmx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T21:14:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.00991ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:38:46Z"
    - latency: 1.676032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:38:46Z"
    - latency: 1.043859ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:37:46Z"
    - latency: 1.593804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:37:46Z"
    - latency: 781.455µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 1.955422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:36:46Z"
    - latency: 959.218µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 1.655408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:35:46Z"
    - latency: 893.043µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T21:34:46Z"
    - latency: 2.319081ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T21:34:46Z"
kind: List
metadata:
  resourceVersion: ""