-
Notifications
You must be signed in to change notification settings - Fork 78
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
support for nginx-ingress controller #282
Comments
Looks like a worthwhile and achievable goal. But again, I've been pretty alone working on these integrations and thus somewhat put them on the back burner (I'm motivated by cooperation and that's hard being the only guy :-). From a first glance-over of the IBM code, it might benefit from a resolution of #182 as it still uses the no longer supported OpenSSL111 code base. As you noticed I've been updating So the best advice to you that I can give is that you try to merge the Dockerfile logic in our |
Thanks for the detailed response. I understand your hesitation to contribute to the IBM project—it’s just the only example I found that does what I need. I'll do my best to merge the Dockerfile logic from your nginx integration with the Kubernetes one. Once I'm successful, I’ll be happy to contribute here. Thanks again, and I’ll reach out if I face any issues. |
Hello, I'm setting up a Kubernetes cluster with the Ingress Nginx controller from https://github.com/kubernetes/ingress-nginx. My aim is to create a custom Nginx Ingress Controller supporting quantum-safe keys. Specifically, I want to use p384_kyber768 as the default Key Encapsulation Mechanism (KEM) algorithm. However, I'm facing challenges in building the image for this custom controller. The default Nginx image provided here works perfectly. IBM made a custom ingress controller a while back, but it's outdated now and doesn't work anymore! https://github.com/IBM/qsc-ingress/tree/main/kubernetes/nginx. So, if you have any tips or tricks, I'd be super grateful!
The text was updated successfully, but these errors were encountered: