Default Blueprint
All managed clusters, immaterial of type (i.e. imported or provisioned by controller) always have a blueprint associated with it.
Default Cluster Blueprint¶
The default cluster blueprint is the baseline for any managed cluster. Default blueprints are version controlled. These are remotely updated when patches or upgrades are necessary.
In the example below, the managed cluster is based on a default blueprint. Note the following details
- Name of Blueprint: "default" in this example
- The version/timestamp of the default blueprint
- Blueprint Sync Status
By Cluster Type¶
"Optimized" default blueprints are available per type of cluster to ensure that the experience is optimized for the particular environment. The table below describes what is common/shared and what is unique for the cluster type.
| Category | Upstream k8s | EKS | AKS | GKE | Imported |
|---|---|---|---|---|---|
| k8s Management Operator | YES | YES | YES | YES | YES |
| Monitoring & Alerting | YES | YES | YES | YES | YES |
| Log Aggregation | YES | YES | YES | YES | YES |
| Ingress Controller | YES | YES | YES | YES | YES |
| Instance Interruption | NO | YES | NO | NO | NO |
| Network Policy | YES | NO | NO | NO | NO |
Optional Overrides¶
Several addons (Ingress Controller, Log Aggregation, Monitoring & Alerting) in the default blueprint can be disabled. This may be necessary if the customer intends to use an alternate option or does not require it.
View Default 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 that there are >300 versions of the default blueprint over the entire lifecycle and that there two clusters in the Project based on the default blueprint
Clicking on the clusters link will display the status of the default blueprint on the list of clusters. An illustrative example is shown below.
