Azure Kubernetes Service

Contents

Introduction

This sample demonstrates how to use the WebLogic Kubernetes Operator (hereafter “the operator”) to set up a WebLogic Server (WLS) cluster on the Azure Kubernetes Service (AKS). After going through the steps, your WLS domain runs on an AKS cluster. You have several options for managing the cluster, depending on which domain home source type you choose. With Domain in PV, you can manage your WLS domain by accessing the WebLogic Server Administration Console or WLST. With Model in Image, you use the operator to perform WLS administrative operations.

Note: For an alternative approach to this sample, see the Oracle WebLogic Server on AKS from the Azure Marketplace offering which automates the provisioning of AKS cluster, AKS resources, the Azure Container Registry (ACR), WebLogic Kubernetes Operator, and WebLogic Server images.

Azure Kubernetes Service cluster

Azure Kubernetes Service (AKS) makes it simple to deploy a managed Kubernetes cluster in Azure. AKS reduces the complexity and operational overhead of managing Kubernetes by offloading much of that responsibility to Azure. As a hosted Kubernetes service, Azure handles critical tasks like health monitoring and maintenance for you. The Kubernetes masters are managed by Azure. You manage and maintain only the agent nodes. As a managed Kubernetes service, AKS is free - you pay for only the agent nodes within your clusters, not for the masters.

To learn more, see What is Azure Kubernetes Service?

Domain home source types

This sample demonstrates running the WebLogic cluster on AKS using two domain home types. The instructions for each are self-contained and independent. This section lists the domain home source types recommended for use with AKS, along with some benefits of each. For complete details on domain home source types, see Choose a domain home source type.

  • Model in Image: running the WebLogic cluster on AKS with model in image offers the following benefits:

    • Reuse image to create different domains with different domainUID and different configurations.
    • Mutate the domain home configuration with additional model files supplied in a ConfigMap. Many such changes do not need to restart the entire domain for the change to take effect.
    • The model file syntax is far simpler and less error prone than the configuration override syntax, and, unlike configuration overrides, allows you to directly add data sources and JMS modules.

  • Domain in PV: running the WebLogic cluster on AKS with domain home in PV offers the following benefits:

    • Use standard Oracle-provided images with patches installed.
    • No Docker environment required. You are able to run your business quickly without building knowledge of Docker.
    • Mutate the live domain configuration with Administration Console from a browser or WLST.

Stop and Start an Azure Kubernetes Service (AKS) cluster using Azure CLI, as described in the azure docs. This allows you to optimize costs during your AKS cluster’s idle time. Don’t pay for running development clusters unless they are actively being used. You can pick up objects and cluster state right where you were left off.

References

For references to the relevant user documentation, see: