Can't access weblogic Admin, and the weblogic domain with pvc & pv it seems to failt in a step

[dbibiamine-gh]

Hello,

While deploying a weblogic domain with a pv & pvc im not having the good result and i can't access my weblogic Admin Server :

$ kubectl describe domain adbdomain -n adbdomain
Name:         adbdomain
Namespace:    adbdomain
Labels:       weblogic.domainUID=adbdomain
Annotations:  <none>
API Version:  weblogic.oracle/v9
Kind:         Domain
Metadata:
  Creation Timestamp:  2023-03-07T16:27:15Z
  Generation:          1
  Managed Fields:
    API Version:  weblogic.oracle/v8
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
        f:labels:
          .:
          f:weblogic.domainUID:
      f:spec:
        .:
        f:clusters:
        f:dataHome:
        f:domainHome:
        f:domainHomeSourceType:
        f:httpAccessLogInLogHome:
        f:image:
        f:imagePullPolicy:
        f:includeServerOutInPodLog:
        f:logHome:
        f:logHomeEnabled:
        f:serverPod:
          .:
          f:env:
          f:resources:
            .:
            f:requests:
              .:
              f:cpu:
              f:memory:
          f:volumeMounts:
          f:volumes:
        f:serverStartPolicy:
        f:webLogicCredentialsSecret:
          .:
          f:name:
    Manager:         kubectl-client-side-apply
    Operation:       Update
    Time:            2023-03-07T16:27:15Z
  Resource Version:  3539952
  UID:               3d9919ba-35a2-4136-b2ad-26e168c0e381
Spec:
  Clusters:
    Name:                           adbdomain-cluster-1
  Data Home:
  Domain Home:                      /shared/domains/adbdomain
  Domain Home Source Type:          PersistentVolume
  Failure Retry Interval Seconds:   120
  Failure Retry Limit Minutes:      1440
  Http Access Log In Log Home:      true
  Image:                            container-registry.oracle.com/middleware/weblogic:12.2.1.4
  Image Pull Policy:                IfNotPresent
  Include Server Out In Pod Log:    true
  Log Home:                         /shared/logs/adbdomain
  Log Home Enabled:                 true
  Log Home Layout:                  Flat
  Max Cluster Concurrent Shutdown:  1
  Max Cluster Concurrent Startup:   0
  Max Cluster Unavailable:          1
  Replicas:                         0
  Server Pod:
    Env:
      Name:   JAVA_OPTIONS
      Value:  -Dweblogic.StdoutDebugEnabled=false
      Name:   USER_MEM_ARGS
      Value:  -Djava.security.egd=file:/dev/./urandom -Xms256m -Xmx512m
    Resources:
      Requests:
        Cpu:     250m
        Memory:  768Mi
    Volume Mounts:
      Mount Path:  /shared
      Name:        weblogic-domain-storage-volume
    Volumes:
      Name:  weblogic-domain-storage-volume
      Persistent Volume Claim:
        Claim Name:     adbdomain-weblogic-sample-pvc
  Server Start Policy:  IfNeeded
  Web Logic Credentials Secret:
    Name:  adbdomain-weblogic-credentials
Events:    <none>

$ kubectl get all -n adbdomain
NAME                                                    READY   STATUS      RESTARTS   AGE
pod/adbdomain-create-weblogic-sample-domain-job-fw2bv   0/1     Completed   0          22h

NAME                                                    COMPLETIONS   DURATION   AGE
job.batch/adbdomain-create-weblogic-sample-domain-job   1/1           61s        22h

NAME                               AGE
domain.weblogic.oracle/adbdomain   22h

NAME                                          AGE
cluster.weblogic.oracle/adbdomain-cluster-1   22h

[Tom Barnes]

There is no 'status' in the domain resource. This is an indication that the operator hasn't been deployed or that it has not been configured to monitor the 'adbdomain' namespace.

See https://oracle.github.io/weblogic-kubernetes-operator/managing-operators/common-mistakes/#forgetting-to-configure-the-operator-to-monitor-a-namespace

[dbibiamine-gh]

There is no 'status' in the domain resource. This is an indication that the operator hasn't been deployed or that it has not been configured to monitor the 'adbdomain' namespace.

See https://oracle.github.io/weblogic-kubernetes-operator/managing-operators/common-mistakes/#forgetting-to-configure-the-operator-to-monitor-a-namespace

i have tried with the an other example and still can not access, here is the status of my pods and services on differenet namespaces

[Ryan Eberhard]

The operator can be installed to watch or not watch certain namespaces to accommodate different business requirements. The default behavior for the 4.0 operator is to only monitor namespaces with a certain label. Can you please give us the output of this command:

helm get values weblogic-operator -n weblogic-operator

Assuming that you've used the default installation (the above command will verify that by showing any user-supplied values) then you need to enable monitoring for your "adbdomain" by executing:

kubectl label ns adbdomain weblogic-operator=enabled

[Robert Patrick]

@dbibiamine-gh I assume this issue is resolved due to the lack of activity.