apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-95.ec2.internal
      uid: 3675dfd4-7af1-42fd-ba36-b2c80cc8bff6
    resourceVersion: "50139"
    uid: f6535684-62b5-4c65-acc5-be1ce27baed7
  spec:
    sourcePod: network-check-source-6947749cfc-mpr55
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:45:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 1.220172ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 1.129756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 841.522µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:10:49Z"
    - latency: 1.113839ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:09:49Z"
    - latency: 849.784µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:08:49Z"
    - latency: 1.102316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:07:49Z"
    - latency: 1.21691ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:06:49Z"
    - latency: 1.162268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:05:49Z"
    - latency: 1.259411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:04:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-95.ec2.internal
      uid: 3675dfd4-7af1-42fd-ba36-b2c80cc8bff6
    resourceVersion: "50772"
    uid: 5a9323ff-5b87-46cf-92c9-5bfc2828596d
  spec:
    sourcePod: network-check-source-6947749cfc-mpr55
    targetEndpoint: adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:44:49Z"
      message: 'load-balancer-api-external: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.502158ms
      message: 'load-balancer-api-external: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:14:49Z"
    - latency: 8.915488ms
      message: 'load-balancer-api-external: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:14:49Z"
    - latency: 5.200901ms
      message: 'load-balancer-api-external: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 7.380319ms
      message: 'load-balancer-api-external: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 4.466941ms
      message: 'load-balancer-api-external: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 8.576771ms
      message: 'load-balancer-api-external: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 5.237608ms
      message: 'load-balancer-api-external: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 8.751531ms
      message: 'load-balancer-api-external: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 3.558049ms
      message: 'load-balancer-api-external: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:10:49Z"
    - latency: 6.783237ms
      message: 'load-balancer-api-external: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:10:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-95.ec2.internal
      uid: 3675dfd4-7af1-42fd-ba36-b2c80cc8bff6
    resourceVersion: "50773"
    uid: c2f84e08-329e-4928-b970-b34e193e94bf
  spec:
    sourcePod: network-check-source-6947749cfc-mpr55
    targetEndpoint: adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:44:49Z"
      message: 'load-balancer-api-internal: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.459813ms
      message: 'load-balancer-api-internal: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:14:49Z"
    - latency: 9.008387ms
      message: 'load-balancer-api-internal: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:14:49Z"
    - latency: 5.168135ms
      message: 'load-balancer-api-internal: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 7.448152ms
      message: 'load-balancer-api-internal: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 3.538199ms
      message: 'load-balancer-api-internal: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 8.635541ms
      message: 'load-balancer-api-internal: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 5.208786ms
      message: 'load-balancer-api-internal: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 8.697189ms
      message: 'load-balancer-api-internal: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 3.547359ms
      message: 'load-balancer-api-internal: tcp connection to adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:10:49Z"
    - latency: 6.84985ms
      message: 'load-balancer-api-internal: resolved host name adde93ebf66dd472e928fda19e1adf56-4414051cd2e777e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:10:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-95-to-network-check-target-ip-10-0-133-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-95.ec2.internal
      uid: 3675dfd4-7af1-42fd-ba36-b2c80cc8bff6
    resourceVersion: "50138"
    uid: ae6b8d68-b470-4495-bd83-954f9d7a3832
  spec:
    sourcePod: network-check-source-6947749cfc-mpr55
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:45:49Z"
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.331275ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 2.400889ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 2.45462ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 2.279161ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:10:49Z"
    - latency: 2.429081ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:09:49Z"
    - latency: 2.012758ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:08:49Z"
    - latency: 2.36005ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:07:49Z"
    - latency: 2.356916ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:06:49Z"
    - latency: 2.211833ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:05:49Z"
    - latency: 2.244738ms
      message: 'network-check-target-ip-10-0-133-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:04:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-95-to-network-check-target-ip-10-0-133-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-95.ec2.internal
      uid: 3675dfd4-7af1-42fd-ba36-b2c80cc8bff6
    resourceVersion: "50137"
    uid: 1e3ced9f-4431-4bad-9888-314629ab4d1d
  spec:
    sourcePod: network-check-source-6947749cfc-mpr55
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:45:49Z"
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 976.796µs
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 957.399µs
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 1.266585ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 1.171912ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:10:49Z"
    - latency: 1.001934ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:09:49Z"
    - latency: 1.34156ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:08:49Z"
    - latency: 1.10699ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:07:49Z"
    - latency: 1.528597ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:06:49Z"
    - latency: 1.221557ms
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:05:49Z"
    - latency: 818.106µs
      message: 'network-check-target-ip-10-0-133-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:04:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-95-to-network-check-target-ip-10-0-135-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-95.ec2.internal
      uid: 3675dfd4-7af1-42fd-ba36-b2c80cc8bff6
    resourceVersion: "50136"
    uid: 06fa7a4c-1561-483e-8382-6ef5b47b87b2
  spec:
    sourcePod: network-check-source-6947749cfc-mpr55
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:45:49Z"
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.864789ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 2.206938ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 1.932323ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 2.051628ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:10:49Z"
    - latency: 1.919453ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:09:49Z"
    - latency: 1.653356ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:08:49Z"
    - latency: 1.822876ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:07:49Z"
    - latency: 2.346277ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:06:49Z"
    - latency: 2.058226ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:05:49Z"
    - latency: 1.867279ms
      message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:04:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-95.ec2.internal
      uid: 3675dfd4-7af1-42fd-ba36-b2c80cc8bff6
    resourceVersion: "50771"
    uid: fe695133-06f9-4a5c-b02e-ff55370927d7
  spec:
    sourcePod: network-check-source-6947749cfc-mpr55
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:44:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 814.563µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:14:49Z"
    - latency: 2.163761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:14:49Z"
    - latency: 1.109692ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 1.635204ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:13:49Z"
    - latency: 892.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 1.809158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:12:49Z"
    - latency: 833.988µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 1.76969ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:11:49Z"
    - latency: 900.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T22:10:49Z"
    - latency: 1.780832ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T22:10:49Z"
kind: List
metadata:
  resourceVersion: ""