squakez edited a comment on issue #2469: URL: https://github.com/apache/camel-k/issues/2469#issuecomment-871382117
I've just tried locally with `minikube` and version `1.4`. Cannot reproduce the issue. ``` $ k get pods -w NAME READY STATUS RESTARTS AGE camel-k-operator-784d84fdc9-sc9n8 1/1 Running 0 3m2s sample-5cc76747fc-84cfw 0/1 Pending 0 1s sample-5cc76747fc-84cfw 0/1 Pending 0 1s sample-5cc76747fc-84cfw 0/1 ContainerCreating 0 1s sample-5cc76747fc-84cfw 1/1 Running 0 5s sample-5dc7f8dd89-fhkr8 0/1 Pending 0 0s sample-5dc7f8dd89-fhkr8 0/1 Pending 0 0s sample-5dc7f8dd89-fhkr8 0/1 ContainerCreating 0 0s sample-5dc7f8dd89-fhkr8 1/1 Running 0 3s sample-5cc76747fc-84cfw 1/1 Terminating 0 42s sample-5cc76747fc-84cfw 0/1 Terminating 0 45s sample-5cc76747fc-84cfw 0/1 Terminating 0 46s sample-5cc76747fc-84cfw 0/1 Terminating 0 46s sample-5dc7f8dd89-fhkr8 1/1 Terminating 0 13s sample-5dc7f8dd89-fhkr8 0/1 Terminating 0 14s ``` The second `Pod` take over when I made a change on the source file (as it is expected in the `--dev` option). What version and what cluster are you running? Do you have by any chance an editor or any other process open the integration file? The `--dev` is controlling any change happening on the file, and redeploy accordingly. Can you run the same integration without the `--dev` to verify if you have the same behavior? -- 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]
