Requirements for Running CloudOps for Kubernetes

The following section lists requirements to consider when evaluating and planning to use CloudOps for Kubernetes.

AWS Account

Each installation of CloudOps for Kubernetes requires a separate AWS account. We strongly recommend using only clean and empty AWS accounts with CloudOps for Kubernetes. The tooling is not designed or tested to work in AWS accounts that contain existing resources and conflicts may occur.

AWS Regions

CloudOps for Kubernetes is known and expected to work in the AWS regions operated by Amazon and that offer the required AWS services. AWS regions operated by entities other than Amazon are not tested and may be incompatible.

AWS Services

CloudOps for Kubernetes requires an AWS region that offers the following AWS services:

• Virtual Private Cloud (VPC)
• Identity and Access Management (IAM)
• Elastic Kubernetes Service (EKS)
• Simple Storage Service (S3)
• DynamoDB Database
• Route53
• EC2 Instances
• Network Load Balancers (NLBs)
• Elastic Block Store (EBS)
• Elastic Container Registry (ECR)
• Security Groups
• Relational Database Service (RDS) Aurora MySQL version 2
• Elastic File System (EFS)
• Key Management Service (KMS)

CloudOps for Kubernetes also includes support for the following optional AWS services:

• Simple Email Service (SES)
• Simple Queue Service (SQS)

The Amazon Regional Services tool provided in the AWS documentation may be helpful while investigating AWS region options.

Connectivity to Third-Party Services

Self Managed Commerce and CloudOps for Kubernetes both leverage open-source and community tools and services. Various CloudOps for Kubernetes processes, including code and container builds, connect to services on the Internet to securely access these trusted and tested dependencies. Ensure that your AWS account has open Internet egress to allow these processes to connect to the third-party services on the Internet.

Knowledge Requirements

Knowledge in the below technologies is required to configure and operate CloudOps for Kubernetes.

For your initial Experience

Getting started with CloudOps for Kubernetes requires the ability to use the following tools and technologies:

• Installing software tools
• Using a command-line interface
• Setting up Git source code projects
• Cloning Git repositories using SSH keys
• Creating and managing SSH key pairs
• Editing text files in a text editor
• The following AWS services:
  • Route53

To Operate CloudOps for Kubernetes

The basic operation of CloudOps for Kubernetes requires additional knowledge in the following tools and technologies:

• Self Managed Commerce
• Docker and Linux Containers
• Building and testing Java projects with Maven
• Building container images
• Jenkins Pipelines
• Bash scripting
• Git branching and Docker tagging concepts
• Jenkins administration and management
• The following AWS services:
  • The AWS Command Line Interface (awscli)
  • Virtual Private Cloud (VPC)
  • Elastic Kubernetes Service (EKS)
  • EC2 Instances
  • Elastic Container Registry (ECR)
  • Relational Database Service (RDS) Aurora MySQL version 2
• Kubernetes, including the following services:
  • The kubectl command-line tool
  • Kubernetes services, deployments, pods and replicas
• Terraform, including
  • How Terraform manages infrastructure state

Advanced operation of CloudOps for Kubernetes requires additional knowledge in the following tools and technologies:

• Kubernetes, including the following services:
  • HAProxy Ingress Controller
  • Cluster Autoscaler
  • Pod Autoscaler
  • Cert-manager
• AWS services including:
  • Network Load Balancers (NLBs)
  • Elastic Container Registry (ECR)
  • Security Groups
  • Relational Database Service (RDS)
  • Elastic Block Store (EBS)
  • Elastic File System (EFS)
  • Key Management Service (KMS)
  • Simple Storage Service (S3)
  • DynamoDB Database
• Nexus artifact repository management
• Updating and merging code branches using Git
• Terraform, including
  • How to read Terraform files