In my series of blogs around WebLogic, containers and Kubernetes I’d like to tell you about “old meets new”. Well “Old” is maybe an inappropriate term in this case, but what I actually mean is how WebLogic’s relation to traditional infrastructure like servers and VMs and from a container based perspective with a container orchestrator platform such as Kubernetes, and Oracle’s cloud implementation of it, Oracle Container Clusters(OKE) holds.
Kubernetes as a platform knows all about it’s pods, services, policies, persitent volumes and so on, but as demands of what to containerize became more demanding, it was not sufficient anymore. If you have a stateless web app to control, in a lightweight container, kubernetes can handle it well. But an entire database or application server platform in a container is something different. Specific tasks and details regarding all kinds of configurations and operations can never be handled by kubernetes, similar to a VM or server; they can’t do that either.
Here Operators will be implemented.
· They extend the K8S api
· Configure & manage more complex instances
· They leverage more experience based knowledge to Kubernetes. Read the complete article here.
For regular information become a member in the Developer Partner Community please register here.
Blog Twitter LinkedIn Facebook Meetups
Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic