[openwhisk-deploy-kube] branch master updated: Update k8s-aws.md (#589)

[dg...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dgrove pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk-deploy-kube.git


The following commit(s) were added to refs/heads/master by this push:
     new 9cf4a27  Update k8s-aws.md (#589)
9cf4a27 is described below

commit 9cf4a271e48d1eec9d8dbda853a43047b11022c7
Author: Tom Barber <to...@spicule.co.uk>
AuthorDate: Mon Mar 9 13:59:53 2020 +0000

    Update k8s-aws.md (#589)
    
    Since EKS 1.11 which is the oldest you can deploy there has been support for default storageclasses (https://docs.aws.amazon.com/eks/latest/userguide/storage-classes.html)
    As such I propose we remove the stuff about PVCs because with it enabled it allocates volumes just fine.
---
 docs/k8s-aws.md | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/docs/k8s-aws.md b/docs/k8s-aws.md
index 4e0ffee..5fa956a 100644
--- a/docs/k8s-aws.md
+++ b/docs/k8s-aws.md
@@ -73,18 +73,8 @@ whisk:
     annotations:
       service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
       service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:iam::12345678901:server-certificate/ow-self-signed
-
-k8s:
-  persistence:
-    enabled: false
 ```
 
-For ease of deployment, you should disable persistent volumes because
-EKS does not come with an automatically configured default
-StorageClass. Alternatively, you may choose to leave persistence
-enabled and manually create the necessary persistent volumes using
-AWS/EKS instructions to do so.
-
 Shortly after you deploy your helm chart, an ELB should be
 automatically created. You can determine its hostname by issuing
 the command `kubectl get services -o wide`. Use the value in the
@@ -100,9 +90,5 @@ errors from `wsk` when attempting to access it.
 
 ## Limitations
 
-Without additional configuration to enable persistent volumes, EKS is
-only appropriate for development and testing purposes.  It is not
-recommended for production deployments of OpenWhisk.
-
 If you used a self-signed certificate, you will need to invoke `wsk`
 with the `-i` command line argument to bypass certificate checking.