apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:21:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-48.ec2.internal
      uid: fd0b066f-0c53-4326-89d7-430358852cfc
    resourceVersion: "65837"
    uid: c0738187-7581-4aa4-89f4-c8cccb3ac6d9
  spec:
    sourcePod: network-check-source-6f8b768455-4d79x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:28:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.117µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 1.773431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 1.303319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 3.537694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:23Z"
    - latency: 1.168319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:23Z"
    - latency: 1.366939ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:51:23Z"
    - latency: 903.962µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:50:23Z"
    - latency: 1.353209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:49:23Z"
    - latency: 985.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:48:23Z"
    - latency: 1.232679ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:47:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:21:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-48.ec2.internal
      uid: fd0b066f-0c53-4326-89d7-430358852cfc
    resourceVersion: "66541"
    uid: f8ffe806-42ac-4b95-8776-e42ef4dddddb
  spec:
    sourcePod: network-check-source-6f8b768455-4d79x
    targetEndpoint: ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:27:23Z"
      message: 'load-balancer-api-external: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.249485ms
      message: 'load-balancer-api-external: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:57:23Z"
    - latency: 8.54871ms
      message: 'load-balancer-api-external: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:57:23Z"
    - latency: 5.892698ms
      message: 'load-balancer-api-external: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 13.83672ms
      message: 'load-balancer-api-external: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 5.311283ms
      message: 'load-balancer-api-external: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 8.635623ms
      message: 'load-balancer-api-external: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 4.602784ms
      message: 'load-balancer-api-external: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 8.569902ms
      message: 'load-balancer-api-external: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 3.794348ms
      message: 'load-balancer-api-external: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:23Z"
    - latency: 13.369285ms
      message: 'load-balancer-api-external: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:53:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:21:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-48.ec2.internal
      uid: fd0b066f-0c53-4326-89d7-430358852cfc
    resourceVersion: "66542"
    uid: bd32f81f-169b-4a00-b98b-d5cf43d946a3
  spec:
    sourcePod: network-check-source-6f8b768455-4d79x
    targetEndpoint: ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:27:23Z"
      message: 'load-balancer-api-internal: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.966788ms
      message: 'load-balancer-api-internal: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:57:23Z"
    - latency: 8.627529ms
      message: 'load-balancer-api-internal: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:57:23Z"
    - latency: 6.056761ms
      message: 'load-balancer-api-internal: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 13.963696ms
      message: 'load-balancer-api-internal: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 4.772051ms
      message: 'load-balancer-api-internal: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 8.736891ms
      message: 'load-balancer-api-internal: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 4.678766ms
      message: 'load-balancer-api-internal: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 8.633934ms
      message: 'load-balancer-api-internal: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 3.361983ms
      message: 'load-balancer-api-internal: tcp connection to ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:23Z"
    - latency: 13.610126ms
      message: 'load-balancer-api-internal: resolved host name ac590ef7b77854563ad089e354e06b58-a6b52b39ece73551.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:53:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:21:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-48-to-network-check-target-ip-10-0-128-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-48.ec2.internal
      uid: fd0b066f-0c53-4326-89d7-430358852cfc
    resourceVersion: "65833"
    uid: f5955f43-2369-4b1a-bec4-c5cafe734924
  spec:
    sourcePod: network-check-source-6f8b768455-4d79x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:28:23Z"
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.281746ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 2.859371ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 2.25233ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 6.35583ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:23Z"
    - latency: 2.457171ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:23Z"
    - latency: 2.819856ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:51:23Z"
    - latency: 3.049266ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:50:23Z"
    - latency: 2.222102ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:49:23Z"
    - latency: 2.628747ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:48:23Z"
    - latency: 2.462316ms
      message: 'network-check-target-ip-10-0-128-111: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:47:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:21:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-48-to-network-check-target-ip-10-0-137-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-48.ec2.internal
      uid: fd0b066f-0c53-4326-89d7-430358852cfc
    resourceVersion: "65834"
    uid: ba12e06f-bbea-429e-8a14-e58f31a070a8
  spec:
    sourcePod: network-check-source-6f8b768455-4d79x
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:28:23Z"
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.580539ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 2.379188ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 2.379573ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 2.762149ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:23Z"
    - latency: 2.908463ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:23Z"
    - latency: 2.746379ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:51:23Z"
    - latency: 2.624141ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:50:23Z"
    - latency: 2.735446ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:49:23Z"
    - latency: 2.553888ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:48:23Z"
    - latency: 2.430809ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:47:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:21:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-48-to-network-check-target-ip-10-0-143-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-48.ec2.internal
      uid: fd0b066f-0c53-4326-89d7-430358852cfc
    resourceVersion: "65832"
    uid: 2795b512-92c4-4b2c-94fe-cb51f4e5ca76
  spec:
    sourcePod: network-check-source-6f8b768455-4d79x
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:28:23Z"
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.875µs
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 1.834422ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 1.562293ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 4.034147ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:23Z"
    - latency: 1.797744ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:23Z"
    - latency: 1.031839ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:51:23Z"
    - latency: 1.659479ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:50:23Z"
    - latency: 840.887µs
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:49:23Z"
    - latency: 2.185826ms
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:48:23Z"
    - latency: 820.305µs
      message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:47:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:21:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-48.ec2.internal
      uid: fd0b066f-0c53-4326-89d7-430358852cfc
    resourceVersion: "66540"
    uid: 49da74b7-2393-445f-b2c5-0e607c369ccd
  spec:
    sourcePod: network-check-source-6f8b768455-4d79x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:27:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.464µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:57:23Z"
    - latency: 2.123503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:57:23Z"
    - latency: 888.341µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 2.504957ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:56:23Z"
    - latency: 932.626µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 2.068543ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:55:23Z"
    - latency: 868.533µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 1.777791ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:54:23Z"
    - latency: 1.513983ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:23Z"
    - latency: 3.093966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:53:23Z"
kind: List
metadata:
  resourceVersion: ""