apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:27:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-17-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-17.ec2.internal
      uid: f70a6bf4-e1a2-4c18-8238-f8eedd9825d4
    resourceVersion: "52865"
    uid: 4fb7ae16-8cf8-479d-88c6-1d8a4095c8ed
  spec:
    sourcePod: network-check-source-6947749cfc-mkbkq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:34:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:02:06Z"
    - latency: 1.015748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:01:06Z"
    - latency: 859.652µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:00:06Z"
    - latency: 1.01829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:59:06Z"
    - latency: 951.402µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:58:06Z"
    - latency: 1.213581ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 1.210684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 1.006443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 1.07345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 1.222454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:27:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-17-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-17.ec2.internal
      uid: f70a6bf4-e1a2-4c18-8238-f8eedd9825d4
    resourceVersion: "47520"
    uid: 8794cb8a-958d-4df1-84a6-565dace0bf15
  spec:
    sourcePod: network-check-source-6947749cfc-mkbkq
    targetEndpoint: aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:33:06Z"
      message: 'load-balancer-api-external: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.800276ms
      message: 'load-balancer-api-external: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 7.151838ms
      message: 'load-balancer-api-external: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 4.887581ms
      message: 'load-balancer-api-external: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 6.152733ms
      message: 'load-balancer-api-external: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 5.106352ms
      message: 'load-balancer-api-external: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 10.600596ms
      message: 'load-balancer-api-external: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 3.218087ms
      message: 'load-balancer-api-external: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 6.196935ms
      message: 'load-balancer-api-external: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 4.7303ms
      message: 'load-balancer-api-external: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:06Z"
    - latency: 6.476212ms
      message: 'load-balancer-api-external: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:27:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-17-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-17.ec2.internal
      uid: f70a6bf4-e1a2-4c18-8238-f8eedd9825d4
    resourceVersion: "47521"
    uid: a35ef32b-24be-408b-af36-6d044dac705b
  spec:
    sourcePod: network-check-source-6947749cfc-mkbkq
    targetEndpoint: aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:33:06Z"
      message: 'load-balancer-api-internal: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.803145ms
      message: 'load-balancer-api-internal: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 7.213838ms
      message: 'load-balancer-api-internal: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 4.911858ms
      message: 'load-balancer-api-internal: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 6.165495ms
      message: 'load-balancer-api-internal: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 4.719452ms
      message: 'load-balancer-api-internal: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 10.65948ms
      message: 'load-balancer-api-internal: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 5.542936ms
      message: 'load-balancer-api-internal: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 6.175537ms
      message: 'load-balancer-api-internal: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 4.743091ms
      message: 'load-balancer-api-internal: tcp connection to aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:06Z"
    - latency: 6.544514ms
      message: 'load-balancer-api-internal: resolved host name aeaee0017a6914599a2f6598d20023b5-d144671955956197.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:27:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-17-to-network-check-target-ip-10-0-136-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-17.ec2.internal
      uid: f70a6bf4-e1a2-4c18-8238-f8eedd9825d4
    resourceVersion: "52864"
    uid: b64f325a-bf68-4aec-8f63-4ee9841a71d6
  spec:
    sourcePod: network-check-source-6947749cfc-mkbkq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:34:06Z"
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.331907ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:02:06Z"
    - latency: 2.27986ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:01:06Z"
    - latency: 2.525687ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:00:06Z"
    - latency: 2.140535ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:59:06Z"
    - latency: 2.889026ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:58:06Z"
    - latency: 2.402669ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 2.23107ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 2.208848ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 2.332462ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 2.16236ms
      message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:27:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-17-to-network-check-target-ip-10-0-138-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-17.ec2.internal
      uid: f70a6bf4-e1a2-4c18-8238-f8eedd9825d4
    resourceVersion: "52862"
    uid: 9512dcd1-4b11-488a-8ede-40b8e4c7c27e
  spec:
    sourcePod: network-check-source-6947749cfc-mkbkq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:34:06Z"
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.126µs
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:02:06Z"
    - latency: 1.37351ms
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:01:06Z"
    - latency: 932.676µs
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:00:06Z"
    - latency: 1.278014ms
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:59:06Z"
    - latency: 1.212374ms
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:58:06Z"
    - latency: 1.675461ms
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 859.7µs
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 935.09µs
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 865.759µs
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 1.020325ms
      message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:27:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-17-to-network-check-target-ip-10-0-143-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-17.ec2.internal
      uid: f70a6bf4-e1a2-4c18-8238-f8eedd9825d4
    resourceVersion: "52863"
    uid: 51efd21d-670e-4b44-bf4e-7a781ddef24f
  spec:
    sourcePod: network-check-source-6947749cfc-mkbkq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:34:06Z"
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.302633ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:02:06Z"
    - latency: 2.540683ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:01:06Z"
    - latency: 2.594699ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T22:00:06Z"
    - latency: 2.360057ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:59:06Z"
    - latency: 2.345415ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:58:06Z"
    - latency: 2.291779ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 1.984266ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 2.150034ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 2.517343ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 2.401394ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:27:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-17-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-17.ec2.internal
      uid: f70a6bf4-e1a2-4c18-8238-f8eedd9825d4
    resourceVersion: "47519"
    uid: 4194780c-f798-4479-b6f5-fa81916e6402
  spec:
    sourcePod: network-check-source-6947749cfc-mkbkq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:33:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.147442ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 1.840749ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:57:06Z"
    - latency: 1.083272ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 1.729722ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:56:06Z"
    - latency: 974.975µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 1.72948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:55:06Z"
    - latency: 1.017518ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 1.652415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:54:06Z"
    - latency: 930.802µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:06Z"
    - latency: 1.850911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:53:06Z"
kind: List
metadata:
  resourceVersion: ""