-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debugging dont work #1
Comments
I'm not sure if any special step is required. While writing I did most of my testing on minikube. I will test this on 3.11 and get back on this. |
Unfortunately, I could not try it out on Openshift online as I don't have access to create CRDs on the Openshift online cluster I use.
When I ran this on Minishift, I was able to hit breakpoint: However, I also faced the same error. I think it is because I hardcoded namespace here: podsetoperatorinjava/src/main/java/io/fabric8/podset/operator/controller/PodSetController.java Lines 34 to 41 in 8faf9eb
I think we should pick namespace either from kubeconfig or maybe as a commandline argument. |
As reported in #1 , this project doesn't seem to be working for users who have namespace set other than default.
Problem
The java application starts very well
but if we want to debug, then break points is not called when a CR is deployed on ocp3.11
and logs report such information
Question: Do we have to perform a specific step to debug a java operator (= connected to an informer queue) ?
The text was updated successfully, but these errors were encountered: