ephemeris-lappis opened a new issue, #6433:
URL: https://github.com/apache/camel-k/issues/6433

   ### Bug description
   
   An integration that works using camel-k 2.8.0 fails mounting a PVC.
   
   The integration code is like :
   
   ```
   apiVersion: camel.apache.org/v1
   kind: Integration
   metadata:
     name: phi-test-0-16
     labels:
       phi-marker: test-0
   spec:
     traits:
       mount:
         volumes:
           - phi-pvc-0-01:/share
     flows:
       - route:
           id: "phi:test-0-16"
           from:
             uri: file:/share/TEST16/input
             parameters:
               delete: true
             steps:
               - log: File ${header.CamelFilePath} = ${body}
   ```
   
   And in the operator's logs an error message seems to say that there's 
insufficient privilege for mounting (watching) PVC in th cluster :
   
   ```
   
{"level":"error","ts":"2025-12-26T14:27:08Z","logger":"controller-runtime.cache.UnhandledError","msg":"Failed
 to 
watch","reflector":"k8s.io/[email protected]/tools/cache/reflector.go:290","type":"*v1.PersistentVolumeClaim","error":"failed
 to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User 
\"system:serviceaccount:phi-camel-01:camel-k-operator\" cannot list resource 
\"persistentvolumeclaims\" in API group \"\" in the namespace 
\"phi-camel-01\"","stacktrace":"k8s.io/apimachinery/pkg/util/runtime.logError\n\tk8s.io/[email protected]/pkg/util/runtime/runtime.go:221\nk8s.io/apimachinery/pkg/util/runtime.handleError\n\tk8s.io/[email protected]/pkg/util/runtime/runtime.go:212\nk8s.io/apimachinery/pkg/util/runtime.HandleErrorWithContext\n\tk8s.io/[email protected]/pkg/util/runtime/runtime.go:198\nk8s.io/client-go/tools/cache.DefaultWatchErrorHandler\n\tk8s.io/[email protected]/tools/cache/reflector.go:205\nk8s.io/client-go/tools/cache.(*Reflector).RunWith
 
Context.func1\n\tk8s.io/[email protected]/tools/cache/reflector.go:361\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1\n\tk8s.io/[email protected]/pkg/util/wait/backoff.go:233\nk8s.io/apimachinery/pkg/util/wait.BackoffUntilWithContext.func1\n\tk8s.io/[email protected]/pkg/util/wait/backoff.go:255\nk8s.io/apimachinery/pkg/util/wait.BackoffUntilWithContext\n\tk8s.io/[email protected]/pkg/util/wait/backoff.go:256\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil\n\tk8s.io/[email protected]/pkg/util/wait/backoff.go:233\nk8s.io/client-go/tools/cache.(*Reflector).RunWithContext\n\tk8s.io/[email protected]/tools/cache/reflector.go:359\nk8s.io/client-go/tools/cache.(*controller).RunWithContext.(*Group).StartWithContext.func3\n\tk8s.io/[email protected]/pkg/util/wait/wait.go:63\nk8s.io/apimachinery/pkg/util/wait.(*Group).Start.func1\n\tk8s.io/[email protected]/pkg/util/wait/wait.go:72"}
   ```
   
   This has been working with several examples on the same cluster with camel-k 
2.8.0.
   
   New privilege requirements for 2.9.0, or just a bug ?
   
   ### Camel K or runtime version
   
   2.9.0


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