apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:04:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: 993c949a-9163-4ec0-b1e2-fd1fb095a544
    resourceVersion: "72326"
    uid: 512ec477-c8cf-495a-a501-864cd0e4ca7b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gzxx6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:11:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026108ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 1.08741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 1.104681ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 1.068172ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 1.224952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:01Z"
    - latency: 1.229354ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:41:01Z"
    - latency: 1.266089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:01Z"
    - latency: 1.011075ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:01Z"
    - latency: 1.015728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:01Z"
    - latency: 1.359958ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:04:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: 993c949a-9163-4ec0-b1e2-fd1fb095a544
    resourceVersion: "72325"
    uid: 0b493009-fcaf-4955-a65c-4de4655c16f3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gzxx6
    targetEndpoint: a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:10:01Z"
      message: 'load-balancer-api-external: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.767852ms
      message: 'load-balancer-api-external: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 6.383259ms
      message: 'load-balancer-api-external: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 3.870733ms
      message: 'load-balancer-api-external: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 6.181101ms
      message: 'load-balancer-api-external: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 4.62381ms
      message: 'load-balancer-api-external: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 7.202698ms
      message: 'load-balancer-api-external: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 4.705616ms
      message: 'load-balancer-api-external: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 9.365462ms
      message: 'load-balancer-api-external: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 9.660528ms
      message: 'load-balancer-api-external: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:01Z"
    - latency: 7.543241ms
      message: 'load-balancer-api-external: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:42:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:04:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: 993c949a-9163-4ec0-b1e2-fd1fb095a544
    resourceVersion: "72327"
    uid: 645281c8-e421-4245-82eb-06abe2158fd7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gzxx6
    targetEndpoint: a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:10:01Z"
      message: 'load-balancer-api-internal: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.556149ms
      message: 'load-balancer-api-internal: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 6.406106ms
      message: 'load-balancer-api-internal: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 11.579535ms
      message: 'load-balancer-api-internal: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 6.161931ms
      message: 'load-balancer-api-internal: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 4.159427ms
      message: 'load-balancer-api-internal: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 7.265384ms
      message: 'load-balancer-api-internal: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 4.393326ms
      message: 'load-balancer-api-internal: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 9.345809ms
      message: 'load-balancer-api-internal: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 9.651171ms
      message: 'load-balancer-api-internal: tcp connection to a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:01Z"
    - latency: 7.573753ms
      message: 'load-balancer-api-internal: resolved host name a11f9e5ab929f4d7283be086db220920-4009fd6c4839e6b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:42:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:04:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-network-check-target-ip-10-0-129-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: 993c949a-9163-4ec0-b1e2-fd1fb095a544
    resourceVersion: "72320"
    uid: f8a5c2d0-0f12-4a19-8eb4-5ef456c565f6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gzxx6
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:11:01Z"
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.620164ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 890.929µs
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 862.906µs
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 873.138µs
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 1.535865ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:01Z"
    - latency: 961.948µs
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:41:01Z"
    - latency: 987.536µs
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:01Z"
    - latency: 1.149551ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:01Z"
    - latency: 1.160745ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:01Z"
    - latency: 1.625193ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:04:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-network-check-target-ip-10-0-129-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: 993c949a-9163-4ec0-b1e2-fd1fb095a544
    resourceVersion: "72324"
    uid: 981ee8ef-6b34-4058-8441-bc75fcb9c10a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gzxx6
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:11:01Z"
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.125924ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 2.060316ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 2.192328ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 2.094191ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 2.156164ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:01Z"
    - latency: 1.890008ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:41:01Z"
    - latency: 1.732749ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:01Z"
    - latency: 2.066602ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:01Z"
    - latency: 2.059552ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:01Z"
    - latency: 2.175328ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:04:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-network-check-target-ip-10-0-130-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: 993c949a-9163-4ec0-b1e2-fd1fb095a544
    resourceVersion: "72323"
    uid: b2914886-0cd0-4dc4-a63b-e28d3b345e56
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gzxx6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:11:01Z"
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376843ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 2.10506ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 2.311134ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 2.351452ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 2.369333ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:01Z"
    - latency: 2.251293ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:41:01Z"
    - latency: 2.321636ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:01Z"
    - latency: 2.41834ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:01Z"
    - latency: 2.224457ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:01Z"
    - latency: 2.337654ms
      message: 'network-check-target-ip-10-0-130-3: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:37:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:04:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: 993c949a-9163-4ec0-b1e2-fd1fb095a544
    resourceVersion: "72322"
    uid: a5435c4b-430c-4fa3-a95f-c7790b1d835b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-gzxx6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:10:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.394µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 1.675281ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:46:01Z"
    - latency: 1.066493ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 1.715435ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:45:01Z"
    - latency: 724.677µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 1.7806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:44:01Z"
    - latency: 1.151047ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 1.783805ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:43:01Z"
    - latency: 813.782µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:01Z"
    - latency: 1.670596ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:42:01Z"
kind: List
metadata:
  resourceVersion: ""