apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:05:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4043ce9b-935c-4e28-a5dc-b98cd79acae5
    resourceVersion: "56232"
    uid: 11571ef3-f8f7-466a-8a47-33e28f556fca
  spec:
    sourcePod: network-check-source-6f8b768455-rd965
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:12:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.374032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 1.041675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 1.301401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:31:47Z"
    - latency: 1.268255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:30:47Z"
    - latency: 7.545747ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:29:47Z"
    - latency: 854.541µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:28:47Z"
    - latency: 1.177936ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:47Z"
    - latency: 1.347658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:47Z"
    - latency: 1.314502ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:47Z"
    - latency: 1.369977ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:24:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:05:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4043ce9b-935c-4e28-a5dc-b98cd79acae5
    resourceVersion: "57434"
    uid: 01eef194-0036-4933-9123-1b70af4a7c3c
  spec:
    sourcePod: network-check-source-6f8b768455-rd965
    targetEndpoint: a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:11:47Z"
      message: 'load-balancer-api-external: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.135718ms
      message: 'load-balancer-api-external: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:47Z"
    - latency: 7.68753ms
      message: 'load-balancer-api-external: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:35:47Z"
    - latency: 7.738629ms
      message: 'load-balancer-api-external: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:47Z"
    - latency: 8.788448ms
      message: 'load-balancer-api-external: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:34:47Z"
    - latency: 4.808705ms
      message: 'load-balancer-api-external: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 7.416399ms
      message: 'load-balancer-api-external: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 4.969218ms
      message: 'load-balancer-api-external: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 7.079479ms
      message: 'load-balancer-api-external: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 8.437276ms
      message: 'load-balancer-api-external: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:31:47Z"
    - latency: 6.799021ms
      message: 'load-balancer-api-external: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:31:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:05:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4043ce9b-935c-4e28-a5dc-b98cd79acae5
    resourceVersion: "57435"
    uid: 963e5f38-e8ab-4e21-aa4a-044ae51bd9ad
  spec:
    sourcePod: network-check-source-6f8b768455-rd965
    targetEndpoint: a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:11:47Z"
      message: 'load-balancer-api-internal: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.711321ms
      message: 'load-balancer-api-internal: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:47Z"
    - latency: 7.630565ms
      message: 'load-balancer-api-internal: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:35:47Z"
    - latency: 7.727331ms
      message: 'load-balancer-api-internal: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:47Z"
    - latency: 8.744728ms
      message: 'load-balancer-api-internal: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:34:47Z"
    - latency: 4.777576ms
      message: 'load-balancer-api-internal: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 7.500225ms
      message: 'load-balancer-api-internal: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 4.954116ms
      message: 'load-balancer-api-internal: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 6.962854ms
      message: 'load-balancer-api-internal: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 4.17189ms
      message: 'load-balancer-api-internal: tcp connection to a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:31:47Z"
    - latency: 6.899908ms
      message: 'load-balancer-api-internal: resolved host name a6166511cd9264054a0e0222758160b6-fe0a73c1a588f6e1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:31:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:05:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-network-check-target-ip-10-0-130-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4043ce9b-935c-4e28-a5dc-b98cd79acae5
    resourceVersion: "56231"
    uid: a84ff501-d6c1-4889-88b0-31487a45d933
  spec:
    sourcePod: network-check-source-6f8b768455-rd965
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:12:47Z"
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.263762ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 2.393853ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 2.223153ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:31:47Z"
    - latency: 2.266013ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:30:47Z"
    - latency: 2.992081ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:29:47Z"
    - latency: 1.848086ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:28:47Z"
    - latency: 2.020899ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:47Z"
    - latency: 2.344142ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:47Z"
    - latency: 2.281383ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:47Z"
    - latency: 2.286727ms
      message: 'network-check-target-ip-10-0-130-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:24:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:05:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-network-check-target-ip-10-0-137-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4043ce9b-935c-4e28-a5dc-b98cd79acae5
    resourceVersion: "56230"
    uid: 22937961-3ec3-40bd-beae-9df39f29ef5c
  spec:
    sourcePod: network-check-source-6f8b768455-rd965
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:12:47Z"
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.283915ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 1.158421ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 1.041874ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:31:47Z"
    - latency: 984.621µs
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:30:47Z"
    - latency: 8.655925ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:29:47Z"
    - latency: 1.005588ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:28:47Z"
    - latency: 900.34µs
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:47Z"
    - latency: 1.032374ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:47Z"
    - latency: 912.22µs
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:47Z"
    - latency: 1.037028ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:24:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:05:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-network-check-target-ip-10-0-139-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4043ce9b-935c-4e28-a5dc-b98cd79acae5
    resourceVersion: "56229"
    uid: 21ba89d0-622f-4c1a-8d25-0abaf7697076
  spec:
    sourcePod: network-check-source-6f8b768455-rd965
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:12:47Z"
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.231208ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 2.3959ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 2.683975ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:31:47Z"
    - latency: 2.164195ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:30:47Z"
    - latency: 7.232949ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:29:47Z"
    - latency: 2.343695ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:28:47Z"
    - latency: 2.428921ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:27:47Z"
    - latency: 2.270197ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:26:47Z"
    - latency: 2.433015ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:25:47Z"
    - latency: 2.40052ms
      message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:24:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:05:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-9.ec2.internal
      uid: 4043ce9b-935c-4e28-a5dc-b98cd79acae5
    resourceVersion: "57433"
    uid: bab9316e-eec4-461c-955d-b953d7da4e62
  spec:
    sourcePod: network-check-source-6f8b768455-rd965
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:11:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.513µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:35:47Z"
    - latency: 1.782537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:35:47Z"
    - latency: 874.674µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:34:47Z"
    - latency: 2.527629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:34:47Z"
    - latency: 1.043983ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 2.309681ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:33:47Z"
    - latency: 1.382159ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 1.790191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:32:47Z"
    - latency: 1.208974ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:31:47Z"
    - latency: 1.761286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:31:47Z"
kind: List
metadata:
  resourceVersion: ""