Ensure that you have gathered the necessary information about your Kubernetes cluster in your tenancy and have the necessary privileges in place to connect your cluster. Oracle recommends that a user with Administrator privileges performs this operation. After a successful connect, the logs, metrics, and object information from related Kubernetes components, and compute nodes are collected from this cluster.

1. Open the navigation menu and click Observability & Management. Under Logging Analytics, click Solutions, and click Kubernetes. The Kubernetes Monitoring Solution page opens.

2. In the Kubernetes Monitoring Solution page, click Connect clusters. The Add Data wizard opens. Here, the Monitor Kubernetes section is already expanded. Click Oracle OKE. The Configure OKE environment monitoring page opens.

3. Select the OKE cluster that you want to connect with Oracle Logging Analytics by clicking on the corresponding row in the table of clusters. Use the details in the table to identify the right OKE cluster. Click Next.

4. From the menu, select the compartment to store the telemetry data and related monitoring resources.

5. Optionally, the required Policies and dynamic groups are created. You can disable the check box if you have already created them. For the required policies, see Allow All Kubernetes Solution Operations.

6. Optionally, the metrics server is installed for the collection of usage metrics. You can disable the check box if you have already installed it.

7. Select the Solution deployment option:

   • Enable the above clusters automatically: Select this option to allow Oracle Logging Analytics to automatically create all the required resources.

     The automatic log collection configuration creates or updates the following resources:

     • IAM Policy and Dynamic Groups
     • Oracle Logging Analytics Log Groups and Entities
     • Management Agent key
     • Metric namespace
     • Management Agent configuration
     • Fluentd configuration
     • Kubernetes manifests and helm chart
   • I will manually deploy the above clusters: Select this option for Oracle Logging Analytics to create all the Oracle Cloud Infrastructure resources and for providing you the ability to manage the deployment of Fluentd and other configuration through Helm / Kubernetes manifests into your cluster. However, the installation instructions will be provided at the end of the connect workflow. This option allows you to customize the default configuration and other collection parameters used in automatic deployment.

8. Click Configure log collection to confirm the configuration that you specified.

   The Oracle Cloud Infrastructure resources are now created.

9. If you select the manual deployment option for the solution, then follow the installation instructions provided at the end of the connect workflow for Helm chart deployment.

With this the configuration is complete to collect the data from your Kubernetes cluster. Go to the Kubernetes monitoring solution page, and wait for a few minutes for the data collection to complete. When the data collection is in progress, the Latest Telemetry of the cluster is Unknown. You can view the solution after this status changes.

The telemetry data collected from your Kubernetes cluster is presented in multiple views to help you obtain insights into the environment and its performance.

To view the solution for your Kubernetes cluster:

1. Open the navigation menu and click Observability & Management. Under Logging Analytics, click Solutions, and click Kubernetes. The Kubernetes Monitoring Solution page opens.

2. In the Kubernetes Monitoring Solution page, click the name of the cluster that you want to monitor and analyze. The solution for the selected cluster opens with the default Cluster view.

Now explore the solution and the various views available to traverse the tiers of the topology and obtain details at each level in Cluster view, Workload view, Node view, and Pod view. Note that the filter context is sustained between the different views.

An example Kubernetes solution pod view:

The sections Time selector, Events, Left Panel Summary, and Right Panel Widgets are the same as in the cluster view. The Namespace Filter, Workloads Filter, and Nodes Filter context are retained from the Nodes view. The Pods section displays the pods and their status based on the filter selection. Additionally, the view includes the Pods status. In this section, you can expand each pod to view the detailed information like status, node, namespace, pod IP, controller, controller kind, and scheduler. You can also selectively view the details of the pods based on their current status like running, failed, succeeded, and pending.

Create a dynamic group to allow collection of logs, metrics, and object information:

ALL {instance.compartment.id = '<OKE_COMPARTMENT_OCID>'}
ALL {resource.type='managementagent', resource.compartment.id='<TELEMETRY_COMPARTMENT_OCID>'}

Create policies to allow the dynamic group to perform the data collection operations:

allow dynamic-group <dynamic_group_name> to {LOG_ANALYTICS_LOG_GROUP_UPLOAD_LOGS} in compartment id <TELEMETRY_COMPARTMENT_OCID>
allow dynamic-group <dynamic_group_name> to use METRICS in compartment id <TELEMETRY_COMPARTMENT_OCID> WHERE target.metrics.namespace = 'mgmtagent_kubernetes_metrics'
allow dynamic-group <dynamic_group_name> to {LOG_ANALYTICS_DISCOVERY_UPLOAD} in tenancy

For information about dynamic groups and IAM policies, see OCI Documentation: Managing Dynamic Groups and OCI Documentation: Managing Policies.