Hi Devs, Today we fixed an issue in KubernetesIaaS class which prevented Kubernetes workflow on EC2 and now it's working without a problem.
The problem was that we were using the minion's public IP addresses when creating Kubernetes services. As a result iptable rules were not properly creating to forward the traffic to the Kubernetes services. *Scenario* - A Kubernetes cluster was created in EC2 using their latest AMIs: One master and three minions. - A PHP Docker image was created with Stratos cartridge agent. - Stratos was run in single JVM mode with Active MQ in another VM. - A sample Stratos application (single-cartridge sample) was deployed containing the above Docker cartridge. - A PHP docker container cluster (a set of pods) was created and Kubernetes service was created for load balancing. - Kubernetes service is accessed via the minion public IP and auto-generated port. Thanks -- Imesh Gunaratne Senior Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
