-
Notifications
You must be signed in to change notification settings - Fork 91
Enhancement Request: Support initializeDomainOnPV in discoverDomain output for WebLogic Kubernetes Operator #1628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@mxb904 Thanks for the suggestion. Unfortunately, the The basic idea would be for you to create your own templatized model file that only contains the The high level provisioning process flow would be something like:
Discussing this internally, this seems like it would create a much better result than almost anything we could do as a result of enhancing discoverDomain. |
@mxb904 Any update on our proposed procedure? |
@robertpatrick Thank you for the explanation, and apologies for the delayed response. I’m not entirely clear on the steps you outlined, but let me share our current approach:
Would it be possible to provide an example based on your suggestion, especially how to create and apply the templatized model in conjunction with the discovered model? |
Hello mxb904 - The templatized model we're discussing would have only a kubernetes:
domain:
spec:
configuration:
initializeDomainOnPV:
domain:
domainType: JRF
persistentVolume:
spec:
storageClassName: test The
Let us know if you have any more questions about this process. |
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: