text: To generate a hash for your environment, use the**base64**command, as shown in 
  Example 7-14. 
  
  Example 7-14 Creating base64 hash for password stored in secrets 
  
  <html>
          <head> <meta charset="UTF-8">
          <style>
          table, th, td {
              border: 1px solid black;
              font-size: 10px;
          }
          </style> </head>
          <body>
          <table frame="hsides" rules="groups" width="100%%">
              [html]<thead><tr><td>[ root @ dcocp01</td></tr></thead><tbody><tr><td>]# echo - n start1234 | base64</td></tr><tr><td>c3RhcnQxM ; jM0</td></tr></tbody>
          </table> </body> </html>
  
  This scenario uses MongoDB 3.6.3 image available at the redhat registry 
  (registry.access.redhat.com/rhscl/mongodb-36-rhel7). As shown in Example 7-15, our 
  scenario creates a yaml file that picks any architecture between POWER and x86, but a 
  different weight can be set to give preference to one architecture. This pod definition makes it 
  transparent to the cluster operator if the MongoDB is being deployed on-premise, in the cloud, 
  on POWER, or on x86. The image has a unique name, although a container for each 
  architecture exists and is pulled accordingly without any user input. 