manduinca opened a new pull request, #6902:
URL: https://github.com/apache/camel-k/pull/6902

   I add the `CamelMonitorAvailable` condition and a `Camel Monitor` kubectl 
column to show whether an Integration has an associated monitor. I keep this 
discovery information independent of runtime readiness.
   
   I verify the monitor's name, namespace and owner UID, either directly 
through the Integration or through its Deployment/CronJob. I reuse the 
unstructured lookup helper and handle monitor creation, deletion and ownership 
changes, including non-controller owners. Missing resources report `False`; 
lookup failures report `Unknown` and retry after 30 seconds.
   
   I register optional watches after checking discovery and permissions for 
each effective namespace. I add only `get/list/watch` permissions for 
CamelMonitor and regenerate the CRD and Helm artifacts. I document the restart 
needed when the CRD or watch permissions are added after operator startup. The 
lookup follows the same-name contract; it does not discover revision-suffixed 
monitors.
   
   Validation:
   - 45 new test results pass, covering association, lifecycle events, optional 
watches, permissions, reconciliation and unchanged Ready/Phase behavior.
   - `make generate`, `make update-docs`, `make fmt`, `make goimport` and `make 
lint` pass; lint reports 0 issues.
   - The unfiltered `make test` run reports 1,427 passes, one skip and one 
failure: `TestGitCloneCommit` in the unchanged builder package. I reproduced 
the same `worktree contains unstaged changes` failure in a clean worktree at 
`main` (`a27343186`).
   - I checked the generated CRD/Helm column and both RBAC scopes. I have not 
run cluster e2e tests.
   
   Fixes #6898
   
   For the code, AI directed by me (@manduinca). I write it, AI helps with my 
English.
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to