You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently migrating our WebLogic domains to Kubernetes using the WebLogic Kubernetes Operator, and we've chosen the Domain-on-PV pattern as our preferred configuration—primarily because most of our domains are ADF (JRF) based.
As part of this migration, we are deploying empty domains and planning to use the new initializeDomainOnPV feature introduced in the operator. However, when using the discoverDomain tool to generate model files, there is currently no way to include the initializeDomainOnPV field in the resulting model, even when using -target wko or -target wko-pv.
We would like to request support for this feature in discoverDomain. Automatically populating initializeDomainOnPV (perhaps via a flag or template option) would help streamline our domain setup process and reduce the need for post-processing the generated model.
Thank you for considering this enhancement!
The text was updated successfully, but these errors were encountered:
Hi team,
We are currently migrating our WebLogic domains to Kubernetes using the WebLogic Kubernetes Operator, and we've chosen the Domain-on-PV pattern as our preferred configuration—primarily because most of our domains are ADF (JRF) based.
As part of this migration, we are deploying empty domains and planning to use the new initializeDomainOnPV feature introduced in the operator. However, when using the discoverDomain tool to generate model files, there is currently no way to include the initializeDomainOnPV field in the resulting model, even when using -target wko or -target wko-pv.
We would like to request support for this feature in discoverDomain. Automatically populating initializeDomainOnPV (perhaps via a flag or template option) would help streamline our domain setup process and reduce the need for post-processing the generated model.
Thank you for considering this enhancement!
The text was updated successfully, but these errors were encountered: