Image pushed for Jenkins build #1:

quay.io/infinispan-test/server-native:PR-118

Image pushed for Jenkins build #2:

quay.io/infinispan-test/server-native:PR-118

👋 Hi! I'm trying out Infinispan, and the native image looked very interesting to me as an option - I don't personally have a ton of experience with the JVM 🙇

However, I'm running in kubernetes, and ran into this precise issues - I was wondering if this fix was going to be released soon? I'm not sure what the release schedules are like for the project. 😄

I can also try building and running my own image with the fix for now, if it's not going to be released anytime soon-ish. But I figured it was worth asking before I went down that path 😆

@ahayworth This isn't a high priority issue for us at the moment and I don't expect that it will be fixed in the short term. The native server is still a WIP with many features disabled etc. If you're running in k8s, I recommend that you use our JVM based server images which has a lot more test coverage and has frequent bug/feature fixes.

https://quay.io/repository/infinispan/server?tab=tags&tag=latest

Of course, if you have the time to look into this and are able to get this working, PRs are always welcome 🙂

This isn't a high priority issue for us at the moment and I don't expect that it will be fixed in the short term. The native server is still a WIP with many features disabled etc.

@ryanemerson That's actually really good to know, thank you! I had assumed that it was more or less a feature-complete, supported alternative - but that assumption was clearly incorrect! 😆

I'll take your advice and keep working with the JVM image for now. Thank you for the response, I appreciate it!