apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:57:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-239-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-239.ec2.internal
      uid: 4bd9b032-e5b4-49d7-89ac-067a9d90e4e8
    resourceVersion: "39324"
    uid: 27a2addf-e6ff-4812-a4a6-99dde340b341
  spec:
    sourcePod: network-check-source-8894fc9bd-qqm97
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:04:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 804.774µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:49Z"
    - latency: 1.256891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:52:49Z"
    - latency: 1.073842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 785µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 1.37844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 1.072941ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 1.313402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:47:49Z"
    - latency: 907.367µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:46:49Z"
    - latency: 873.521µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:45:49Z"
    - latency: 865.163µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:44:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:57:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-239-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-239.ec2.internal
      uid: 4bd9b032-e5b4-49d7-89ac-067a9d90e4e8
    resourceVersion: "38375"
    uid: 73f261be-c065-4c2e-a6b9-8fd0c4ac3174
  spec:
    sourcePod: network-check-source-8894fc9bd-qqm97
    targetEndpoint: a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:03:49Z"
      message: 'load-balancer-api-external: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.010394ms
      message: 'load-balancer-api-external: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 6.951431ms
      message: 'load-balancer-api-external: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 4.241975ms
      message: 'load-balancer-api-external: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 8.581915ms
      message: 'load-balancer-api-external: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 6.124179ms
      message: 'load-balancer-api-external: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 8.785366ms
      message: 'load-balancer-api-external: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 5.429012ms
      message: 'load-balancer-api-external: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 7.481286ms
      message: 'load-balancer-api-external: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 3.991225ms
      message: 'load-balancer-api-external: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:47:49Z"
    - latency: 9.753378ms
      message: 'load-balancer-api-external: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:47:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:57:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-239-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-239.ec2.internal
      uid: 4bd9b032-e5b4-49d7-89ac-067a9d90e4e8
    resourceVersion: "38374"
    uid: 9bdaee60-e286-4b27-b601-5f9a128a2b35
  spec:
    sourcePod: network-check-source-8894fc9bd-qqm97
    targetEndpoint: a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:03:49Z"
      message: 'load-balancer-api-internal: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.046595ms
      message: 'load-balancer-api-internal: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 6.902183ms
      message: 'load-balancer-api-internal: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 3.812646ms
      message: 'load-balancer-api-internal: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 8.477045ms
      message: 'load-balancer-api-internal: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 5.105339ms
      message: 'load-balancer-api-internal: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 8.85213ms
      message: 'load-balancer-api-internal: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 5.420828ms
      message: 'load-balancer-api-internal: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 7.518068ms
      message: 'load-balancer-api-internal: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 4.01722ms
      message: 'load-balancer-api-internal: tcp connection to a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:47:49Z"
    - latency: 9.727113ms
      message: 'load-balancer-api-internal: resolved host name a1c00b575f7e541d3863001ca20ccbd8-d51b52652ada41e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:47:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:57:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-239-to-network-check-target-ip-10-0-129-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-239.ec2.internal
      uid: 4bd9b032-e5b4-49d7-89ac-067a9d90e4e8
    resourceVersion: "39321"
    uid: 143292d9-d533-47d3-a0ba-968b99bd4fa0
  spec:
    sourcePod: network-check-source-8894fc9bd-qqm97
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:04:49Z"
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.105237ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:49Z"
    - latency: 2.197167ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:52:49Z"
    - latency: 2.114742ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 2.250599ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 2.143323ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 2.160825ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 1.996376ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:47:49Z"
    - latency: 2.295801ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:46:49Z"
    - latency: 2.114737ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:45:49Z"
    - latency: 2.420935ms
      message: 'network-check-target-ip-10-0-129-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:44:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:57:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-239-to-network-check-target-ip-10-0-135-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-239.ec2.internal
      uid: 4bd9b032-e5b4-49d7-89ac-067a9d90e4e8
    resourceVersion: "39322"
    uid: 1f115425-cb4a-4f6d-9b52-9a71d87b94a8
  spec:
    sourcePod: network-check-source-8894fc9bd-qqm97
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:04:49Z"
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.558704ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:49Z"
    - latency: 1.839662ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:52:49Z"
    - latency: 1.894257ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 1.678715ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 1.836551ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 1.845561ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 2.173021ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:47:49Z"
    - latency: 2.185559ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:46:49Z"
    - latency: 1.652019ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:45:49Z"
    - latency: 1.829896ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:44:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:57:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-239-to-network-check-target-ip-10-0-137-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-239.ec2.internal
      uid: 4bd9b032-e5b4-49d7-89ac-067a9d90e4e8
    resourceVersion: "39323"
    uid: c3b117e0-79d4-47f3-8c34-80555e6cebce
  spec:
    sourcePod: network-check-source-8894fc9bd-qqm97
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:04:49Z"
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.278006ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:49Z"
    - latency: 1.294695ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:52:49Z"
    - latency: 880.047µs
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 843.248µs
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 1.229379ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 1.328757ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 902.47µs
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:47:49Z"
    - latency: 1.651096ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:46:49Z"
    - latency: 847.55µs
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:45:49Z"
    - latency: 1.556741ms
      message: 'network-check-target-ip-10-0-137-239: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:44:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:57:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-239-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-239.ec2.internal
      uid: 4bd9b032-e5b4-49d7-89ac-067a9d90e4e8
    resourceVersion: "38373"
    uid: b27c88e1-e37d-407b-867d-7397b080c854
  spec:
    sourcePod: network-check-source-8894fc9bd-qqm97
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:03:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.524µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 1.853359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:51:49Z"
    - latency: 741.965µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 2.421708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:50:49Z"
    - latency: 1.026161ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 1.919188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:49:49Z"
    - latency: 1.021178ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 2.094168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:48:49Z"
    - latency: 1.050472ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:47:49Z"
    - latency: 1.941559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:47:49Z"
kind: List
metadata:
  resourceVersion: ""