-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
removed yaml syntax highlighting which doesn't look good either
switched a couple of commands to a root shell (# not $)
- Loading branch information
Showing
1 changed file
with
5 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1087,9 +1087,9 @@ You can find instructions to install KernelCare agent on http://your-eportal-dom | |
To install agent through ePortal you can use special endpoint `http://your-eportal-domain/install-kernelcare`: | ||
|
||
```text | ||
$ export [email protected] | ||
$ curl -s http://eportal.mycompany.com/install-kernelcare | bash | ||
$ kcarectl --register my-key | ||
# export [email protected] | ||
# curl -s http://eportal.mycompany.com/install-kernelcare | bash | ||
# kcarectl --register my-key | ||
``` | ||
|
||
Exporting `KCARE_MAILTO` is an optional step, it helps to configure corresponding entry in `/etc/cron.d/kcare-cron` to receive all notifications related to failed KernelCare updates. | ||
|
@@ -1132,7 +1132,7 @@ To start the automated deployment, you need to specify the following information | |
|
||
Ansible playbook for deployment phase may look like: | ||
|
||
```yaml | ||
```text | ||
- hosts: kernelcare | ||
vars: | ||
eportal_srv: http://192.168.250.19 | ||
|
@@ -1153,7 +1153,7 @@ Ansible playbook for deployment phase may look like: | |
|
||
Ansible playbook file example for KernelCare agent removal: | ||
|
||
```yaml | ||
```text | ||
- hosts: kernelcare | ||
tasks: | ||
- name: unregister KernelCare agents | ||
|