apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:42:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-112-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-112.ec2.internal
      uid: 165199e6-e090-4b89-86d1-8f006d415118
    resourceVersion: "21963"
    uid: 973152ab-b34c-414b-a4d2-5d7b2a3bcf63
  spec:
    sourcePod: network-check-source-56499946bc-rgpc9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:49:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.22086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:03:23Z"
    - latency: 784.468µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:23Z"
    - latency: 1.080818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:23Z"
    - latency: 903.23µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 938.502µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 1.248698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 1.366283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 1.331574ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:23Z"
    - latency: 1.105098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:23Z"
    - latency: 1.084193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:54:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:42:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-112-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-112.ec2.internal
      uid: 165199e6-e090-4b89-86d1-8f006d415118
    resourceVersion: "20535"
    uid: c622344d-0f94-4c2a-80a2-6f214591c588
  spec:
    sourcePod: network-check-source-56499946bc-rgpc9
    targetEndpoint: a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:48:23Z"
      message: 'load-balancer-api-external: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.901869ms
      message: 'load-balancer-api-external: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 9.367931ms
      message: 'load-balancer-api-external: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 4.994276ms
      message: 'load-balancer-api-external: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 7.009639ms
      message: 'load-balancer-api-external: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 6.253731ms
      message: 'load-balancer-api-external: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 6.854655ms
      message: 'load-balancer-api-external: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 5.952441ms
      message: 'load-balancer-api-external: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 7.302153ms
      message: 'load-balancer-api-external: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 6.187908ms
      message: 'load-balancer-api-external: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:23Z"
    - latency: 6.886534ms
      message: 'load-balancer-api-external: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:56:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:42:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-112-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-112.ec2.internal
      uid: 165199e6-e090-4b89-86d1-8f006d415118
    resourceVersion: "20536"
    uid: 615266a7-51b3-49fa-9236-837dcf140904
  spec:
    sourcePod: network-check-source-56499946bc-rgpc9
    targetEndpoint: a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:48:23Z"
      message: 'load-balancer-api-internal: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.883753ms
      message: 'load-balancer-api-internal: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 9.419412ms
      message: 'load-balancer-api-internal: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 5.026592ms
      message: 'load-balancer-api-internal: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 7.031919ms
      message: 'load-balancer-api-internal: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 6.200069ms
      message: 'load-balancer-api-internal: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 6.881282ms
      message: 'load-balancer-api-internal: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 24.834691ms
      message: 'load-balancer-api-internal: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 7.44688ms
      message: 'load-balancer-api-internal: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 5.556348ms
      message: 'load-balancer-api-internal: tcp connection to a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:23Z"
    - latency: 6.935097ms
      message: 'load-balancer-api-internal: resolved host name a77a4c2b2c1cd4451951766e4bf95252-3c0f9aa5fca53816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:56:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:42:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-112-to-network-check-target-ip-10-0-133-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-112.ec2.internal
      uid: 165199e6-e090-4b89-86d1-8f006d415118
    resourceVersion: "21962"
    uid: 43a231f4-1e75-4647-96d8-8584ff430d0a
  spec:
    sourcePod: network-check-source-56499946bc-rgpc9
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:49:23Z"
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.863945ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:03:23Z"
    - latency: 1.868943ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:23Z"
    - latency: 1.98273ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:23Z"
    - latency: 1.99285ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 1.868395ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 2.250432ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 1.938392ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 1.873198ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:23Z"
    - latency: 2.191877ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:23Z"
    - latency: 1.645165ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:54:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:42:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-112-to-network-check-target-ip-10-0-139-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-112.ec2.internal
      uid: 165199e6-e090-4b89-86d1-8f006d415118
    resourceVersion: "21960"
    uid: 083bbeee-1db9-4341-b2bc-19cf9d5762bd
  spec:
    sourcePod: network-check-source-56499946bc-rgpc9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:49:23Z"
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067512ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:03:23Z"
    - latency: 1.162964ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:23Z"
    - latency: 979.351µs
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:23Z"
    - latency: 1.466592ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 838.125µs
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 938.282µs
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 745.625µs
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 991.032µs
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:23Z"
    - latency: 838.506µs
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:23Z"
    - latency: 953.904µs
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:54:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:42:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-112-to-network-check-target-ip-10-0-142-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-112.ec2.internal
      uid: 165199e6-e090-4b89-86d1-8f006d415118
    resourceVersion: "21961"
    uid: 15002ba6-0d47-42d6-a60b-6427f69ab23c
  spec:
    sourcePod: network-check-source-56499946bc-rgpc9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:49:23Z"
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.142876ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:03:23Z"
    - latency: 2.031323ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:23Z"
    - latency: 2.379115ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:23Z"
    - latency: 2.100565ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 1.890395ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 2.189981ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 2.176976ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 2.088046ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:23Z"
    - latency: 2.147946ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:23Z"
    - latency: 2.053928ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:54:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:42:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-112-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-112.ec2.internal
      uid: 165199e6-e090-4b89-86d1-8f006d415118
    resourceVersion: "20534"
    uid: 11ea65f0-c158-4abb-ac44-d3dcb9a9c4b5
  spec:
    sourcePod: network-check-source-56499946bc-rgpc9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:48:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 979.46µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 1.834006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:00:23Z"
    - latency: 1.093835ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 1.972789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:59:23Z"
    - latency: 1.252265ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 1.834408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:58:23Z"
    - latency: 878.034µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 2.034738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:57:23Z"
    - latency: 1.224387ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:23Z"
    - latency: 2.051444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:56:23Z"
kind: List
metadata:
  resourceVersion: ""