apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-37.ec2.internal
      uid: 79c1a5dc-72b3-400a-9753-9f0612e68886
    resourceVersion: "63041"
    uid: b80845c9-29dc-4efd-a738-08975d89daba
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2kfdx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T23:03:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 806.199µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 1.051995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 1.143308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 1.093916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 1.092898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:34:40Z"
    - latency: 995.841µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:33:40Z"
    - latency: 880.552µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:32:40Z"
    - latency: 1.054411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:31:40Z"
    - latency: 872.006µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:30:40Z"
    - latency: 1.081658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:29:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-37.ec2.internal
      uid: 79c1a5dc-72b3-400a-9753-9f0612e68886
    resourceVersion: "63043"
    uid: 85da4c2c-5584-4025-9f0a-4ab90d3a1529
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2kfdx
    targetEndpoint: a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T23:02:40Z"
      message: 'load-balancer-api-external: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.026114ms
      message: 'load-balancer-api-external: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 7.900238ms
      message: 'load-balancer-api-external: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 4.177084ms
      message: 'load-balancer-api-external: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 8.066211ms
      message: 'load-balancer-api-external: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 5.081073ms
      message: 'load-balancer-api-external: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 7.695176ms
      message: 'load-balancer-api-external: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 3.89482ms
      message: 'load-balancer-api-external: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 7.797125ms
      message: 'load-balancer-api-external: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 3.766885ms
      message: 'load-balancer-api-external: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:34:40Z"
    - latency: 7.517602ms
      message: 'load-balancer-api-external: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:34:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-37.ec2.internal
      uid: 79c1a5dc-72b3-400a-9753-9f0612e68886
    resourceVersion: "63042"
    uid: f86821e4-834e-4d96-a1ba-02dcc05cfd28
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2kfdx
    targetEndpoint: a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T23:02:40Z"
      message: 'load-balancer-api-internal: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.01507ms
      message: 'load-balancer-api-internal: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 8.11141ms
      message: 'load-balancer-api-internal: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 4.159308ms
      message: 'load-balancer-api-internal: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 8.134041ms
      message: 'load-balancer-api-internal: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 3.875086ms
      message: 'load-balancer-api-internal: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 7.766208ms
      message: 'load-balancer-api-internal: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 4.889122ms
      message: 'load-balancer-api-internal: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 7.72637ms
      message: 'load-balancer-api-internal: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 3.811682ms
      message: 'load-balancer-api-internal: tcp connection to a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:34:40Z"
    - latency: 7.418968ms
      message: 'load-balancer-api-internal: resolved host name a87cd87b13e704353ab68ffe89a899eb-720addcafdf0fd55.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:34:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-37-to-network-check-target-ip-10-0-129-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-37.ec2.internal
      uid: 79c1a5dc-72b3-400a-9753-9f0612e68886
    resourceVersion: "63039"
    uid: 3185bbaa-e248-48ec-856e-99deaf0d83fa
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2kfdx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T23:03:40Z"
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.303759ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 2.490624ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 2.316985ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 2.327654ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 2.511677ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:34:40Z"
    - latency: 2.372543ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:33:40Z"
    - latency: 2.174257ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:32:40Z"
    - latency: 2.522064ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:31:40Z"
    - latency: 2.429685ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:30:40Z"
    - latency: 2.325964ms
      message: 'network-check-target-ip-10-0-129-209: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:29:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-37-to-network-check-target-ip-10-0-130-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-37.ec2.internal
      uid: 79c1a5dc-72b3-400a-9753-9f0612e68886
    resourceVersion: "63040"
    uid: 1b079ff4-fca0-4eb9-97c0-80476f8abbe2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2kfdx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T23:03:40Z"
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.562484ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 2.445544ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 2.031602ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 2.456858ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 2.104995ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:34:40Z"
    - latency: 2.292186ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:33:40Z"
    - latency: 2.068573ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:32:40Z"
    - latency: 2.382438ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:31:40Z"
    - latency: 2.283396ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:30:40Z"
    - latency: 1.86155ms
      message: 'network-check-target-ip-10-0-130-50: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:29:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-37-to-network-check-target-ip-10-0-134-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-37.ec2.internal
      uid: 79c1a5dc-72b3-400a-9753-9f0612e68886
    resourceVersion: "63037"
    uid: 529bf336-1977-478d-8b27-b591e1471f91
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2kfdx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T23:03:40Z"
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 691.654µs
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 890.765µs
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 1.30966ms
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 959.314µs
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 884.219µs
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:34:40Z"
    - latency: 851.097µs
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:33:40Z"
    - latency: 758.827µs
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:32:40Z"
    - latency: 831.884µs
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:31:40Z"
    - latency: 863.14µs
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:30:40Z"
    - latency: 836.08µs
      message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:29:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T22:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-37.ec2.internal
      uid: 79c1a5dc-72b3-400a-9753-9f0612e68886
    resourceVersion: "63038"
    uid: a81660da-31af-4c86-916c-7e409b87625e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2kfdx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T23:02:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.175127ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 2.385955ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:38:40Z"
    - latency: 997.365µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 1.654559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:37:40Z"
    - latency: 1.003926ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 1.699784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:36:40Z"
    - latency: 1.103997ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 2.121925ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:35:40Z"
    - latency: 1.316925ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T23:34:40Z"
    - latency: 1.73629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T23:34:40Z"
kind: List
metadata:
  resourceVersion: ""