openwhisk-deploy-kube icon indicating copy to clipboard operation
openwhisk-deploy-kube copied to clipboard

EKS deployment does not accept https requests, only http

Open ferancona opened this issue 3 years ago • 0 comments

Steps to reproduce the issue

  1. Create EKS cluster: eksctl create cluster --name test-cluster-1 --region eu-central-1 --node-type t2.large --nodes 1
  2. Label nodes: kubectl label nodes --all openwhisk-role=invoker
  3. Install Helm chart: helm install owdev openwhisk-deploy-kube/helm/openwhisk -n openwhisk --create-namespace -f mycluster.yaml
  4. Setup WSK CLI as the docs say, using the load balancer's DNS: wsk -i property set --apihost https://<load-balancer-DNS>:443
  5. Run WSK command: wsk list -v

Observations

  • Output of wsk list -v: image
  • Load balancer's info from AWS Console: image
  • Api calls work when setting up the WSK CLI using http instead of https.

mycluster.yaml

k8s:
  persistence:
    enabled: false

whisk:
  ingress:
    type: LoadBalancer
    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::XXXXXXXXXXXX:server-certificate/ow-self-signed

whisk:
  ingress:
    awsSSL: "true"
    type: LoadBalancer
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http
      service.beta.kubernetes.io/aws-load-balancer-ssl-ports: https-api
      service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:eu-central-1:XXXXXXXXXXXX:certificate/YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY # AWS Certificate Manager (ow-self-signed).

Reason of interest

I want to use the OpenWhisk deployment as an endpoint for AWS EventBridge, but currently it is only possible to add API Destinations that use https endpoints.

ferancona avatar Aug 19 '22 19:08 ferancona