squakez commented on pull request #1912: URL: https://github.com/apache/camel-k/pull/1912#issuecomment-762733070
> Great, let's dive into the `version` endpoint approach 👍🏼. > > The health and monitoring endpoints are delegated to controller-runtime: > > https://github.com/apache/camel-k/blob/aaeb4573fb62881fae1f6fa0b8f20695237414d4/pkg/cmd/operator/operator.go#L130-L131 > . > > I'm not sure it's possible to hook into these. Otherwise we can start our own listener. > > For the backward compatibility point, better sooner than later wink. I had a thought at the possibility to include a version endpoint. If we go in that direction we must expose the version endpoint publicly in order to be externally read: health and monitoring are not public endpoint. We also may have difficulty to know beforehand where a `global` operator is installed. I like the idea to expose something but I feel we need a wider discussion and a more devised design: I can open an issue to follow up with that. In the while I think we have a better way to deal with the problem and solve the `global` installation point. We can check the `IntegrationPlatfom` that contains the version and is installed in each namespace where an operator is watching (also a global one). How do you see this? ---------------------------------------------------------------- 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
