We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Doing:
kamel run TLS.java --resource trust.jks
The sha256sum of the trust.jsk file in the container is different from the original one, which means something has corrupted it.
trust.jsk
Workaround is:
kubectl create secret generic trust --from-file trust.jks kamel run TLS.java --secret trust
Which is also a best practice for such data, but this problem may cause other issues.
Tested on: https://self-signed.badssl.com/
The text was updated successfully, but these errors were encountered:
Fix apache#1750: auto-compress/encode binary sources and resources
10d36bf
Fix #1750: auto-compress/encode binary sources and resources
82e7e03
Tried with v 1.2, and jks files are still getting corrupted. Compared the file size and its different when bundled with camel. Woks fine for txt file.
e.g kamel run kafka.java --resource keystore.jks --resource truststore.jks
Caused by: java.io.IOException: Invalid keystore format
The workaround is what i am still using and it seems to work.
Sorry, something went wrong.
This is strange, as binary resources are base64 encoded.
@rampraveen83 can you try with:
kamel run kafka.java --resource keystore.jks --resource truststore.jks --compression=true
Compression is the mechanism that we tried to auto-enable on 1.2 to avoid corruption. Also, can you double check the version with kamel version?
kamel version
kamel run
nicolaferraro
Successfully merging a pull request may close this issue.
Doing:
The sha256sum of the
trust.jsk
file in the container is different from the original one, which means something has corrupted it.Workaround is:
Which is also a best practice for such data, but this problem may cause other issues.
Tested on: https://self-signed.badssl.com/
The text was updated successfully, but these errors were encountered: