Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sourceless Integration status show default provider/version #5309

Closed
squakez opened this issue Apr 2, 2024 · 0 comments · Fixed by #5378
Closed

Sourceless Integration status show default provider/version #5309

squakez opened this issue Apr 2, 2024 · 0 comments · Fixed by #5378
Labels
kind/bug Something isn't working
Milestone

Comments

@squakez
Copy link
Contributor

squakez commented Apr 2, 2024

Running a sourceless Integration always report the default provider and the default runtime version:

$ kubectl get it -w
NAME   PHASE     RUNTIME PROVIDER   RUNTIME VERSION   KIT       REPLICAS
csb    Running   quarkus            3.2.3             kit-csb   1
csb    Running   quarkus            3.2.3             kit-csb   0
@squakez squakez added the kind/bug Something isn't working label Apr 2, 2024
@squakez squakez changed the title Sourceless Integration status show Quarkus provider Sourceless Integration status show default provider/version Apr 2, 2024
@squakez squakez added this to the 2.4.0 milestone Apr 5, 2024
squakez added a commit to squakez/camel-k that referenced this issue Apr 17, 2024
... for external kit or syntetic Integrations.

As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default.

Closes apache#5309
squakez added a commit to squakez/camel-k that referenced this issue Apr 19, 2024
... for external kit or syntetic Integrations.

As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default.

Closes apache#5309
squakez added a commit to squakez/camel-k that referenced this issue Apr 23, 2024
... for external kit or syntetic Integrations.

As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default.

Closes apache#5309
squakez added a commit that referenced this issue Apr 23, 2024
... for external kit or syntetic Integrations.

As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default.

Closes #5309
squakez added a commit to squakez/camel-k that referenced this issue Apr 23, 2024
... for external kit or syntetic Integrations.

As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default.

Closes apache#5309
squakez added a commit that referenced this issue Apr 24, 2024
... for external kit or syntetic Integrations.

As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default.

Closes #5309
squakez added a commit to jboss-fuse/camel-k that referenced this issue Apr 24, 2024
... for external kit or syntetic Integrations.

As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default.

Closes apache#5309

(cherry picked from commit apache/camel-k@3e7006887)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant