Rachael-Graham: staging tags

cs_access_reference.md

@@ -125,9 +125,9 @@ The following table shows the permissions granted by each {{site.data.keyword.cl
 | Delete all logging filter configurations for the Kubernetes cluster. | - | [`DELETE /v1/logging/{idOrName}/filterconfigs`](https://containers.cloud.ibm.com/global/swagger-global-api/#/filter/DeleteFilterConfigs) |
 | Update a log filtering configuration. | [`ibmcloud ks logging filter update`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_log_filter_update) | [`PUT /v1/logging/{idOrName}/filterconfigs/{id}`](https://containers.cloud.ibm.com/global/swagger-global-api/#/filter/UpdateFilterConfig) |
 | Add one NLB IP address to an existing NLB subdomain. | [`ibmcloud ks nlb-dns add`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_nlb-dns-add) | [`PUT /clusters/{idOrName}/add`](https://containers.cloud.ibm.com/global/swagger-global-api/#/nlb-dns/UpdateDNSWithIP) |
-| Create a DNS subdomain to register an NLB IP address. | [`ibmcloud ks nlb-dns create classic`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_nlb-dns-create) | [`POST /clusters/{idOrName}/register`](https://containers.cloud.ibm.com/global/swagger-global-api/#/nlb-dns/RegisterDNSWithIP) |
+| Create a DNS subdomain to register an NLB IP address. | [`ibmcloud ks nlb-dns create`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_nlb-dns-create) | [`POST /clusters/{idOrName}/register`](https://containers.cloud.ibm.com/global/swagger-global-api/#/nlb-dns/RegisterDNSWithIP) |
 | List the NLB subdomains and IP addresses that are registered in a cluster. | [`ibmcloud ks nlb-dns ls`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_nlb-dns-ls) | [`GET /clusters/{idOrName}/list`](https://containers.cloud.ibm.com/global/swagger-global-api/#/nlb-dns/ListNLBIPsForSubdomain) |
-| Remove an NLB IP address from a subdomain. | [`ibmcloud ks nlb-dns rm classic`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_nlb-dns-rm) | [`DELETE /clusters/{idOrName}/host/{nlbHost}/ip/{nlbIP}/remove`](https://containers.cloud.ibm.com/global/swagger-global-api/#/nlb-dns/UnregisterDNSWithIP) |
+| Remove an NLB IP address from a subdomain. | [`ibmcloud ks nlb-dns rm`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_nlb-dns-rm) | [`DELETE /clusters/{idOrName}/host/{nlbHost}/ip/{nlbIP}/remove`](https://containers.cloud.ibm.com/global/swagger-global-api/#/nlb-dns/UnregisterDNSWithIP) |
 | Configure and optionally enable a health check monitor for an existing NLB subdomain in a cluster. | [`ibmcloud ks nlb-dns monitor configure`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_nlb-dns-monitor-configure) | [`POST /health/clusters/{idOrName}/config`](https://containers.cloud.ibm.com/global/swagger-global-api/#/nlb-health-monitor/AddNlbDNSHealthMonitor) |
 | View the settings for an existing health check monitor. | [`ibmcloud ks nlb-dns monitor get`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_nlb-dns-monitor-get) | [`GET /health/clusters/{idOrName}/host/{nlbHost}/config`](https://containers.cloud.ibm.com/global/swagger-global-api/#/nlb-health-monitor/GetNlbDNSHealthMonitor) |
 | Disable an existing health check monitor for a subdomain in a cluster. | [`ibmcloud ks nlb-dns monitor disable`](/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_nlb-dns-monitor-disable) | [`PUT /clusters/{idOrName}/health`](https://containers.cloud.ibm.com/global/swagger-global-api/#/nlb-health-monitor/UpdateNlbDNSHealthMonitor) |

cs_loadbalancer_dns.md

@@ -309,7 +309,7 @@ ibmcloud ks nlb-dns add --cluster <cluster_name_or_id> --ip <NLB_IP> --ip <NLB2_
 
 You can also remove IP addresses of NLBs that you no longer want to be registered with a subdomain. Note that you must run the following command for each IP address that you want to remove. If you remove all IPs from a subdomain, the subdomain still exists but no IPs are associated with it.
 ```
-ibmcloud ks nlb-dns rm classic --cluster <cluster_name_or_id> --ip <ip1,ip2> --nlb-host <host_name>
+ibmcloud ks nlb-dns rm --cluster <cluster_name_or_id> --ip <ip> --nlb-host <host_name>
 ```
 {: pre}
 

kubernetes-service-cli.md

@@ -5602,8 +5602,9 @@ ibmcloud ks script update [--in-place] FILE [FILE ...]
 <dt><code><em>FILE [FILE ...]</em></code></dt>
 <dd>The file that contains the scripts that you want to update.</dd>
 </dl>
+</br>
 
-To use this command to prepare your automation scripts for the release of version 1.0 of the kubernetes-service:
+To use this command to prepare your automation scripts for the release of version 1.0 of the {{site.data.keyword.containerlong_notm}} plug-in:
 1. Run the command on a test script without the `--in-place` flag.
   ```
   ibmcloud ks script update ./mytestscript.sh
@@ -5616,13 +5617,13 @@ To use this command to prepare your automation scripts for the release of versio
     +++ b/script-test-2
     @@ -1,5 +1,5 @@
     -ibmcloud ks logging-config-get --cluster mycluster
-    -ibmcloud ks logging-config-update --cluster mycluster --id fakeee --logsource application --type ibm --app-containers app1,app2,app3 --app-paths /var/log/path/
-    -ibmcloud ks logging-config-update --cluster mycluster --id fakeee --logsource application --type ibm --app-paths=/var/log/path/,/var/log/other/path/
+    -ibmcloud ks logging-config-update --cluster mycluster --id myconfig --logsource application --type ibm --app-containers app1,app2,app3 --app-paths /var/log/path/
+    -ibmcloud ks logging-config-update --cluster mycluster --id myconfig --logsource application --type ibm --app-paths=/var/log/path/,/var/log/other/path/
     -ibmcloud ks clusters -s --locations dal09,dal12 --json
     -ibmcloud ks subnets --locations sao01
     +ibmcloud ks logging config get --cluster mycluster
-    +ibmcloud ks logging config update --cluster mycluster --id fakeee --logsource application --type ibm -C app1 -C app2 -C app3 -p /var/log/path/
-    +ibmcloud ks logging config update --cluster mycluster --id fakeee --logsource application --type ibm -p /var/log/path/ -p /var/log/other/path/
+    +ibmcloud ks logging config update --cluster mycluster --id myconfig --logsource application --type ibm -C app1 -C app2 -C app3 -p /var/log/path/
+    +ibmcloud ks logging config update --cluster mycluster --id myconfig --logsource application --type ibm -p /var/log/path/ -p /var/log/other/path/
     +ibmcloud ks clusters -s -l dal09 -l dal12 --json
     +ibmcloud ks subnets -l sao01
     ```