WebLogic Kubernetes Toolkit UI has a number of prerequisites that must be installed locally to fully use the WKT UI application functionality.
These include:
kubectl
- The Kubernetes client; the version should align with the Kubernetes cluster version. Required to interact with your Kubernetes cluster. For more information, see the Kubernetes Client Configuration
page in the UI.kubectl
to properly authenticate to the Kubernetes cluster. Again, see the Kubernetes
Client Configuration
page for more information about configuring kubectl
to work with your cluster.helm
- Helm version 3.9 or later. Required to install the WebLogic Kubernetes Operator and to install an ingress controller.openssl
- Used to generate an X.509 TLS certificate for ingress routes, should you ask the application
to generate one for you.The WKT UI application is built using the Electron framework and as such, we support only the platforms and versions supported by Electron; see the listing under Platform Support. For example, because of the Electron requirement for Fedora 24 or newer, we support only versions 8.0 and higher of Oracle Linux, RedHat Linux, and CentOS Linux.
In addition to these local software dependencies, you will need a Kubernetes cluster to which you can deploy your containerized WebLogic Server domain and its applications. If you do not already have a model, then you can either write one by hand using the WKT UI application or discover the model from an existing domain. Most likely, you’ll want to start with a WebLogic domain that can be used to discover the model from the domain.
For RPM-based systems, such as Oracle, RedHat, CentOS, and some others:
https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/2717454_1.html
sudo dnf install xterm
logout
ssh -X ...
xterm
For Debian-based systems, such as Ubuntu and Debian:
sudo apt install gnome-session gdm3
sudo reboot
For running the WKT UI on a remote machine without desktop environment and accessing it through X forwarding, you need to ensure X forwarding is working properly. For example,
sudo apt install xterm
logout
ssh -X ...
xterm