apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T15:27:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-183-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-183.ec2.internal
      uid: f505dcd2-208a-4a96-a8b4-8b627aaeaed5
    resourceVersion: "61892"
    uid: 61755de4-8a29-48e2-9434-0500cfb980ba
  spec:
    sourcePod: network-check-source-685456655f-llcq8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T15:34:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.137673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 981.847µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 1.082697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 942.887µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:59:47Z"
    - latency: 1.104729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:58:47Z"
    - latency: 1.37658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:57:47Z"
    - latency: 1.129411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:56:47Z"
    - latency: 1.090799ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:55:47Z"
    - latency: 1.106476ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:54:47Z"
    - latency: 948.115µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:53:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T15:27:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-183-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-183.ec2.internal
      uid: f505dcd2-208a-4a96-a8b4-8b627aaeaed5
    resourceVersion: "62745"
    uid: b7fcaa2e-c88b-4df1-85ca-a6eca8fd6445
  spec:
    sourcePod: network-check-source-685456655f-llcq8
    targetEndpoint: a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T15:33:47Z"
      message: 'load-balancer-api-external: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.764507ms
      message: 'load-balancer-api-external: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:03:47Z"
    - latency: 6.323425ms
      message: 'load-balancer-api-external: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:03:47Z"
    - latency: 4.95169ms
      message: 'load-balancer-api-external: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 7.593363ms
      message: 'load-balancer-api-external: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 4.715727ms
      message: 'load-balancer-api-external: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 6.839222ms
      message: 'load-balancer-api-external: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 5.289096ms
      message: 'load-balancer-api-external: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 7.132442ms
      message: 'load-balancer-api-external: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 4.945355ms
      message: 'load-balancer-api-external: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:59:47Z"
    - latency: 7.804747ms
      message: 'load-balancer-api-external: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:59:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T15:27:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-183-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-183.ec2.internal
      uid: f505dcd2-208a-4a96-a8b4-8b627aaeaed5
    resourceVersion: "62746"
    uid: 543b9422-ad82-4dd1-80eb-27e77405eac3
  spec:
    sourcePod: network-check-source-685456655f-llcq8
    targetEndpoint: a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T15:33:47Z"
      message: 'load-balancer-api-internal: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.544992ms
      message: 'load-balancer-api-internal: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:03:47Z"
    - latency: 6.297898ms
      message: 'load-balancer-api-internal: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:03:47Z"
    - latency: 4.373354ms
      message: 'load-balancer-api-internal: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 7.617538ms
      message: 'load-balancer-api-internal: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 5.320488ms
      message: 'load-balancer-api-internal: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 6.991609ms
      message: 'load-balancer-api-internal: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 5.418819ms
      message: 'load-balancer-api-internal: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 7.099637ms
      message: 'load-balancer-api-internal: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 5.344117ms
      message: 'load-balancer-api-internal: tcp connection to a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:59:47Z"
    - latency: 7.773951ms
      message: 'load-balancer-api-internal: resolved host name a925a0491511d43ab8c8e57d137dd513-e5f93db10c3e312a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:59:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T15:27:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-183-to-network-check-target-ip-10-0-129-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-183.ec2.internal
      uid: f505dcd2-208a-4a96-a8b4-8b627aaeaed5
    resourceVersion: "61890"
    uid: 32da480d-879c-45e5-adda-7eb622a34544
  spec:
    sourcePod: network-check-source-685456655f-llcq8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T15:34:47Z"
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.456602ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 2.477321ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 2.436445ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 2.809232ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:59:47Z"
    - latency: 2.230007ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:58:47Z"
    - latency: 2.528399ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:57:47Z"
    - latency: 2.459786ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:56:47Z"
    - latency: 2.360646ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:55:47Z"
    - latency: 2.561133ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:54:47Z"
    - latency: 2.686697ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:53:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T15:27:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-183-to-network-check-target-ip-10-0-134-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-183.ec2.internal
      uid: f505dcd2-208a-4a96-a8b4-8b627aaeaed5
    resourceVersion: "61889"
    uid: f51b9671-0310-4fb5-8c6b-49df8059ee67
  spec:
    sourcePod: network-check-source-685456655f-llcq8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T15:34:47Z"
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.236µs
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 1.06381ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 953.492µs
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 946.24µs
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:59:47Z"
    - latency: 749.581µs
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:58:47Z"
    - latency: 995.347µs
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:57:47Z"
    - latency: 1.451138ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:56:47Z"
    - latency: 911.244µs
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:55:47Z"
    - latency: 1.322935ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:54:47Z"
    - latency: 897.67µs
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:53:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T15:27:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-183-to-network-check-target-ip-10-0-140-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-183.ec2.internal
      uid: f505dcd2-208a-4a96-a8b4-8b627aaeaed5
    resourceVersion: "61891"
    uid: ae0f18d4-3b55-4a21-8387-65adc2dd04a7
  spec:
    sourcePod: network-check-source-685456655f-llcq8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T15:34:47Z"
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.45584ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 2.757303ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 2.727235ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 2.757828ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:59:47Z"
    - latency: 2.747955ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:58:47Z"
    - latency: 2.298494ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:57:47Z"
    - latency: 2.375764ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:56:47Z"
    - latency: 2.68849ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:55:47Z"
    - latency: 2.646652ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:54:47Z"
    - latency: 2.528343ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:53:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T15:27:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-183-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-183.ec2.internal
      uid: f505dcd2-208a-4a96-a8b4-8b627aaeaed5
    resourceVersion: "62744"
    uid: 6e9048e3-4467-43e2-8d5e-3cc4e9258764
  spec:
    sourcePod: network-check-source-685456655f-llcq8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T15:33:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.042401ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:03:47Z"
    - latency: 1.730688ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:03:47Z"
    - latency: 1.163145ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 2.142706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:02:47Z"
    - latency: 1.068551ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 2.133986ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:01:47Z"
    - latency: 1.24871ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 1.945336ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:00:47Z"
    - latency: 927.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T15:59:47Z"
    - latency: 2.034776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T15:59:47Z"
kind: List
metadata:
  resourceVersion: ""