Document AWS limitations due to not running the CCM

[iaguis]

Until #145 is closed, we should document that LoadBalancer services and PersistentVolumeClaims won't work out of the box on the AWS platform.

We might consider documenting how to make NodePort services work as a fallback, this would require the user to open the corresponding Security Group.

Reported-by: @jpetazzo

[invidian]

Until #145 is closed, we should document that LoadBalancer services and PersistentVolumeClaims won't work out of the box on the AWS platform.

PersistentVolumeClaims will work with correct node type and openebs being deployed. Example configuration reflects that.

[iaguis]

PersistentVolumeClaims will work with correct node type and openebs being deployed. Example configuration reflects that.

Right, I'll remove that part from the description.

[invidian]

Right, I'll remove that part from the description.

I mean, I think we could also document this. And it would be applicable for all platforms. Actually having unified components would be nice here:

component "storage" {}