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
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,19 @@ OpenShift Operator for automatic detection and labeling of Red Hat application p
3
3
4
4
## Description
5
5
6
-
This is currently in a Proof of Concept state. The only pods that will be identified and labelled are EAP at the moment, there's a map in `identifier.go` that can be expanded upon to include other images.
6
+
This is currently in a Proof of Concept state. The operator identifies and labels JBoss EAP pods from multiple deployment methods:
7
+
8
+
-**Direct deployments**: Pods using Red Hat EAP images (e.g., `registry.redhat.io/jboss-eap-7/...`)
9
+
-**S2I builds**: Source-to-Image built applications with EAP base images
10
+
-**EAP Operator-managed pods**: Pods deployed via the EAP Operator (identified by `app.kubernetes.io/managed-by: eap-operator` label)
11
+
12
+
The operator adds the following labels to identified pods:
13
+
-`rht.comp`: Red Hat component/product name ("EAP")
14
+
-`rht.pod_image`: The pod's container image name
15
+
-`rht.pod_image_ver`: Version extracted from the pod's container image tag
16
+
-`rht.comp_discovered`: Unix timestamp of when the pod was first discovered
17
+
18
+
The product detection map in `identifier.go` can be expanded to include other Red Hat middleware products.
7
19
8
20
## Getting Started
9
21
@@ -18,6 +30,8 @@ Your operator will need to be run with the following permissions:
18
30
19
31
Get, List, Watch, Patch, Update on pods.
20
32
33
+
Get, List, Watch on images.
34
+
21
35
### Running on the cluster
22
36
23
37
You’ll need an OpenShift cluster to run against. You can use CRC to get a local cluster for testing, or run against a remote cluster. Note: Your controller will automatically use the current context in your kubeconfig file (i.e. whatever cluster oc cluster-info shows).
0 commit comments