Today we continue discussing the best practice from storage engineering:
674) There is no limit to the number of operators run during deploy. It is preferred to run them sequentially one after the other. The more granular the operators the better they are for maintenance.
675) The diagnosability of operators improves with each operator being small and transparent.
676) The upgrade operator can be rolling upgrades. Then the operator does not require scale up or down.
677) The operators can invoke methods defined in other operators as long as they are accessible.
678) Frequently storage applications are written with dependencies on other applications. Those applications may also support operators. Operators can be chained one way or the other.
679) Requirements on operator logic change whether the product is an analysis package or a storage product.
680) There is a lot in common between installer packages on any other desktop platform and the containerization deployment operators.
681) The setup of service accounts is part of the operator actions for deployment and it remains one of the core requirements for the deployment of the product.
682) The dependencies of the software deployment may include such things as identity provider. The identity provider facilitates the registrations of service accounts
683) Identity providers issue token for accounts and these can be interpreted for user and roles
684) Identity providers do not mandate the use of one protocol such as Oauth or JWT and it is easy to switch from one to the other with http requests.
685) The accounts can be made suitable for use with any Identity provider.

#codingexercise

// topN
    for (int k = 0; k < N; k++) {
      Double value;
      if (first[i] > second[j]) {
          value = first[i];
          i++;
      } else {
          value = second[j];
          j++;
      }
    }