Fixed typo in LetsEncrypt example

Removed duplicate Datanet entry from main index.rst

Reworked Use Kubernetes CPU Manager Static Policy prerequisite block.

Restored fault/index version of FM toctree in top-level index.

Added merged doc entries to top level index.rst.

Incorporated review comments. Also some generic formatting clean-up such as
converting abbreviations to rST-style :abbr: markup.

Moved url with embedded substitution out of code-block.

Addressed patch 2 review comments. Some addtional rST tidying. See comment replies
for open questions/issues.

This patch fixes an issue with 'stx' in filenames that may differ downstream using-an-image-from-the-local-docker-registry-in-a-container-spec
new substitution and changing code-blocks to parsed-literals as required.

Initial submission for review. Note that a couple of references to WR persist
in examples. These will be marked up with comments in the review.

Signed-off-by: Stone <ronald.stone@windriver.com>
Change-Id: I1efef569842caff5def9dc00395b594d91d7a5d0
Signed-off-by: Stone <ronald.stone@windriver.com>

2020-12-02 10:34:53 -05:00

1.2 KiB

Raw Blame History

Remote CLI Access

You can access the system CLIs (Command Line Interfaces) from a remote workstation using one of the two methods.

The first method involves using the remote CLI (Command Line Interface) tarball from to install a set of container-backed remote CLIs for accessing a remote . This provides access to the kubernetes-related CLIs (kubectl, helm). This approach is simple to install, portable across Linux, OSX and Windows, and provides access to all CLIs. However, commands such as those that reference local files or require a shell are awkward to run in this environment.
The second method involves installing the kubectl and helm clients directly on the remote host. This method only provides the kubernetes-related CLIs and requires OS-specific installation instructions.

1.2 KiB Raw Blame History

Remote CLI Access

1.2 KiB

Raw Blame History