Skip to content

Part 1: Setup

What Will You Do

This is Part 1 of a multi-part, self-paced quick start exercise. In this part, you will configure a blueprint and deploy it to a cluster. Declarative specifications are also provided for this exercise.


Enable Network Visibility through Blueprints

Visibility into Network Traffic Flows can be enabled by simply checking a box in the Blueprint configuration.

  • Under Infrastructure, navigate to Blueprints
  • Create a new custom blueprint, provide a name for the blueprint (e.g. demo-network-policy)
  • Provide a version name (e.g. v1), navigate to the Network Visibility and Policy section and select Enable
  • Ensure that the Monitoring & Alerting managed system add-on is enabled
  • Click Save Changes

Blueprint Config

Blueprint Config


Assign the Blueprint to the cluster

  • Navigate to the Clusters page
  • Click on the gear icon next to the cluster and select Update Blueprint
  • Select the Blueprint and the version
  • Click Save and Publish

After the blueprint sync operation is complete, you can verify whether the necessary components are installed in the cluster.

Blueprint Assignment


Recap

At this point, you have the blueprint configured and deployed to the cluster.


Enable Network Visibility through Blueprints

You can alternatively enable Network Visibility by using the declarative blueprint spec YAML. For more information on automation via RCTL CLI, refer here

Important

Ensure that you update the "project: defaultproject" with the name of the project in your Org

apiVersion: infra.k8smgmt.io/v3
kind: Blueprint
metadata:
  name: demo-network-policy
  project: defaultproject
spec:
  base:
    name: default
    version: 1.18.0
  defaultAddons:
    csiSecretStoreConfig:
      providers: {}
    enableIngress: false
    enableLogging: false
    enableMonitoring: true
    enableVM: false
  drift:
    enabled: false
  networkPolicy:
    profile:
      name: default           
  opaPolicy: {}
  placement: {}  
  type: custom
  version: v1
  • Type the command below to create the new blueprint
rctl apply -f <path-to-filename>.yaml
  • Type the command below to verify creation of the blueprint
rctl get blueprint -v <blueprint_name>

Assign the Blueprint to the cluster

You can alternatively assign the blueprint to the cluster using the RCTL command.

rctl update cluster <cluster_name> -b <blueprint_name> --blueprint-version <version_name>

Type the command below to verify creation of the blueprint

rctl get cluster -v <cluster_name>

Recap

At this point, you have the blueprint configured and deployed to the cluster.