apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-29-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-29.ec2.internal
      uid: 6a9737f6-c67f-48cd-9189-a23db45225ca
    resourceVersion: "22234"
    uid: a3ded643-4d93-46f9-bcba-ec7b6ff7fee5
  spec:
    sourcePod: network-check-source-6f8b768455-s57pz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.215µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 1.1824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:43Z"
    - latency: 917.227µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:01:43Z"
    - latency: 812.255µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:00:43Z"
    - latency: 980.804µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:59:43Z"
    - latency: 925.763µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:58:43Z"
    - latency: 1.309498ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:57:43Z"
    - latency: 1.147885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:56:43Z"
    - latency: 1.282305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:55:43Z"
    - latency: 1.145235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-29-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-29.ec2.internal
      uid: 6a9737f6-c67f-48cd-9189-a23db45225ca
    resourceVersion: "23222"
    uid: 189a2efc-0ac1-4a54-b7dc-f3defe54f45a
  spec:
    sourcePod: network-check-source-6f8b768455-s57pz
    targetEndpoint: a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:48:43Z"
      message: 'load-balancer-api-external: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.766651ms
      message: 'load-balancer-api-external: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:43Z"
    - latency: 9.516287ms
      message: 'load-balancer-api-external: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:06:43Z"
    - latency: 5.103519ms
      message: 'load-balancer-api-external: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:43Z"
    - latency: 12.612237ms
      message: 'load-balancer-api-external: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:05:43Z"
    - latency: 4.289767ms
      message: 'load-balancer-api-external: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:43Z"
    - latency: 9.970531ms
      message: 'load-balancer-api-external: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:04:43Z"
    - latency: 6.874343ms
      message: 'load-balancer-api-external: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 8.835979ms
      message: 'load-balancer-api-external: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 5.162985ms
      message: 'load-balancer-api-external: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:43Z"
    - latency: 7.925041ms
      message: 'load-balancer-api-external: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:02:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-29-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-29.ec2.internal
      uid: 6a9737f6-c67f-48cd-9189-a23db45225ca
    resourceVersion: "23223"
    uid: e9fa00c7-07c8-4787-8e6e-b3907a3416dd
  spec:
    sourcePod: network-check-source-6f8b768455-s57pz
    targetEndpoint: a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:48:43Z"
      message: 'load-balancer-api-internal: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.807455ms
      message: 'load-balancer-api-internal: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:43Z"
    - latency: 9.419008ms
      message: 'load-balancer-api-internal: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:06:43Z"
    - latency: 5.141369ms
      message: 'load-balancer-api-internal: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:43Z"
    - latency: 12.526869ms
      message: 'load-balancer-api-internal: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:05:43Z"
    - latency: 4.272979ms
      message: 'load-balancer-api-internal: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:43Z"
    - latency: 9.870109ms
      message: 'load-balancer-api-internal: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:04:43Z"
    - latency: 5.968958ms
      message: 'load-balancer-api-internal: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 8.92278ms
      message: 'load-balancer-api-internal: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 5.203027ms
      message: 'load-balancer-api-internal: tcp connection to a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:43Z"
    - latency: 7.802252ms
      message: 'load-balancer-api-internal: resolved host name a76f9caa18f2941bc9b319dfcaba4997-95c7c8aa4b0389e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:02:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-29-to-network-check-target-ip-10-0-129-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-29.ec2.internal
      uid: 6a9737f6-c67f-48cd-9189-a23db45225ca
    resourceVersion: "22233"
    uid: 8293ab12-d7c3-40c5-b4de-0d6f99dcd911
  spec:
    sourcePod: network-check-source-6f8b768455-s57pz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:43Z"
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.368879ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 2.296467ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:43Z"
    - latency: 2.325046ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:01:43Z"
    - latency: 2.369633ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:00:43Z"
    - latency: 2.064993ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:59:43Z"
    - latency: 2.250734ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:58:43Z"
    - latency: 2.079824ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:57:43Z"
    - latency: 2.136761ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:56:43Z"
    - latency: 2.259176ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:55:43Z"
    - latency: 2.201587ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-29-to-network-check-target-ip-10-0-133-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-29.ec2.internal
      uid: 6a9737f6-c67f-48cd-9189-a23db45225ca
    resourceVersion: "22231"
    uid: 82b3ff8c-58bd-41e3-8d9a-3230040af9ea
  spec:
    sourcePod: network-check-source-6f8b768455-s57pz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:43Z"
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.234005ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 836.157µs
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:43Z"
    - latency: 1.368167ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:01:43Z"
    - latency: 836.515µs
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:00:43Z"
    - latency: 910.469µs
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:59:43Z"
    - latency: 833.465µs
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:58:43Z"
    - latency: 786.922µs
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:57:43Z"
    - latency: 889.936µs
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:56:43Z"
    - latency: 1.132917ms
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:55:43Z"
    - latency: 814.343µs
      message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-29-to-network-check-target-ip-10-0-143-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-29.ec2.internal
      uid: 6a9737f6-c67f-48cd-9189-a23db45225ca
    resourceVersion: "22232"
    uid: c030a07e-f9f0-4acd-ad40-96f0aa1aaa57
  spec:
    sourcePod: network-check-source-6f8b768455-s57pz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:43Z"
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.095996ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 2.038511ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:43Z"
    - latency: 2.059086ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:01:43Z"
    - latency: 1.874692ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:00:43Z"
    - latency: 1.85143ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:59:43Z"
    - latency: 1.881089ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:58:43Z"
    - latency: 2.048317ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:57:43Z"
    - latency: 1.645851ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:56:43Z"
    - latency: 1.862239ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:55:43Z"
    - latency: 1.675837ms
      message: 'network-check-target-ip-10-0-143-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:54:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-29-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-29.ec2.internal
      uid: 6a9737f6-c67f-48cd-9189-a23db45225ca
    resourceVersion: "23221"
    uid: 3892ae73-6247-45e3-a3cf-5e631680f1fe
  spec:
    sourcePod: network-check-source-6f8b768455-s57pz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:48:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.220666ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:43Z"
    - latency: 2.020066ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:06:43Z"
    - latency: 1.055191ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:43Z"
    - latency: 1.960168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:05:43Z"
    - latency: 1.031839ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:43Z"
    - latency: 1.687901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:04:43Z"
    - latency: 807.693µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 2.153271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:03:43Z"
    - latency: 755.989µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:43Z"
    - latency: 1.650853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:02:43Z"
kind: List
metadata:
  resourceVersion: ""