apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:25:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-234-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-234.ec2.internal
      uid: a14a3fa0-9319-4594-9441-68cb94af44a6
    resourceVersion: "32586"
    uid: a2f623f3-bb0c-4669-a4f0-e31c155c9c9f
  spec:
    sourcePod: network-check-source-56499946bc-pcww5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:32:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.572812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 1.421048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 832.415µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 858.318µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 1.041334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:03:44Z"
    - latency: 1.015636ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:02:44Z"
    - latency: 851.78µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:01:44Z"
    - latency: 931.024µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:00:44Z"
    - latency: 1.001426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:59:44Z"
    - latency: 1.411728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:58:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:25:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-234-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-234.ec2.internal
      uid: a14a3fa0-9319-4594-9441-68cb94af44a6
    resourceVersion: "32588"
    uid: 4eff3509-0eb5-40a8-97a1-810b4f226c5b
  spec:
    sourcePod: network-check-source-56499946bc-pcww5
    targetEndpoint: ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:31:44Z"
      message: 'load-balancer-api-external: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.377289ms
      message: 'load-balancer-api-external: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 9.17327ms
      message: 'load-balancer-api-external: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 5.287309ms
      message: 'load-balancer-api-external: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 8.813288ms
      message: 'load-balancer-api-external: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 4.961024ms
      message: 'load-balancer-api-external: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 11.232013ms
      message: 'load-balancer-api-external: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 5.813522ms
      message: 'load-balancer-api-external: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 8.535128ms
      message: 'load-balancer-api-external: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 5.699602ms
      message: 'load-balancer-api-external: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:03:44Z"
    - latency: 9.029301ms
      message: 'load-balancer-api-external: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:03:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:25:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-234-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-234.ec2.internal
      uid: a14a3fa0-9319-4594-9441-68cb94af44a6
    resourceVersion: "32587"
    uid: d591fef4-7cd6-4e8b-8da6-bb5bbec2df70
  spec:
    sourcePod: network-check-source-56499946bc-pcww5
    targetEndpoint: ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:31:44Z"
      message: 'load-balancer-api-internal: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.094999ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 9.154854ms
      message: 'load-balancer-api-internal: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 5.319131ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 8.711892ms
      message: 'load-balancer-api-internal: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 4.975079ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 11.20049ms
      message: 'load-balancer-api-internal: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 5.83858ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 8.499246ms
      message: 'load-balancer-api-internal: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 5.759843ms
      message: 'load-balancer-api-internal: tcp connection to ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:03:44Z"
    - latency: 8.957217ms
      message: 'load-balancer-api-internal: resolved host name ab3fa8f12e784463b93e2c5299f94a6b-98865760890a5f73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:03:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:25:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-234-to-network-check-target-ip-10-0-130-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-234.ec2.internal
      uid: a14a3fa0-9319-4594-9441-68cb94af44a6
    resourceVersion: "32582"
    uid: 765f2d49-7344-49fc-a6ac-65720a2f298f
  spec:
    sourcePod: network-check-source-56499946bc-pcww5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:32:44Z"
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 848.885µs
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 902.392µs
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 1.424377ms
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 795.461µs
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 980.775µs
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:03:44Z"
    - latency: 1.471762ms
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:02:44Z"
    - latency: 1.811846ms
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:01:44Z"
    - latency: 807.125µs
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:00:44Z"
    - latency: 996.645µs
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:59:44Z"
    - latency: 1.634703ms
      message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:58:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:25:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-234-to-network-check-target-ip-10-0-139-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-234.ec2.internal
      uid: a14a3fa0-9319-4594-9441-68cb94af44a6
    resourceVersion: "32584"
    uid: bfa57b0c-4096-45ef-8ec5-3a17e4bfe505
  spec:
    sourcePod: network-check-source-56499946bc-pcww5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:32:44Z"
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.281782ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 2.456168ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 2.26971ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 2.256362ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 2.282702ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:03:44Z"
    - latency: 2.245631ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:02:44Z"
    - latency: 2.295893ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:01:44Z"
    - latency: 2.331109ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:00:44Z"
    - latency: 2.055055ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:59:44Z"
    - latency: 2.190823ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:58:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:25:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-234-to-network-check-target-ip-10-0-141-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-234.ec2.internal
      uid: a14a3fa0-9319-4594-9441-68cb94af44a6
    resourceVersion: "32583"
    uid: fca3a630-38f9-4a22-b88c-ba42a0db3bcf
  spec:
    sourcePod: network-check-source-56499946bc-pcww5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:32:44Z"
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.116912ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 2.411565ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 2.271295ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 1.94921ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 2.070408ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:03:44Z"
    - latency: 2.258191ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:02:44Z"
    - latency: 2.082764ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:01:44Z"
    - latency: 2.067467ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:00:44Z"
    - latency: 2.125085ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:59:44Z"
    - latency: 2.098407ms
      message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:58:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:25:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-234-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-234.ec2.internal
      uid: a14a3fa0-9319-4594-9441-68cb94af44a6
    resourceVersion: "32585"
    uid: 7d758254-ab40-45d5-89fd-8443b12a0dc9
  spec:
    sourcePod: network-check-source-56499946bc-pcww5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:31:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026216ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 2.185117ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:07:44Z"
    - latency: 1.28337ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 1.76608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:06:44Z"
    - latency: 1.040325ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 1.892117ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:05:44Z"
    - latency: 943.024µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 1.692728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:04:44Z"
    - latency: 1.184969ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:03:44Z"
    - latency: 2.076964ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:03:44Z"
kind: List
metadata:
  resourceVersion: ""