Table: oci_containerengine_cluster - Query OCI Container Engine Clusters using SQL

Oracle Container Engine for Kubernetes (OKE) is a fully-managed, scalable, and highly available service that you can use to deploy your containerized applications to the cloud. Use OKE when your development team wants to reliably build, deploy, and manage cloud-native applications. You specify the compute resources that your applications require, and OKE provisions and manages the underlying bare metal instances for you.

Table Usage Guide

The oci_containerengine_cluster table provides insights into Container Engine Clusters within Oracle Cloud Infrastructure (OCI). As a DevOps engineer, explore cluster-specific details through this table, including cluster options, metadata, and associated resources. Utilize it to uncover information about clusters, such as those with specific configurations, the relationships between clusters and nodes, and the verification of cluster policies.

Examples

Basic info

Analyze the lifecycle state of your OCI Container Engine clusters to understand their current operational status. This can help in identifying any clusters that may need attention or maintenance.

select
  name,
  id,
  lifecycle_state
from
  oci_containerengine_cluster;

select
  name,
  id,
  lifecycle_state
from
  oci_containerengine_cluster;

List failed container engine clusters

Explore which container engine clusters have failed to understand potential issues or disruptions in your system. This could assist in troubleshooting, maintenance, and system optimization.

select
  name,
  id,
  lifecycle_state
from
  oci_containerengine_cluster
where
  lifecycle_state = 'FAILED';

select
  name,
  id,
  lifecycle_state
from
  oci_containerengine_cluster
where
  lifecycle_state = 'FAILED';

List container engine clusters for which image policy is disabled

Explore which container engine clusters have their image policy disabled. This can help identify potential security risks, as disabling image policy may allow unauthorized images to be deployed.

select
  name,
  id,
  lifecycle_state,
  image_policy_config_enabled
from
  oci_containerengine_cluster
where
  image_policy_config_enabled = false;

select
  name,
  id,
  lifecycle_state,
  image_policy_config_enabled
from
  oci_containerengine_cluster
where
  image_policy_config_enabled = 0;

Schema for oci_containerengine_cluster

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
available_kubernetes_upgrades	jsonb		Available Kubernetes versions to which the clusters masters may be upgraded.
compartment_id	text	=	The OCID of the compartment in Tenant in which the resource is located.
endpoint_config	jsonb		The network configuration for access to the Cluster control plane.
endpoints	jsonb		Endpoints served up by the cluster masters.
id	text	=	The OCID of the cluster.
image_policy_config_enabled	boolean		Whether the image verification policy is enabled. Defaults to false. If set to true, the images will be verified against the policy at runtime.
kms_key_id	text		The OCID of the KMS key to be used as the master encryption key for Kubernetes secret encryption.
kubernetes_version	text		The version of Kubernetes running on the cluster masters.
lifecycle_details	text		Additional information about the current 'lifecycleState'.
lifecycle_state	text	=	The state of the cluster masters.
metadata	jsonb		Metadata about the cluster.
name	text	=	A user-friendly name. It does not have to be unique, and it is changeable.
options	jsonb		Optional attributes for the cluster.
region	text		The OCI region in which the resource is located.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
tenant_id	text	=, !=, ~~, ~~, !~~, !~~	The OCID of the Tenant in which the resource is located.
tenant_name	text		The name of the Tenant in which the resource is located.
title	text		Title of the resource.
vcn_id	text		The OCID of the virtual cloud network (VCN) in which the cluster exists.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- oci

You can pass the configuration to the command with the --config argument:

steampipe_export_oci --config '<your_config>' oci_containerengine_cluster