text: <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>Component</td><td>Description</td></tr></thead><tbody><tr><td>api server</td><td>The Kubernetes API server validates and configures the data for Pods, services, and replication controllers. It also assigns Pods to nodes and synchronizes Pod information with service configuration.</td></tr><tr><td>etcd</td><td>The etcd component stores the persistent master state while other components watch etcd for changes to bring themselves into the wanted state. Also, etcol optionally can be oonfligured for high availability, typically deployed with Zn</td></tr><tr><td>Controller Manager Server</td><td>The controller manager server watches etcd for changes to replication controller objects and then uses the API to enforce the wanted state. Several such processes create a cluster with one active leader at a time.</td></tr><tr><td>HAProxy</td><td>Optional, used when configuring highly available masters with the native method to balance load between API master endoxints. The cluster installation process can configure HAProxy for you by using the native method. Alternatively, b</td></tr></tbody>
          </table> </body> </html>