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
If a kubernetes or openshift component define endpoints with the same target port, the devworkspace will be deemed invalid and will fail to start. Since Kubernetes & OpenShift components are intended to run in a separate pod from container components, it should be valid to have them use the same target port in their endpoints.
How To Reproduce
Start a devworkspace that defines a container component and kubernetes (or openshift) component that both use the same target port in their endpoints, such as the following:
The issue seems to be coming from the devfile validation in the devfile API. Upgrading the devfile API dependency used in DWO (similar to what was done for the devfile library) should resolve the issue.
The text was updated successfully, but these errors were encountered:
Description
If a kubernetes or openshift component define endpoints with the same target port, the devworkspace will be deemed invalid and will fail to start. Since Kubernetes & OpenShift components are intended to run in a separate pod from container components, it should be valid to have them use the same target port in their endpoints.
How To Reproduce
Start a devworkspace that defines a container component and kubernetes (or openshift) component that both use the same target port in their endpoints, such as the following:
The devworkspace will fail to start, with the following error message:
* devfile contains multiple containers with same endpoint targetPort: 8080
Expected behavior
The devworkspace should start up correctly (or rather, it should not fail to start due to the same endpoint target port being used)
Additional context
Downstream issue: https://issues.redhat.com/browse/CRW-4856
Related Devfile API issue: devfile/api#1049
The issue seems to be coming from the devfile validation in the devfile API. Upgrading the devfile API dependency used in DWO (similar to what was done for the devfile library) should resolve the issue.
The text was updated successfully, but these errors were encountered: