Describe the Bug
After creating an AppWrapper, the logs display that there are 0 pods while there are actually 3 pods running.
The reason for this is that the pods created have the label i.e., ray.io/cluster when they should have appwrapper.mcad.ibm.com. As discussed in this PR, it seems the controller owning the resource / generic item is overwriting the label applied by MCAD.
Steps to Reproduce the Bug
- With MCAD running
- Create an AppWrapper
- Search in the MCAD logs for
There are.
- See 0 pods of your AppWrapper, when there should be 3.

AND
- With MCAD running
- Create an AppWrapper
- Check the pods' labels
Expected Behavior
When an AppWrapper is created, the logs should display the correct number of pods for the AppWrapper.
Component Versions
Kuberay: v0.5.0
MCAD: latest main branch
Describe the Bug
After creating an AppWrapper, the logs display that there are 0 pods while there are actually 3 pods running.
The reason for this is that the pods created have the label i.e.,
ray.io/clusterwhen they should haveappwrapper.mcad.ibm.com. As discussed in this PR, it seems the controller owning the resource / generic item is overwriting the label applied by MCAD.Steps to Reproduce the Bug
There are.AND
Expected Behavior
When an AppWrapper is created, the logs should display the correct number of pods for the AppWrapper.
Component Versions
Kuberay: v0.5.0
MCAD: latest main branch