apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-138-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-138.ec2.internal
      uid: dd984c33-3f0f-460f-b3d7-153e2e3b6324
    resourceVersion: "64748"
    uid: 40c143b4-8705-4cd8-a152-2f0561c1fb01
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wcfrx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:38:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.033345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 1.175808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 1.257276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 882.399µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 1.237533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:09:05Z"
    - latency: 974.21µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:08:05Z"
    - latency: 1.047429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:07:05Z"
    - latency: 1.635817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:06:05Z"
    - latency: 1.150286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:05:05Z"
    - latency: 1.01836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-138-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-138.ec2.internal
      uid: dd984c33-3f0f-460f-b3d7-153e2e3b6324
    resourceVersion: "64750"
    uid: 23a99a26-83ce-4780-8029-b360d7581334
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wcfrx
    targetEndpoint: ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:37:05Z"
      message: 'load-balancer-api-external: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.990842ms
      message: 'load-balancer-api-external: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 7.605715ms
      message: 'load-balancer-api-external: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 4.048981ms
      message: 'load-balancer-api-external: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 6.17436ms
      message: 'load-balancer-api-external: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 4.404624ms
      message: 'load-balancer-api-external: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 7.007809ms
      message: 'load-balancer-api-external: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 3.997618ms
      message: 'load-balancer-api-external: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 7.35354ms
      message: 'load-balancer-api-external: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 4.308834ms
      message: 'load-balancer-api-external: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:09:05Z"
    - latency: 8.195907ms
      message: 'load-balancer-api-external: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:09:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-138-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-138.ec2.internal
      uid: dd984c33-3f0f-460f-b3d7-153e2e3b6324
    resourceVersion: "64749"
    uid: ce937847-1af5-42f9-b1ae-7eae592f46f6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wcfrx
    targetEndpoint: ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:37:05Z"
      message: 'load-balancer-api-internal: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.053643ms
      message: 'load-balancer-api-internal: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 7.570207ms
      message: 'load-balancer-api-internal: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 3.389775ms
      message: 'load-balancer-api-internal: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 6.231108ms
      message: 'load-balancer-api-internal: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 4.536397ms
      message: 'load-balancer-api-internal: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 7.278229ms
      message: 'load-balancer-api-internal: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 4.127749ms
      message: 'load-balancer-api-internal: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 7.44426ms
      message: 'load-balancer-api-internal: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 4.282559ms
      message: 'load-balancer-api-internal: tcp connection to ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:09:05Z"
    - latency: 8.245047ms
      message: 'load-balancer-api-internal: resolved host name ab2d52400b65345dab4414fc41194d83-53dad0e3033a25b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:09:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-138-to-network-check-target-ip-10-0-133-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-138.ec2.internal
      uid: dd984c33-3f0f-460f-b3d7-153e2e3b6324
    resourceVersion: "64746"
    uid: c1f0f766-71e9-4fc4-9c76-abb9c8885951
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wcfrx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:38:05Z"
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.401471ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 2.438476ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 2.689951ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 2.18695ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 2.073856ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:09:05Z"
    - latency: 1.909408ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:08:05Z"
    - latency: 2.376063ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:07:05Z"
    - latency: 2.137118ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:06:05Z"
    - latency: 2.327607ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:05:05Z"
    - latency: 2.834561ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-138-to-network-check-target-ip-10-0-139-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-138.ec2.internal
      uid: dd984c33-3f0f-460f-b3d7-153e2e3b6324
    resourceVersion: "64745"
    uid: 2dcdd456-bde6-46c4-9803-594c2dacd63e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wcfrx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:38:05Z"
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.148279ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 1.856752ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 2.28111ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 2.413624ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 2.409456ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:09:05Z"
    - latency: 2.387148ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:08:05Z"
    - latency: 2.025319ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:07:05Z"
    - latency: 2.684114ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:06:05Z"
    - latency: 2.488799ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:05:05Z"
    - latency: 2.10273ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-138-to-network-check-target-ip-10-0-139-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-138.ec2.internal
      uid: dd984c33-3f0f-460f-b3d7-153e2e3b6324
    resourceVersion: "64744"
    uid: b13ca1d0-47dd-4976-86f5-181719d30653
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wcfrx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:38:05Z"
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 988.319µs
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 868.722µs
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 986.731µs
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 879.776µs
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 1.539598ms
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:09:05Z"
    - latency: 866.759µs
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:08:05Z"
    - latency: 1.315461ms
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:07:05Z"
    - latency: 888.618µs
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:06:05Z"
    - latency: 1.0904ms
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:05:05Z"
    - latency: 854.616µs
      message: 'network-check-target-ip-10-0-139-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-138-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-138.ec2.internal
      uid: dd984c33-3f0f-460f-b3d7-153e2e3b6324
    resourceVersion: "64747"
    uid: 61a599bf-3ab9-4f84-b9e6-36ac7a872820
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wcfrx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:37:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 862.348µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 1.880164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:13:05Z"
    - latency: 830.033µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 1.861374ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:12:05Z"
    - latency: 825.695µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 1.729404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:11:05Z"
    - latency: 1.172841ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 1.909819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:10:05Z"
    - latency: 941.198µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:09:05Z"
    - latency: 2.130582ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:09:05Z"
kind: List
metadata:
  resourceVersion: ""