Skip to content

KOP Blueprints - Default Upstream

Default Upstream Cluster Blueprint

The default-upstream blueprint is the baseline for any Upstream Kubernetes cluster to deploy on both public cloud and on-premises environments, and is version controlled.

In the example below, the upstream cluster is based on a default upstream blueprint. Note the following details

  • Name of Blueprint: default-upstream in this example
  • The version/timestamp of the default-upstream blueprint
  • Blueprint Sync Status

Default Cluster Blueprint

Available Addons

The table below shows the addons that are enabled in the default-upstream blueprint

Category Addon
k8s Management Operator YES
Managed Storage YES
Monitoring & Alerting NO
Log Aggregation NO
Ingress Controller NO
VM Operator NO

View Default Upstream Blueprints

As an Admin, login into the Web Console

  • Select Project
  • Select Infrastructure -> Blueprints
  • Select the "Default Blueprints" tab

In the example below, the dashboard shows 15 versions of the default-upstream blueprint over the entire lifecycle and two clusters in the Project based on the default-upstream blueprint

View Default Blueprint

Clicking on the clusters link will display the status of the default-upstream blueprint on the list of clusters. An illustrative example is shown below.

Clusters with Default Blueprint