--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/hashicorp/otto/issues
IRC: #otto-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Otto" group.
To unsubscribe from this group and stop receiving emails from it, send an email to otto-tool+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/otto-tool/6e6d9813-21f3-4cb0-b7f2-198de52f8d6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Rodrigo,Otto has not been superseded by anything else at HashiCorp, we have just shiftedsome of our priorities and haven’t been able to dedicate as many resources to theproject. However, a lot of work that we are doing on other projects internally will belanding in Otto as we are able to dedicate more resources to it.
There are no plans to integrate with Kubernetes currently but Otto is designed to supportmultiple backend implementations. The Appfile is agnostic to the underlying infrastructure,so it would be possible to implement a Kubernetes backend if you wanted!
Rodrigo,
There isn’t great documentation available, but if you look at the repo in the “infrastructure”and “foundation” folders, you will see that its an interface that must be implemented, andthat there are specific implementations for AWS, Consul, etc. There are factory functionsthat allow it to be extended to support multiple implementations of those various layers soI would start there!