maxClusterUnavailable Parameter Does Not Reflect To Domain Resource (Doc ID 2997062.1)

Last updated on JANUARY 11, 2024

Applies to:

Symptoms

When deploying WebLogic into Verrazzano, maxClusterUnavailable in WebLogicWorkLoad does not reflect to weblogic.oracle.Domain resource.

In vz-application.yaml

apiVersion: core.oam.dev/v1alpha2
kind: Component
metadata:
name: test-domain-domain
namespace: test-domain
spec:
workload:
apiVersion: oam.verrazzano.io/v1alpha1
kind: VerrazzanoWebLogicWorkload
spec:
template:
metadata:
name: test-domain-domain
namespace: test-domain
spec:
domainUID: test-domain
domainHome: /u01/domains/base_domain

:
:
maxClusterUnavailable: 2
:

But Domain resource is here:
apiVersion: v1
items:
- apiVersion: weblogic.oracle/v9
kind: Domain
metadata:
:
:
maxClusterConcurrentShutdown: 1
maxClusterConcurrentStartup: 0
maxClusterUnavailable: 1

:

Then ALLOWED DISRUPTIONS is still 1

kubectl get pdb -n test-domain
NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE
test-domain-cluster_1 2 N/A 1 47m

If modified Domain resource to 2,ALLOWED DISRUPTIONS is 2 as expected.

kubectl get pdb -n test-domain
NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE
test-domain-cluster_1 2 N/A 2 47m

How to reflect this parameter to Domain resource from VerrazzanoWebLogicWorkload?

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.