ToDo List

An example application containing a WebLogic component

Before you begin

  • Install Verrazzano by following the installation instructions.
  • To download the example image, you must first accept the license agreement.
    • In a browser, navigate to https://container-registry.oracle.com/ and sign in.
    • Search for example-todo and select the image name in the results.
    • Click Continue, then read and accept the license agreement.

NOTE: The ToDo List example application deployment files are contained in the Verrazzano project located at <VERRAZZANO_HOME>/examples/todo-list, where <VERRAZZANO_HOME> is the root of the Verrazzano project.

All files and paths in this document are relative to <VERRAZZANO_HOME>/examples/todo-list.

Deploy the ToDo List application

ToDo List is an example application containing a WebLogic component. For more information and the source code of this application, see the Verrazzano Examples.

  1. Create a namespace for the ToDo List example and add a label identifying the namespace as managed by Verrazzano.

    $ kubectl create namespace todo-list
    $ kubectl label namespace todo-list verrazzano-managed=true istio-injection=enabled
    
  2. Create a docker-registry secret to enable pulling the ToDo List example image from the registry.

    $ kubectl create secret docker-registry tododomain-repo-credentials \
            --docker-server=container-registry.oracle.com \
            --docker-username=YOUR_REGISTRY_USERNAME \
            --docker-password=YOUR_REGISTRY_PASSWORD \
            --docker-email=YOUR_REGISTRY_EMAIL \
            -n todo-list
    

    Replace YOUR_REGISTRY_USERNAME, YOUR_REGISTRY_PASSWORD, and YOUR_REGISTRY_EMAIL with the values you use to access the registry.

  3. Create and label secrets for the WebLogic domain:

    
    # Replace the values of the WLS_USERNAME and WLS_PASSWORD environment variables as appropriate.
    $ export WLS_USERNAME=<username>
    $ export WLS_PASSWORD=<password>
    $ kubectl create secret generic tododomain-weblogic-credentials \
        --from-literal=password=$WLS_PASSWORD \
        --from-literal=username=$WLS_USERNAME \
        -n todo-list
    
    
    $ kubectl create secret generic tododomain-jdbc-tododb \
        --from-literal=username=$WLS_USERNAME \
        --from-literal=password=$WLS_PASSWORD \
        -n todo-list
    
    $ kubectl -n todo-list label secret tododomain-jdbc-tododb weblogic.domainUID=tododomain
    

    Note that the ToDo List example application is preconfigured to use specific secret names. For the source code of this application, see the Verrazzano Examples.

  4. To deploy the application, apply the example resources.

    $ kubectl apply -f https://raw.githubusercontent.com/verrazzano/verrazzano/v1.0.1/examples/todo-list/todo-list-components.yaml
    $ kubectl apply -f https://raw.githubusercontent.com/verrazzano/verrazzano/v1.0.1/examples/todo-list/todo-list-application.yaml
    
  5. Wait for the ToDo List application to be ready. You can monitor its progress by listing pods and inspecting the output, or you can use the kubectl wait command. You may need to repeat the kubectl wait command several times before it is successful. The tododomain-adminserver pod may take a while to be created and Ready.

    $ kubectl get pods -n todo-list
    
    # -or- #
    
    $ kubectl wait pod \
       --for=condition=Ready tododomain-adminserver \
       -n todo-list
    
  6. Get the generated host name for the application.

    $ HOST=$(kubectl get gateway \
         -n todo-list \
         -o jsonpath='{.items[0].spec.servers[0].hosts[0]}')
    $ echo $HOST
    todo-appconf.todo-list.10.11.12.13.nip.io
    
  7. Get the EXTERNAL_IP address of the istio-ingressgateway service.

    $ ADDRESS=$(kubectl get service \
         -n istio-system istio-ingressgateway \
         -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
    $ echo $ADDRESS
    10.11.12.13
    
  8. Access the ToDo List application:

    • Using the command line

      $ curl -sk \
         https://${HOST}/todo/ \
         --resolve ${HOST}:443:${ADDRESS}
      

      If you are using nip.io, then you do not need to include --resolve.

    • Local testing with a browser

      Temporarily, modify the /etc/hosts file (on Mac or Linux) or c:\Windows\System32\Drivers\etc\hosts file (on Windows 10), to add an entry mapping the host name to the ingress gateway’s EXTERNAL-IP address. For example:

      10.11.12.13 todo.example.com
      

      Then, you can access the application in a browser at https://todo.example.com/todo.

    • Using your own DNS name

      • Point your own DNS name to the ingress gateway’s EXTERNAL-IP address.

      • In this case, you would need to have edited the todo-list-application.yaml file to use the appropriate value under the hosts section (such as yourhost.your.domain), before deploying the ToDo List application.

      • Then, you can use a browser to access the application at https://<yourhost.your.domain>/todo/.

        Accessing the application in a browser opens the page, “Derek’s ToDo List”, with an edit field and an Add button that lets you add tasks.

  9. A variety of endpoints associated with the deployed ToDo List application, are available to further explore the logs, metrics, and such. Accessing them may require the following:

    • Run this command to get the password that was generated for the telemetry components:

      $ kubectl get secret \
          --namespace verrazzano-system verrazzano \
          -o jsonpath='{.data.password}' | base64 \
          --decode; echo
      

      The associated user name is verrazzano.

    • You will have to accept the certificates associated with the endpoints.

    You can retrieve the list of available ingresses with following command:

    $ kubectl get ingress -n verrazzano-system
    NAME                         CLASS    HOSTS                                                     ADDRESS           PORTS     AGE
    verrazzano-ingress           <none>   verrazzano.default.10.11.12.13.nip.io                 10.11.12.13   80, 443   7d2h
    vmi-system-es-ingest         <none>   elasticsearch.vmi.system.default.10.11.12.13.nip.io   10.11.12.13   80, 443   7d2h
    vmi-system-grafana           <none>   grafana.vmi.system.default.10.11.12.13.nip.io         10.11.12.13   80, 443   7d2h
    vmi-system-kibana            <none>   kibana.vmi.system.default.10.11.12.13.nip.io          10.11.12.13   80, 443   7d2h
    vmi-system-prometheus        <none>   prometheus.vmi.system.default.10.11.12.13.nip.io      10.11.12.13   80, 443   7d2h
    

    Using the ingress host information, some of the endpoints available are:

    Description Address Credentials
    Kibana https://[vmi-system-kibana ingress host] verrazzano/telemetry-password
    Grafana https://[vmi-system-grafana ingress host] verrazzano/telemetry-password
    Prometheus https://[vmi-system-prometheus ingress host] verrazzano/telemetry-password

Access the WebLogic Server Administration Console

To access the Console from the machine where you are running kubectl:

  1. Set up port forwarding.

    $ kubectl port-forward pods/tododomain-adminserver 7001:7001 -n todo-list
    

    NOTE: If you are using the OCI Cloud Shell to run kubectl, in order to access the Console using port forwarding, you will need to run kubectl on another machine.

  2. Access the WebLogic Server Administration Console from your browser.

    http://localhost:7001/console
    

Troubleshooting

  1. Verify that the application configuration, domain, and ingress trait all exist.

    $ kubectl get ApplicationConfiguration -n todo-list
    NAME           AGE
    todo-appconf   19h
    
    $ kubectl get Domain -n todo-list
    NAME          AGE
    todo-domain   19h
    
    $ kubectl get IngressTrait -n todo-list
    NAME                           AGE
    todo-domain-trait-7cbd798c96   19h
    
  2. Verify that the WebLogic Administration Server and MySQL pods have been created and are running. Note that this will take several minutes.

    $ kubectl get pods -n todo-list
    
    NAME                     READY   STATUS    RESTARTS   AGE
    mysql-5c75c8b7f-vlhck    1/1     Running   0          19h
    tododomain-adminserver   2/2     Running   0          19h