Consider dropping support for openresty

[fzipi]

After merging support from @TafkaMax on the openresty image, there has been low to zero maintenance, unless the core team does it.

We did mentioned in the past that without additional support/care for the image, we will not maintain it because of bandwidth.

I think we are reaching that limit where we need to have a confirmation from @TafkaMax that maintenance is going to be there, or we are forced to drop this build.

So now we would like to hear from the community, adding comments to the issue, or the next logical step will be to remove support for openresty.

[TafkaMax]

Sorry, yes, I do not have enough time to maintain it unfortunately. As I have not updated it at my use cases, I haven't delved deep into updating it in the repo aswell.

[fzipi]

I understand that you didn't updated it for your use case anymore. If you feel like giving back some time to fix or add some use cases that are different from your daily job is complicated, no problem.

But this is a community, and we share the responsibility of updating the images. If you don't have the time that you know and use the image, why should we maintain it if we aren't users? :)