ArcGIS Enterprise Kubernetes / GIS Functionality Comparison?

Question

Hi,

I'm preparing for a meeting with a technically-capable, tough but reasonable client who's interested in ArcGIS Enterprise for Kubernetes.

I'm wondering if there's a document with info on ArcGIS Enterprise for Kubernetes and the level of GIS feature parity? Specifically, is there a document where I can compare the level of GIS feature and capability completeness for ArcGIS Enterprise for Kubernetes vs. ArcGIS Enterprise (Windows/Linux)? And if there are any differences in the functionality between Kubernetes and non-Kubernetes, how they differ?

I've just spent a few hours trying to figure this out. The current authoritative references I can find are the "ArcGIS Enterprise Functionality Matrix" and the respective release blog article. 
The matrix would lead you to believe there is complete feature parity between ArcGIS Enterprise (Windows/Linux) and ArcGIS Enterprise for Kubernetes. 
But then, looking at the blog article "what's new in ArcGIS Enterprise 12.0 on Kubernetes", there are many contradictions.

It's hard to craft a coherent story with exceptions or surprise requirements (i.e.: Utility Network).

Thanks,

Derek

s.schuette_ct · Answer

Another important consideration is that when migrating from an on-premises deployment to Kubernetes (if that´s the case), WebGIS DR cannot be used for the migration process. To migrate content, consider using the group migration workflow or third-party solutions such as BackupMyOrg.

JoshuaBixby · Answer

I agree that ArcGIS Enterprise Functionality Matrix doesn't do a good job of explaining ArcGIS Enterprise Kubernetes functionality.  There are statements about ArcGIS Enterprise Kubernetes, but they are more along the lines of "see this" or "see that" for information rather than clearly stating how Kubernetes functionality relates.

That said, it seems like a simple question being asked, but it is hard to answer without knowing more of what you are really after.  For example, since ArcGIS Enterprise on Kubernetes can federate with regular ArcGIS Server deployments, one needs to know whether someone's requirement is to only deploy in Kubernetes or whether a hybrid approach is allowed.  If hybrid is allowed, than a lot more functionality and features are possible.

The other complication is that the underlying architecture of deploying ArcGIS Enterprise on Windows or Linux vs Kubernetes is fundamentally different.  Esri may make the REST APIs match, and the browser apps look and function the same, but under the hood they are very differently structured.  Because of this, Esri will sometime use terms like "equivalence" instead of "parity," and they focus more on describing outcomes and workflows than features and functionality when talking about the two types of architecture.

Overall, I agree with the sentiment that Esri does not do a great job helping customers understand the difference.  Also, I really don't care for blogs as being "official" documentation, but the "Summary of Supported Functionality" in the What's New in ArcGIS Enterprise 12.0 on Kubernetes blog is about as authoritative as I have seen.