weblogic-kubernetes-operator: Domain resource can't be created successfully on Azure kubernetes Service
weblogic-kubernetes-operator:4.1.0 just released. I followed this domain-on-pv-sample step by step and try to create domain.
It worked when I run the sample with local minikube,
but when I tried to run the sample on AKS, and it failed in the last step – the step when I run the command kubectl apply -f /tmp/sample/domain-resource.yaml, I tried it for several times, but all failed.
It showed Job has reached the specified backoff limit.
I run the command kubectl get job <job-name> -o yaml > job.yaml to check the value of backoffLimit, and it is 0.
Could anyone tell what should I do if I want create domain with weblogic-kubernetes-operator:4.1.0 on AKS?
Attached is event log file.
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 18 (18 by maintainers)
@backwind1233 I don’t have access to an AKS environment to run the domain creation sample. From the
docker image inspectcommand output that you have provided above, the image is still usingarm64architecture and notamd64. Have you tried to build the image on a virtual machine? I’ll check with my colleagues tomorrow about why architecture is stillarm64after you setDEFAULT_DOCKER_PLATFORMenv variable tolinux/amd64.You can try setting the following environment variable before building the domain creation image on your Mac or build the image on a Linux VM.
export DEFAULT_DOCKER_PLATFORM=linux/amd64Please also consult the debugging document for debugging the problem.
@backwind1233 Can you upload the operator logs and events. From the screen snapshot, I see a
Failedevent for Domain with internal error but I can’t see the complete event. If you have captured the introspector job pod logs, please upload that as well.I see that you’ve already lengthened the timeout of the introspection job. Given that the timeout (activeDeadlineSeconds) is set at 10 minutes, introspection is probably not failing due to a timeout. Can you check the status of the introspection job as described here?: https://oracle.github.io/weblogic-kubernetes-operator/managing-domains/debugging/#check-the-introspector-job.
Likely, we will find that the introspection job is failing for some reason that we can assist with.