lburgazzoli commented on pull request #2058:
URL: https://github.com/apache/camel-k/pull/2058#issuecomment-782087407
> > How does this strategy handle the case where you programmatic create an
IntegrationKit ?
>
> Well, no problems if the integrationKit is co-located with the integration
platform (i.e. it's in the operator namespace).
>
Yep but normal user should not create stuffs in the operator namespace
> But probaly we should allow also local references... But at the same time
we need not to complicate the model too much... thinking...
Maybe instead of having
```yaml
status:
platformNamespace
```
Each linked resource should report the information about the namespace ?
```yaml
status:
kit:
# optional, current if omitted
namespace:
name:
```
I guess it won't be too hard :D to have cascading lookup.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
