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
Previously we were using app labels to define node selectors for CI on the application like selecting ARM-based machine or AMD-based machine to build the code but now this node selector is not working.
👟 Reproduction steps
Create an application and configure the build pipeline in the application
Now use the below label on app labels. Go to the overview page and add the label.
Key: devtron.ai/node-selector
Value: {"purpose": "arm-ci"}
Trigger the CI and check the manifest of the CI it won't use the given label.
👍 Expected behavior
It should use the node Selector as mentioned in the labels.
👎 Actual Behavior
It's not using the labels mentioned in the app labels, but using the default selector configured in orchestrator configmap.
☸ Kubernetes version
1.26
Cloud provider
AWS
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
📜 Description
Previously we were using app labels to define node selectors for CI on the application like selecting ARM-based machine or AMD-based machine to build the code but now this node selector is not working.
👟 Reproduction steps
Key: devtron.ai/node-selector
Value: {"purpose": "arm-ci"}
👍 Expected behavior
It should use the node Selector as mentioned in the labels.
👎 Actual Behavior
It's not using the labels mentioned in the app labels, but using the default selector configured in orchestrator configmap.
☸ Kubernetes version
1.26
Cloud provider
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
AB#6192
The text was updated successfully, but these errors were encountered: