apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T00:19:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 6a2f6c4b-c6ed-4d4c-8ae5-6ceb6bfe988c
    resourceVersion: "68818"
    uid: f0677a2e-73c3-41cf-9e40-7e1a0a3d7a9b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5jr28
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T00:26:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.25853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:08:45Z"
    - latency: 935.511µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 974.614µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 872.696µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 996.361µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 1.114789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:03:45Z"
    - latency: 1.039529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:02:45Z"
    - latency: 1.457468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:01:45Z"
    - latency: 1.120279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:00:45Z"
    - latency: 923.396µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T00:59:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T00:19:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 6a2f6c4b-c6ed-4d4c-8ae5-6ceb6bfe988c
    resourceVersion: "67800"
    uid: d0a3d819-8dac-41c3-9a7f-6c8e19fbd936
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5jr28
    targetEndpoint: a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T00:25:45Z"
      message: 'load-balancer-api-external: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.063022ms
      message: 'load-balancer-api-external: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 7.134771ms
      message: 'load-balancer-api-external: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 4.249196ms
      message: 'load-balancer-api-external: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 6.484086ms
      message: 'load-balancer-api-external: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 3.688112ms
      message: 'load-balancer-api-external: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 7.076897ms
      message: 'load-balancer-api-external: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 3.189681ms
      message: 'load-balancer-api-external: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 6.088276ms
      message: 'load-balancer-api-external: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 5.649781ms
      message: 'load-balancer-api-external: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:03:45Z"
    - latency: 6.699985ms
      message: 'load-balancer-api-external: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:03:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T00:19:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 6a2f6c4b-c6ed-4d4c-8ae5-6ceb6bfe988c
    resourceVersion: "67801"
    uid: d05ebaad-0a11-4787-9c73-f0f93bf3d1ce
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5jr28
    targetEndpoint: a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T00:25:45Z"
      message: 'load-balancer-api-internal: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.053934ms
      message: 'load-balancer-api-internal: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 7.171918ms
      message: 'load-balancer-api-internal: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 4.188479ms
      message: 'load-balancer-api-internal: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 6.508176ms
      message: 'load-balancer-api-internal: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 3.670764ms
      message: 'load-balancer-api-internal: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 7.144021ms
      message: 'load-balancer-api-internal: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 3.046761ms
      message: 'load-balancer-api-internal: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 6.139622ms
      message: 'load-balancer-api-internal: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 5.696677ms
      message: 'load-balancer-api-internal: tcp connection to a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:03:45Z"
    - latency: 6.733568ms
      message: 'load-balancer-api-internal: resolved host name a2bbfda654edf4b138b74f40b73fbd21-9fe202b977ca36eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:03:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T00:19:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-network-check-target-ip-10-0-135-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 6a2f6c4b-c6ed-4d4c-8ae5-6ceb6bfe988c
    resourceVersion: "68816"
    uid: dae2e2f5-05b4-43e2-b104-1fb449bb70d0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5jr28
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T00:26:45Z"
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.375894ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:08:45Z"
    - latency: 2.110901ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 2.253637ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 1.887937ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 2.538584ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 2.301314ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:03:45Z"
    - latency: 2.319026ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:02:45Z"
    - latency: 2.334925ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:01:45Z"
    - latency: 2.470298ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:00:45Z"
    - latency: 2.154012ms
      message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T00:59:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T00:19:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-network-check-target-ip-10-0-139-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 6a2f6c4b-c6ed-4d4c-8ae5-6ceb6bfe988c
    resourceVersion: "68817"
    uid: e95876a5-f0aa-4934-8f72-78d2f2a4ab25
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5jr28
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T00:26:45Z"
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.37951ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:08:45Z"
    - latency: 2.299125ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 2.237916ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 2.429934ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 2.630647ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 2.696701ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:03:45Z"
    - latency: 2.287902ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:02:45Z"
    - latency: 2.383997ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:01:45Z"
    - latency: 2.297823ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:00:45Z"
    - latency: 2.533585ms
      message: 'network-check-target-ip-10-0-139-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T00:59:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T00:19:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-network-check-target-ip-10-0-139-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 6a2f6c4b-c6ed-4d4c-8ae5-6ceb6bfe988c
    resourceVersion: "68815"
    uid: 4427c17f-46c0-4e08-af16-9c0566edc7cd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5jr28
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T00:26:45Z"
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.181223ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:08:45Z"
    - latency: 1.277296ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 1.228026ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 1.222221ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 1.245734ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 968.223µs
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:03:45Z"
    - latency: 952.409µs
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:02:45Z"
    - latency: 1.624641ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:01:45Z"
    - latency: 1.280959ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:00:45Z"
    - latency: 1.668861ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T00:59:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T00:19:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 6a2f6c4b-c6ed-4d4c-8ae5-6ceb6bfe988c
    resourceVersion: "67799"
    uid: a6c2b668-0d26-449a-8429-7917ea40a03f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5jr28
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T00:25:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.369µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 1.816943ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:07:45Z"
    - latency: 826.593µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 1.517234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:06:45Z"
    - latency: 870.272µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 1.948385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:05:45Z"
    - latency: 1.108978ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 1.662084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:04:45Z"
    - latency: 962.809µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T01:03:45Z"
    - latency: 1.797643ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T01:03:45Z"
kind: List
metadata:
  resourceVersion: ""