Merge pull request #15866 from g-pan/H26012-HelmChgs

HPCC-26012 Add Annotations value to helm docs

Reviewed-By: Jake Smith <jake.smith@lexisnexis.com>
Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>

docs/EN_US/ContainerizedHPCC/ContainerizedMods/ConfigureValues.xml

@@ -158,6 +158,28 @@
       functional system, however you should define the component resources in
       a manner that corresponds best to your operational strategy.</para>
 
+      <sect3 id="YML_HPCCSystemsServices">
+        <title>The Systems services</title>
+
+        <para>Most of the HPCC Systems components have a service definition
+        entry, similar to the resources entry. All the components that have
+        service definitions follow this same pattern.</para>
+
+        <para>Any service related info needs to be under a service object, for
+        example:</para>
+
+        <para><programlisting>  service:
+    servicePort: 7200
+    visibility: local
+</programlisting></para>
+
+        <para>This applies to most all of the HPCC Systems components, ESP,
+        Dali, dafilesrv, and Sasha. Roxie's specification is slightly
+        different, in that it has its service defined under "roxieservice".
+        Each Roxie can then have multiple "roxieservice" definitions. (see
+        schema).</para>
+      </sect3>
+
       <sect3 id="DALI_ValueYAML">
         <title>Dali</title>
 
@@ -167,7 +189,7 @@
         assign all the pods to the same virtual machine and components
         fighting for memory will crush them. Therefore more memory assigned
         the better. If you define these wrong and a process uses more memory
-        than configured, Kubernetes will kill the pod. </para>
+        than configured, Kubernetes will kill the pod.</para>
       </sect3>
 
       <sect3 id="DAFLESRV_DFURVR_YMLSECT">
@@ -380,35 +402,35 @@
     <para>The delivered HPCC Systems Values file primarily consists of the
     following areas:</para>
 
-    <itemizedlist>
-      <listitem>
-        <para>global</para>
-      </listitem>
+    <para><informaltable>
+        <tgroup cols="3">
+          <tbody>
+            <row>
+              <entry>global</entry>
+
+              <entry>storage</entry>
 
-      <listitem>
-        <para>storage</para>
-      </listitem>
+              <entry>visibilities</entry>
+            </row>
 
-      <listitem>
-        <para>data planes</para>
-      </listitem>
+            <row>
+              <entry>data planes</entry>
 
-      <listitem>
-        <para>certificates</para>
-      </listitem>
+              <entry>certificates</entry>
 
-      <listitem>
-        <para>security</para>
-      </listitem>
+              <entry>security</entry>
+            </row>
 
-      <listitem>
-        <para>secrets</para>
-      </listitem>
+            <row>
+              <entry>secrets</entry>
 
-      <listitem>
-        <para>components</para>
-      </listitem>
-    </itemizedlist>
+              <entry>components</entry>
+
+              <entry></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </informaltable></para>
 
     <para>The subsequent sections will examine some of these more closely and
     why each of them is there.</para>
@@ -801,6 +823,13 @@
     </sect2>
 
     <sect2>
+      <title>Visibilities</title>
+
+      <para>The visibilities section can be used to set labels, annotations,
+      and service types for any service with the specified visibility.</para>
+    </sect2>
+
+    <sect2>
       <title>Replicas and Resources</title>
 
       <para>Other noteworthy values in the charts that have bearing on HPCC