Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This topic describes the steps to create a Kubernetes YAML based blueprint. HyperCloud™ Platform supports deploying standard Kubernetes blueprints. Kubernetes blueprints can only be deployed if a Kubernetes cluster is deployed using HyperCloud Platform.

Anchor
_

...

Use the following steps to deploy a Kubernetes Cluster using the Microsoft Azure Kubernetes Service
Note: There must be enough resources available in the Resource Pool used for deploying the Azure Kubernetes Cluster.

  • Login to the HyperCloud™ Platform with your credentials  Click on Services Orchestration Tab  Click on Containers tab  Click on New to Launch Kubernetes Cluster Wizard
    • Enter a Name: hg-prod-aks-1
    • From the drop-down for Cloud Select Azure Kubernetes Service (AKS)
    • Type: Standard
    • Resource Pools: RP.ARM.South East Asia.<RP-Name>
    • Machine Type: Standard_D11
    • Node Count per Zone: 2
    • Select Resource group from the drop-down for e.g hg-prod-aks-rg
    • Click Save Changes
  • Click on the Cluster  Click on Timeline Tab  Click on View Execution Logs.

Note: If you run into an error stating - Operation could not be completed as it results in exceeding approved standardDFamily Cores quota. Additional details…. You may need to pick a different instance or contact your administrator who can request a quota increase

...

Use the following steps to deploy a Kubernetes Cluster using the Amazon Elastic Kubernetes Service

  • Login to the HyperCloud™ Platform with your credentials  Click on Services Orchestration Tab  Click on Containers tab  Click on New to Launch Kubernetes Cluster Wizard
    • Enter a Name: hg-prod-eks-1
    • From the Target drop-down: Select Amazon Elastic Kubernetes Service (AKS)
    • Type: High-Availability
    • Resource Pools: RP.AWS.ap-southeast-1a.<RP>, RP.AWS.ap-southeast-1b.<RP >

Note: Must have 2 AWS Resource available which are created from a different Availability Zones

    • Machine Type: c5.large
    • Node Count per Zone: 2
    • AutoScale Custer: Enabled (Default)
    • Minimum Worker per Pool: 2
    • Maximum Worker per Pool: 5
    • ROLE ARN: Select the Amazon EKS Service Role
    • Select Resource group from the drop-down for e.g hg-prod-aks-rg
    • To allow specific users to access this Cluster, Click on Users & Groups
      • Only Me: Only the creator can access this Cluster
      • Everyone: All users in this Tenant can access this Kubernetes Cluster
      • Groups & Users
        • In the users Text Box: Type the first alphabet of a username you would like to add & select the user
        • In the Groups Text Box: Type the first alphabet of a group name you would like to add and select the group.
    • Click Save Changes
  • Click on the Cluster  Click on Timeline Tab  Click on View Execution Logs

Anchor
_Toc39796591
_Toc39796591
Configuring a Managed Kubernetes Cluster

...

Note: Refer the Kubernetes Secret Overview for more details

      • Click Save to create a secret in the name space
    • To view the secret, click on the Kubernetes Namespace tab  Click on the same space which was selected to create the secret.

Configuring Kubernetes Storage Class

...

spec:
#type : NodePort (Comment this line)
type: LoadBalancer

    • Click Save Changes
  • Click on the Kubernetes Blueprint
    • Select the namespace: production
    • Click on Run

...