odo version
odo login
I set the proxy in order for IJ to connect the license server and get the plugins, my only concern was: does the connector use it? but it seems not to be an issue at the end because I excluded my company domains from being proxy in case the connector would use it.
I hope there are using the same kube config, how can I make sure ?
odo version:
odo v1.0.0 (4e3175e6f)
Server: https://ose-master-np.inv.adroot.lgim.com:8443
OpenShift: v3.11.117
Kubernetes: v1.11.0+d4cacc0
and odo login performs well too:
odo login
Connecting to the OpenShift cluster
Authentication required for https://ose-master-np.inv.adroot.lgim.com:8443 (openshift)
Username: FT89797
Password:
Login successful.
You have access to 118 projects, the list has been suppressed. You can list all projects with 'odo projects'
Using project "distribution-build-tools".
import java.io.File;
public class NetworkTestDrive {
public static void main(String[] args) {
System.out.println(new File(getKubeConfigPath()).exists());
}
public static String getKubeConfigPath() {
return System.getProperty("user.home") + "/.kube/config";
}
}
I will, just in between, I can confirm that the connector tries to login because if I pass a wrong password, I get :
Error: Process exited with an error: 1 (Exit value: 1) Connecting to the OpenShift cluster
Login failed (401 Unauthorized)
Verify you have provided correct credentials.
X challenger chose not to retry the request
@sbouchet I found an initial workaround, I created a windows link into my %USERPROFILE% (c:\Users\<ME>) pointing to %HOMESHARE%%HOMEPATH%.kube (H:.kube) and created a new %USER_HOME% with %USERPROFILE% as value and got something.
I'm not sure how should look like the initial connector view but I got that now:
import java.io.File;
public class NetworkTestDrive {
public static void main(String[] args) {
System.out.println(Files.exists(new File(getKubeConfigPath()).toPath()));
}
public static String getKubeConfigPath() {
return System.getProperty("user.home") + "/.kube/config";
}
}
yeah, I've seen the code, I was only thinking that relying on the USER_HOME env var for windows users would force the user to create one when it does not exist and might not be the location of the .kube when weirdly set by some companies' IT team.
that's the reason why i was suggesting to add a connector configuration setting in the IDE for the .kube lookup path although the env var might be good enough for the time being.
Another point that is a blocker is the odo ability to use proxies, I've seen an open issue on that on the connector an on odo itself, do you know if anyone has already started looking at it ? If not I might have a look.