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>protocol : TCP</td></tr></thead><tbody><tr><td>targetPort : 8080</td></tr><tr><td>selector :</td></tr><tr><td>name : httpd - test03</td></tr><tr><td>sessionAf finity : None</td></tr><tr><td>type : NodePort</td></tr><tr><td>status :</td></tr><tr><td>1oadBa1ancer : {||</td></tr></tbody>
          </table> </body> </html>
  
  NodePorts are in the 30000-32767 range by default, which is unlikely to match a service’s 
  intended port. 
  
  For service and application access, the administrator must ensure that the external IPs are 
  routed to the nodes and local firewall rules on all nodes allow access to the open port. The 
  DNS wildcard feature can be used to configure resolution for a subset of names to an IP 
  address in the cluster. 