liqo icon indicating copy to clipboard operation
liqo copied to clipboard

Issue while offloading an application using pod-offloading-strategy

Open Priyaboliset opened this issue 2 years ago • 1 comments

.#### What happened: We tried to offload an application on peered clusters using pod-offloading-strategy on Remote, as per strategy it needs to run on only remote but pods are running on local cluster

liqo-eks liqo-pod-running-gke liqo-deploy-manifest liqo-pod-offloading-strategy liqo-peering

What you expected to happen:

Pods should run on remote cluster as per the pod-offloading-strategy

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

The steps we performed are below Step1: Peering is established between AWS and GCP Clusters. (Refer image : liqo-peering.png ) Step2: Created namespace and enabled pod-offloading-strategy on remote. (Refer Image: liqo-pod-offloading-strategy.png) Step3: Deployed manifest files in GCP cluster (Refer Image: liqo-deploy-manifest.png) Step4: When I check the pods, All the pods are running in gke cluster only. But ideally it has to run in aws cluster right? (Refer Image: liqo-pod-running-gke.png) Step5: No pods are listing in eks cluster.(Refer image : liqo-eks.png) using liqoctl version: v0.4.. Kindly help to resolve the issue asap Attached all the images for reference above

Environment:

  • Liqo version: liqoctl version: v0.4
  • Kubernetes version (use kubectl version):v1.21.14

Priyaboliset avatar Aug 09 '22 05:08 Priyaboliset

Hi @Priyaboliset,

Could you please post the yaml of one of the pods that is not scheduled correctly? And the logs of the liqo-webhook?

By the way, I would suggest you to upgrade liqo to the latest version, as we fixed different bugs, and many commands present in the current documentation are incompatible with v0.4.0.

giorio94 avatar Aug 09 '22 08:08 giorio94