-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Question on fips compliance #2732
Milestone
Comments
I am having the same issuе here. Really hope this gets checked out. |
11 tasks
@SubhraB , @DimoDonchev , I've created PR with a fix. Hope that it will be merged and solve our problem. |
I got around it by not using the default k8s client. Buts its a little pain. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are using the k8s client version 4.13.0.
I was looking at this class.
io.fabric8.kubernetes.client.internal.CertUtils
Specifically the code below, which I see multiple instances of.
KeyStore trustStore = KeyStore.getInstance("JKS");
The above line of code becomes invalid when we run our application on fips mode, since the truststore format becomes BCFKS. We expect something like this.
KeyStore trustStore = KeyStore.getInstance(KeyStore.getDefaultType());
Is there a way to override that to make us fips compliance. FYI, we are not allowed to make insecure https calls, we have to use a truststore in BCFKS format
The text was updated successfully, but these errors were encountered: