You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-18Lines changed: 20 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,45 +12,47 @@ or how to use it, head over to [Ansible Edge GitOps](http://validatedpatterns.io
12
12
This Validated Pattern lays the OTEL based infrastructure foundation to setup observability in federated and/or distributed environments.
13
13
The infrastructure components are a central OpenShift Hub server with 4 edge nodes which are running as preconfigured virtual machines on OpenShift-Virtualization (OCP-V).
14
14
15
-
The technology components used here are
15
+
The technology components used here are
16
+
16
17
- OpenShift,
17
18
- ArgoCD as OpenShift GitOps,
18
19
- Hashicorp Vault,
19
-
- OpenShift Virtualization,
20
+
- OpenShift Virtualization,
20
21
- Ansible Automation Platform,
21
22
- OpenShift Data Foundations (ODF),
22
23
- Red Hat Device Edge (running at the edge),
23
24
- OpenTelemetry.
24
25
25
-
The installation at the OpenShift hub cluster happens via Operators (subscriptions), the pattern itself (see values-hub.yaml) or via an Ansible playbook (OTEL at the edge) while the installation at the edge happens via an Ansible playbook installing an RPM: https://github.com/validatedpatterns-demos/rhvp.federated_edge_observability/blob/main/roles/otel_collector/tasks/main.yml
26
+
The installation at the OpenShift hub cluster happens via Operators
27
+
(subscriptions), the pattern itself (see values-hub.yaml) or via an Ansible
28
+
playbook (OTEL at the edge) while the installation at the edge happens via an
29
+
Ansible playbook installing an [RPM](https://github.com/validatedpatterns-demos/rhvp.federated_edge_observability/blob/main/roles/otel_collector/tasks/main.yml)
26
30
ArgoCD is managing the applications as defined in the values-hub.yaml file.
27
31
28
32
The user/password/key config happens in your user home (!) directory via the values-secret.yaml, so make sure you copy and then edit your values-secret.yaml.template to ~/values-secret.yaml.
29
33
30
-
There are several different git repositories in play which serve different purposes. The multiple git repos serve the purpose of easy customization and adoption into different environments.
34
+
There are several different Git repositories in play which serve different purposes. The multiple Git repositories serve the purpose of easy customization and adoption into different environments.
31
35
32
36
### GitRepos setup
33
37
34
-
#### Federated Edge Observability
35
-
This pattern repo is the starting point and main git repo:
0 commit comments