2020-05-07 01:23:11 UTC - Lixiang Ao: I’m trying to deploy OW on Amazon EKS. But, when running `helm install owdev ./helm/openwhisk -n openwhisk -f mycluster.yaml` , I get this error: > create: failed to create: namespaces “openwhisk” not found does this mean I need to manually create a kubernetes namespace called openwhisk? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588814591221800?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 01:43:50 UTC - Lixiang Ao: I just did. It seems to be the case. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588815830221900?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 01:53:35 UTC - Dave Grove: Yes. Our docs should be more explicit about that. Helm v2 used to create the namespace for you if it didn’t exist. Helm v3 treats it as an error. +1 : Lixiang Ao https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588816415222100?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 16:13:17 UTC - Lixiang Ao: `helm install` seems successful. however, `kubectl get services -o wide` shows the cluster has no EXTERNAL-IP. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588867997224200?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 16:14:19 UTC - Lixiang Ao: the cluster was created following the EKS example using eksctl <https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588868059224400?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 16:14:53 UTC - Lixiang Ao: with commands in “*Cluster with Linux-only workloads*” https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588868093224700?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 16:17:29 UTC - Lixiang Ao: so I manually add the externalIP by `kubectl edit svc` and change the type to LoadBalancer https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588868249225000?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 16:18:34 UTC - Lixiang Ao: then there’s an externalIP that wsk can talk to, but wsk gives *403 Error* https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588868314225200?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 16:26:50 UTC - Lixiang Ao: I can think of 2 possible causes of the problem. First, kubernetes was not created correctly. Is there any special parameters needed when creating the cluster? Second, the doc says upload and use the certificate created when building OW. However, building OW only creates the private key. I had to create the certificate using the private key. Could that be the problem? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588868810225400?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 16:29:06 UTC - Lixiang Ao: sorry about the length questions https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588868946225700?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 16:55:03 UTC - Dave Grove: i haven’t personally deployed on Amazon EKS for over a year. You might want to open a top-level conversation in <#C4J3R7JFL|kubernetes> channel so that others who have done it can try to help. There is some documentation <https://github.com/apache/openwhisk-deploy-kube/blob/master/docs/k8s-aws.md> that might be relevant if you haven’t looked at it already. We did get some fixes to that doc about a month ago, so I think it is probably still accurate https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588870503225900?thread_ts=1588814591.221800&cid=C3TPCAQG1 ---- 2020-05-07 17:00:39 UTC - Lixiang Ao: sounds good. thanks! https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1588870839226100?thread_ts=1588814591.221800&cid=C3TPCAQG1 ----
