I2P Enterprise story
Everything we do related to I2P and Kubernetes should, given the limitations of compatibility be fully usable in production by our Enterprise customers. That means that we might not support all infrastructure, but if you are running Kubernetes, you should be able to use all our tools. If we ship things and don't call them 'Alpha' or 'Beta', the will be considered production-ready.
This means that we need to be able to check off the following things for everything that we've shipped for I2P (and everything else we've shipped):
- Guides for production-level setups
- Backup strategies
- Scaling
- Security
- Updates and upgrades
- Full customer support for anything that comes out of this
I fear that we run into the risk of having a large customer building on what we have now, say Auto Deploy, hitting a roadblock and us not being able to support or help them further. I might be wrong, but I believe we don't have the things I've listed above now.
We can do this the same way we always iterate. We start by trying to fully support one type of application and move from there. Assuming Rails users are often early-adopters and fast movers, being able to run a full Rails app, scale it, secure it, make sure it's backed up, etc would be a good start.
@markpundsack I'd love to hear your thinking about this.
cc @gl-product