apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:34:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: fade1145-209f-4081-8e12-1289d7fd2176
    resourceVersion: "53486"
    uid: fa8f01ec-8e61-4454-882c-291abd969665
  spec:
    sourcePod: network-check-source-685456655f-w8mtk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:41: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.167115ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 989.239µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 1.025562ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:06Z"
    - latency: 843.67µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:59:06Z"
    - latency: 1.07196ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:06Z"
    - latency: 815.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:06Z"
    - latency: 1.178309ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:56:06Z"
    - latency: 941.47µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:55:06Z"
    - latency: 1.101348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:54:06Z"
    - latency: 1.069888ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:34:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: fade1145-209f-4081-8e12-1289d7fd2176
    resourceVersion: "55663"
    uid: 5db18952-1c86-44d7-ae9a-e1629289663c
  spec:
    sourcePod: network-check-source-685456655f-w8mtk
    targetEndpoint: a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:40:06Z"
      message: 'load-balancer-api-external: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.309468ms
      message: 'load-balancer-api-external: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:04:06Z"
    - latency: 18.78018ms
      message: 'load-balancer-api-external: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:04:06Z"
    - latency: 3.399089ms
      message: 'load-balancer-api-external: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:03:06Z"
    - latency: 14.085288ms
      message: 'load-balancer-api-external: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:03:06Z"
    - latency: 4.952555ms
      message: 'load-balancer-api-external: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 14.081685ms
      message: 'load-balancer-api-external: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 4.404199ms
      message: 'load-balancer-api-external: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 9.591185ms
      message: 'load-balancer-api-external: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 4.955351ms
      message: 'load-balancer-api-external: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:06Z"
    - latency: 10.790932ms
      message: 'load-balancer-api-external: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:00:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:34:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: fade1145-209f-4081-8e12-1289d7fd2176
    resourceVersion: "55664"
    uid: 2cbca755-6643-4f2e-bbda-a4b3f84025b4
  spec:
    sourcePod: network-check-source-685456655f-w8mtk
    targetEndpoint: a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:40:06Z"
      message: 'load-balancer-api-internal: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.975136ms
      message: 'load-balancer-api-internal: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:04:06Z"
    - latency: 18.818706ms
      message: 'load-balancer-api-internal: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:04:06Z"
    - latency: 3.46095ms
      message: 'load-balancer-api-internal: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:03:06Z"
    - latency: 13.869561ms
      message: 'load-balancer-api-internal: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:03:06Z"
    - latency: 4.990231ms
      message: 'load-balancer-api-internal: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 13.989861ms
      message: 'load-balancer-api-internal: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 4.06838ms
      message: 'load-balancer-api-internal: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 9.513718ms
      message: 'load-balancer-api-internal: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 4.984467ms
      message: 'load-balancer-api-internal: tcp connection to a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:06Z"
    - latency: 10.840113ms
      message: 'load-balancer-api-internal: resolved host name a26dd95a51fab4f2c8e202a90c36c7c3-5ac6bbab3de9a267.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:00:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:34:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-network-check-target-ip-10-0-133-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: fade1145-209f-4081-8e12-1289d7fd2176
    resourceVersion: "53485"
    uid: b0e407d7-c83d-4594-97d1-ff67889c84a4
  spec:
    sourcePod: network-check-source-685456655f-w8mtk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:41:06Z"
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.509778ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 2.314934ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 2.233486ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:06Z"
    - latency: 2.32085ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:59:06Z"
    - latency: 2.174411ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:06Z"
    - latency: 2.032048ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:06Z"
    - latency: 2.551358ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:56:06Z"
    - latency: 2.17915ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:55:06Z"
    - latency: 1.958029ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:54:06Z"
    - latency: 2.199858ms
      message: 'network-check-target-ip-10-0-133-187: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:34:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-network-check-target-ip-10-0-136-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: fade1145-209f-4081-8e12-1289d7fd2176
    resourceVersion: "53484"
    uid: c6b19507-400f-4bbd-936f-c51a7e46119c
  spec:
    sourcePod: network-check-source-685456655f-w8mtk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:41:06Z"
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.26265ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 2.042857ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 1.856556ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:06Z"
    - latency: 1.963617ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:59:06Z"
    - latency: 2.331689ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:06Z"
    - latency: 2.45527ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:06Z"
    - latency: 2.316798ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:56:06Z"
    - latency: 2.507089ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:55:06Z"
    - latency: 2.781518ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:54:06Z"
    - latency: 2.217163ms
      message: 'network-check-target-ip-10-0-136-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:34:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-network-check-target-ip-10-0-139-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: fade1145-209f-4081-8e12-1289d7fd2176
    resourceVersion: "53483"
    uid: 08193663-07bb-4de9-95a4-fbf2af61deb6
  spec:
    sourcePod: network-check-source-685456655f-w8mtk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:41:06Z"
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.000518ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 959.854µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 952.865µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:06Z"
    - latency: 1.383629ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:59:06Z"
    - latency: 1.010295ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:58:06Z"
    - latency: 912.47µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:57:06Z"
    - latency: 890.404µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:56:06Z"
    - latency: 1.120546ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:55:06Z"
    - latency: 1.484153ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:54:06Z"
    - latency: 939.196µs
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:53:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:34:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-41-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-41.ec2.internal
      uid: fade1145-209f-4081-8e12-1289d7fd2176
    resourceVersion: "55661"
    uid: 39158d8a-de55-4c50-be85-c67a6a8f9e87
  spec:
    sourcePod: network-check-source-685456655f-w8mtk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:40:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.792µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:04:06Z"
    - latency: 1.934072ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:04:06Z"
    - latency: 816.788µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:03:06Z"
    - latency: 1.899047ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:03:06Z"
    - latency: 897.116µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 1.642058ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:02:06Z"
    - latency: 1.11027ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 1.924436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:01:06Z"
    - latency: 1.329695ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T12:00:06Z"
    - latency: 1.834948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T12:00:06Z"
kind: List
metadata:
  resourceVersion: ""