K
Q

Migrating karaf from Legacy deployment to cloud with active-standby deployment

6/23/2018

Currently we have karaf deployment like following

  • Its active-standby
  • Standby is there with startlevel as 50 so failover would be fast as system bundles are at start status and user bundles are at install status
  • As soon as active goes down standby takeover.

Now we planned to migrate to kubernetes, as per current research

Kubernetes will create 1 pod for us and we declare happy state as 1 which mean if POD goes down it will automatically launch new, but my concern is launching of new POD will take more time as in legacy deployment, standby was in semi active state.

How we can achieve such active-standby in kubernetes?

-- ImranRazaKhan
apache-camel
apache-karaf
docker
karaf
kubernetes

Similar Questions

Kubernetes LoadBalancer with new IP per service from LAN DHCP
Ingress on GKE is using ephemeral addresses despite specifiying a static one
How to mount HostPath Volume in Kubernetes with SELinux
How to change a running pod name?
Kubernetes: use environment variable/ConfigMap in PersistentVolume host path
Gridgain Partitions loss with node scale down
How to mount aws EC2 files on aws EKS as presistent volume?

1 Answer

6/25/2018

Answer provided by Tomislav Mikulin in comments:

That depends on if you app is stateless or not...if its stateless that just use more then one pod (like 2 or 3) for your app, and you should be all set...

If you don't want (or can't) have multiple pods of you app already running, you could make two different deployments of the same app, and just switch them through the Service object. That way you could have an extra pod running that you can switch on at any moment.

-- VAS
Source: StackOverflow