apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T02:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-215-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-215.ec2.internal
      uid: 836b9add-b511-4992-ae35-f5ea9a92b82a
    resourceVersion: "61730"
    uid: 97bb1034-6993-40bb-ac5f-fb932c950a5e
  spec:
    sourcePod: network-check-source-869dcfcdcd-x76pk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T02:21:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 786.555µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 816.928µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 1.276394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 873.658µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 878.264µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:52:09Z"
    - latency: 922.024µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:51:09Z"
    - latency: 1.023114ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:50:09Z"
    - latency: 1.500541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:49:09Z"
    - latency: 1.036602ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:48:09Z"
    - latency: 934.312µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T02:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-215-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-215.ec2.internal
      uid: 836b9add-b511-4992-ae35-f5ea9a92b82a
    resourceVersion: "61732"
    uid: e2d55e18-9bd1-41a7-bd26-e2c2e1e54eaf
  spec:
    sourcePod: network-check-source-869dcfcdcd-x76pk
    targetEndpoint: abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T02:20:09Z"
      message: 'load-balancer-api-external: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.981912ms
      message: 'load-balancer-api-external: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 7.739526ms
      message: 'load-balancer-api-external: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 5.653578ms
      message: 'load-balancer-api-external: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 6.799169ms
      message: 'load-balancer-api-external: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 4.754679ms
      message: 'load-balancer-api-external: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 7.184482ms
      message: 'load-balancer-api-external: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 6.457183ms
      message: 'load-balancer-api-external: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 8.426868ms
      message: 'load-balancer-api-external: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 4.717791ms
      message: 'load-balancer-api-external: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:52:09Z"
    - latency: 6.564842ms
      message: 'load-balancer-api-external: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:52:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T02:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-215-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-215.ec2.internal
      uid: 836b9add-b511-4992-ae35-f5ea9a92b82a
    resourceVersion: "61733"
    uid: c9a15328-6e15-40ab-bbf7-7d6a7513b747
  spec:
    sourcePod: network-check-source-869dcfcdcd-x76pk
    targetEndpoint: abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T02:20:09Z"
      message: 'load-balancer-api-internal: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.984756ms
      message: 'load-balancer-api-internal: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 7.729809ms
      message: 'load-balancer-api-internal: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 5.634959ms
      message: 'load-balancer-api-internal: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 6.772696ms
      message: 'load-balancer-api-internal: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 4.525411ms
      message: 'load-balancer-api-internal: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 7.152047ms
      message: 'load-balancer-api-internal: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 5.485637ms
      message: 'load-balancer-api-internal: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 8.353186ms
      message: 'load-balancer-api-internal: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 5.48166ms
      message: 'load-balancer-api-internal: tcp connection to abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:52:09Z"
    - latency: 6.497752ms
      message: 'load-balancer-api-internal: resolved host name abe7fdcdcfc05415ab4e5dff9d2d2bb3-cbe9615925448bf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:52:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T02:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-215-to-network-check-target-ip-10-0-130-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-215.ec2.internal
      uid: 836b9add-b511-4992-ae35-f5ea9a92b82a
    resourceVersion: "61727"
    uid: 93bad00e-8760-4f42-adee-e4377cd7c080
  spec:
    sourcePod: network-check-source-869dcfcdcd-x76pk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T02:21:09Z"
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.927093ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 2.338269ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 2.140429ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 2.365383ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 2.368204ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:52:09Z"
    - latency: 2.267991ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:51:09Z"
    - latency: 2.26747ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:50:09Z"
    - latency: 2.200756ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:49:09Z"
    - latency: 2.28405ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:48:09Z"
    - latency: 2.334677ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T02:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-215-to-network-check-target-ip-10-0-131-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-215.ec2.internal
      uid: 836b9add-b511-4992-ae35-f5ea9a92b82a
    resourceVersion: "61728"
    uid: 12e8adb5-7649-494e-8e33-8a4c3ec811c4
  spec:
    sourcePod: network-check-source-869dcfcdcd-x76pk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T02:21:09Z"
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.260492ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 2.214215ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 2.334026ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 2.220776ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 2.226638ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:52:09Z"
    - latency: 2.690642ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:51:09Z"
    - latency: 2.212995ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:50:09Z"
    - latency: 2.572756ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:49:09Z"
    - latency: 2.208844ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:48:09Z"
    - latency: 2.237095ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T02:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-215-to-network-check-target-ip-10-0-139-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-215.ec2.internal
      uid: 836b9add-b511-4992-ae35-f5ea9a92b82a
    resourceVersion: "61726"
    uid: 01d2fa37-dae9-468a-8647-0c25bb816e9b
  spec:
    sourcePod: network-check-source-869dcfcdcd-x76pk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T02:21:09Z"
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 792.599µs
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 845.686µs
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 1.706136ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 800.726µs
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 1.587821ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:52:09Z"
    - latency: 700.679µs
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:51:09Z"
    - latency: 922.743µs
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:50:09Z"
    - latency: 703.109µs
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:49:09Z"
    - latency: 928.647µs
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:48:09Z"
    - latency: 1.246744ms
      message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:47:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T02:14:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-215-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-215.ec2.internal
      uid: 836b9add-b511-4992-ae35-f5ea9a92b82a
    resourceVersion: "61729"
    uid: 64fc4c8e-f2a5-434f-91bf-70e19e7c8a7c
  spec:
    sourcePod: network-check-source-869dcfcdcd-x76pk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T02:20:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 780.944µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 2.073474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:56:09Z"
    - latency: 773.586µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 1.732523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:55:09Z"
    - latency: 989.269µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 1.70888ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:54:09Z"
    - latency: 795.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 1.613596ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:53:09Z"
    - latency: 699.42µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T02:52:09Z"
    - latency: 1.563188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T02:52:09Z"
kind: List
metadata:
  resourceVersion: ""