apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:53:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b6153fb9-f9ef-4cb7-b532-ef8ff9a926a1
    resourceVersion: "29530"
    uid: b100bbee-01ae-491a-b686-ae2d582ff6eb
  spec:
    sourcePod: network-check-source-56d84b9f44-z6hcf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:00:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:46Z"
    - latency: 1.024555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:46Z"
    - latency: 1.355959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 1.225973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 1.224103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 1.028696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 1.476469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:01:46Z"
    - latency: 1.270222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:00:46Z"
    - latency: 1.088676ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:59:46Z"
    - latency: 1.126124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:58:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:53:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b6153fb9-f9ef-4cb7-b532-ef8ff9a926a1
    resourceVersion: "27993"
    uid: 8646c4e9-f645-44bd-9693-e0311f58774b
  spec:
    sourcePod: network-check-source-56d84b9f44-z6hcf
    targetEndpoint: ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:59:46Z"
      message: 'load-balancer-api-external: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.204758ms
      message: 'load-balancer-api-external: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 7.610254ms
      message: 'load-balancer-api-external: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 4.852068ms
      message: 'load-balancer-api-external: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 6.139273ms
      message: 'load-balancer-api-external: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 4.983874ms
      message: 'load-balancer-api-external: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 7.417441ms
      message: 'load-balancer-api-external: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 5.19944ms
      message: 'load-balancer-api-external: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 7.293525ms
      message: 'load-balancer-api-external: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 5.94831ms
      message: 'load-balancer-api-external: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:01:46Z"
    - latency: 8.205825ms
      message: 'load-balancer-api-external: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:01:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:53:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b6153fb9-f9ef-4cb7-b532-ef8ff9a926a1
    resourceVersion: "27992"
    uid: db34a8a2-b76f-4f8b-9893-2ab28efccb92
  spec:
    sourcePod: network-check-source-56d84b9f44-z6hcf
    targetEndpoint: ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:59:46Z"
      message: 'load-balancer-api-internal: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.038733ms
      message: 'load-balancer-api-internal: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 7.677004ms
      message: 'load-balancer-api-internal: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 3.923623ms
      message: 'load-balancer-api-internal: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 6.045174ms
      message: 'load-balancer-api-internal: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 4.994564ms
      message: 'load-balancer-api-internal: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 7.550698ms
      message: 'load-balancer-api-internal: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 5.22238ms
      message: 'load-balancer-api-internal: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 7.213281ms
      message: 'load-balancer-api-internal: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 5.260798ms
      message: 'load-balancer-api-internal: tcp connection to ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:01:46Z"
    - latency: 8.282342ms
      message: 'load-balancer-api-internal: resolved host name ae8cc36fb96964b2f85f25f211abd143-9f84547b419af59f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:01:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:53:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-network-check-target-ip-10-0-135-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b6153fb9-f9ef-4cb7-b532-ef8ff9a926a1
    resourceVersion: "29527"
    uid: 2e435980-32b2-49f7-9fa8-2726940cc6a7
  spec:
    sourcePod: network-check-source-56d84b9f44-z6hcf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:00:46Z"
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 950.368µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:46Z"
    - latency: 838.264µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:46Z"
    - latency: 1.1038ms
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 905.047µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 945.484µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 977.297µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 1.723926ms
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:01:46Z"
    - latency: 913.587µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:00:46Z"
    - latency: 1.006125ms
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:59:46Z"
    - latency: 857.279µs
      message: 'network-check-target-ip-10-0-135-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:58:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:53:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-network-check-target-ip-10-0-139-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b6153fb9-f9ef-4cb7-b532-ef8ff9a926a1
    resourceVersion: "29529"
    uid: 58f948b4-a609-41cf-b27a-58efee014677
  spec:
    sourcePod: network-check-source-56d84b9f44-z6hcf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:00:46Z"
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.183207ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:46Z"
    - latency: 2.342271ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:46Z"
    - latency: 2.330087ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 2.351994ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 2.470799ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 2.119687ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 2.211704ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:01:46Z"
    - latency: 2.165681ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:00:46Z"
    - latency: 1.985628ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:59:46Z"
    - latency: 2.176573ms
      message: 'network-check-target-ip-10-0-139-72: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:58:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:53:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-network-check-target-ip-10-0-141-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b6153fb9-f9ef-4cb7-b532-ef8ff9a926a1
    resourceVersion: "29528"
    uid: 3003a24d-3fa0-46b8-b8e8-6d690aa9ebdb
  spec:
    sourcePod: network-check-source-56d84b9f44-z6hcf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:00:46Z"
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.010206ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:07:46Z"
    - latency: 1.72691ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:06:46Z"
    - latency: 2.053378ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 2.085107ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 1.80697ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 1.95853ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 2.588827ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:01:46Z"
    - latency: 1.862253ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:00:46Z"
    - latency: 1.640541ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:59:46Z"
    - latency: 2.137633ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:58:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:53:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-102.ec2.internal
      uid: b6153fb9-f9ef-4cb7-b532-ef8ff9a926a1
    resourceVersion: "27991"
    uid: b3bd6644-5fff-401d-be7f-c5256d69a8df
  spec:
    sourcePod: network-check-source-56d84b9f44-z6hcf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:59:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.695µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 2.014147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:05:46Z"
    - latency: 785.117µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 1.592996ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:04:46Z"
    - latency: 1.169569ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 1.689076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:03:46Z"
    - latency: 1.006323ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 2.196864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:02:46Z"
    - latency: 851.582µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:01:46Z"
    - latency: 2.016649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:01:46Z"
kind: List
metadata:
  resourceVersion: ""