Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
...
- We are setting a precedent for installation of optional third-party components
- To simplify the installation process, keep each operation atomic, and to allow components to be installed in any order, all component installations will be decoupled from the base anax installation.
- The process should also function if a person is "bringing their own already-installed component" and we are just integrating anax with a pre-existing KubeArmor installation.
- The default case will be based on native applications, not containerized versions, although both options or a mix thereof should work.
- The integration should also be easily reversible.
anax agent installation
Today, installing the agent on the target device involves running the "agent-install.sh" script as documented at Automated agent installation and registration. At this point, we are assuming that no signal needs to be sent to this installation script and process to notify it that KubeArmor should also be installed. If that were the case, we should consider a flag in the form of an installation argument or an environment variable. This will allow us to decouple the process of installing KubeArmor as an optional security component.
...