ic_agile_128ic_banknote_smile_128ic_business_128ic_business_128ic_checkmark_128ic_client_team_manager_128ic_code_file_128ic_code_files_128ic_corporate_cloud_platforms_128ic_crossplatform_apps_128ic_dedicated_team_128ic_developer_128ic_development_team_128ic_enterprise_128ic_faster_timeframe_128ic_fixed_price_128ic_graph_down_128ic_graph_down_128ic_information_finder_128ic_junior_developer_128ic_managed_team_128ic_message_128ic_mobile_app_startups_128ic_mobile_development_128ic_mobile_development_up_128ic_mobile_devices_128ic_multiplatform_128ic_multiplatform_white_128ic_pricetag_128ic_project_checklist_128ic_project_management_128ic_project_management_team_128ic_research_and_development_team_128ic_scalable_team_128ic_senior_developer_128ic_smaller_codebase_128ic_smaller_price_128ic_startup_128ic_team_manager_128ic_three_times_faster_128Arrow_Dropdownic_001_google+_16ic_002_xing_16Group 2ic_003_facebook_16ic_004_linkedIn_16Groupic_005_message_16ic_006_upload_16ic_007_remove_16ic_008_email_16ic_009_attachment_16ic_010_file_16ic_011_name_16ic_012_arrow_left_16ic_013_arrow_right_16ic_014_arrow_down_16ic_015_arrow_up_16ic_016_dropdown_arrow_down_16ic_016_dropdown_arrow_leftic_016_dropdown_arrow_rightic_017_K&C_dropdown_arrow_up_16ic_018_language_16ic_019_Quote_16ic_020_+_16ic_021_=_16ic_022_phone_16ic_023_twitter_16ic_024_position_16ic_025_company_16ic_026_search_16ic_027_mobile_16ic_028_fax_16ic_029_location_16ic_030_enlarge_16ic_031_downscale_16ic_032_contactic_download_normal_16pxic_033_skype_16ic_006_download_16 copyK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxic_Interest_based_64ic_acrivate_card_64ic_api_client_64ic_application_architecture_64ic_application_architecture_ white_64ic_application_development_user_64ic_arrow_down_64ic_automated_backups_64ic_automated_infrastructure_provisioning_64ic_automated_infrastructure_provisioning_white_64ic_automated_storage_64ic_automated_storage_64ic_automation_64ic_avaliability_across_the_world_64ic_avaliability_across_the_world_white_64ic_brackets_64ic_brackets_64ic_build_64ic_build_64ic_business_64ic_business_partnership_64ic_business_partnership_white_64ic_business_64ic_calculator_64ic_calendar_64ic_car_rent_64ic_card_renewal_64ic_chat_64ic_chat_bubbles_64ic_chat_bubbles_64ic_chat_white_64ic_checklist_64ic_checkmark_64ic_checkmark_white_64ic_clock_64ic_clock_white_64ic_cloud_media_64ic_cluster_64ic_cluster_white_64ic_code_base_optimization_64ic_coding_64ic_coding_white_64ic_commenting_widget_64ic_commenting_widget_64ic_containers_64ic_containers_white_64ic_continious_64ic_continious_delivery_64ic_continious_delivery_white_64ic_continious_release_64ic_continious_release_white_64ic_continious_white_64ic_cost_saving_64ic_cost_saving_white_64ic_cpu_load_64ic_credit_card_64ic_crossplatform_app_development_64ic_crossplatform_app_development_white_64ic_custom_crm_64ic_custom_crm_64ic_independence_consulring_64ic_database_calls_64ic_database_calls_white_64ic_dedicated_teams_64ic_dedicated_teams_64ic_desktop_application_user_64ic_desktop_application_user_64ic_desktop_code_64ic_desktop_code_white_64ic_developer_64ic_developer_white_64ic_development_64ic_devops_64ic_documents_64ic_documents_graph_64ic_documents_graph_white_64ic_documents_white_64ic_download_presentation_64ic_education_64ic_email_open_64ic_email_open_white_64ic_environment_healthcheckic_euro_64ic_euro_white_64ic_failure_solved_64ic_globe_outlines_64ic_good_quality_64ic_high_load_websites_64ic_high_load_websites_white_64ic_hotel_booking_64ic_inability_64ic_inability_white_64ic_increase_64ic_increasing_team_64ic_independence_64ic_integration_64ic_it_outsourcing_64ic_it_outsourcing_64ic_knowledge_sharing_64ic_mobile_devices_64ic_laptop_user_64ic_laptop_user_64ic_launch_64ic_launch_white_64ic_learning_64ic_learning_two_white_64ic_lighthouse_64ic_link_64ic_load_balancer_64ic_load_balancer_64ic_load_card_64ic_lock_64ic_lock_white_64ic_low_cost_64ic_low_load_websites_64ic_maintenance_tools_64ic_maintenance_tools_white_64ic_media_player_64ic_messaging_platforms_64ic_microservice_architecture_64ic_microservices_64ic_microservices_64ic_mobile_app_64ic_mobile_content_64ic_mobile_development_64ic_mobile_development_white_64ic_mobile_devices_64ic_mobile_devices_white_64ic_mobile_payments_64ic_mobile_social_media_applications_64ic_mobile_workflows_64ic_money_transfers_64ic_multimedia_sharing_64ic_multimedia_sharing_white_64ic_my_garage_64ic_no_access_64ic_no_access_white_64ic_no_oldschool_64ic_online_marketplaces_64ic_online_trading_64ic_online_trading_64ic_pair_device_64ic_parallels_64ic_parallels_white_64ic_passcode_64ic_performance_64ic_performance_issues_64ic_performance_issues_white_64ic_performance_white_64ic_plane_64ic_plane_white_64ic_plus_64ic_plus_64ic_pricetags_64ic_product_64ic_product_search_64ic_product_white_64ic_productivity_tools_64ic_productivity_tools_64ic_project_delivery_64ic_project_delivery_white_64ic_project_management_64ic_project_management_collaboration_64ic_project_management_team_64ic_project_risks_reduced_64ic_quality_mark_64ic_quality_mark_white_64ic_question_64ic_react_native_64ic_response_time_64ic_response_time_white_64ic_rest_api_64ic_retail_64ic_transparency_consulting_64ic_scale_up_64ic_scale_up_white_64ic_self_healing_64ic_self_healing_64 copyic_send_money_64ic_server_64ic_server_white_64ic_shopping_64ic_sleep_mode_64ic_small_is_beautiful_64ic_smaller_price_64ic_social_benefits_64ic_social_connections_64ic_socket_64ic_spare_parts_for_cars_64ic_spare_parts_for_cars_white_64ic_speedometer_64ic_performance_consulting_64ic_speedometer_white_64ic_startup_64ic_target_64ic_team_64ic_testing_64ic_testing_checklist_64ic_testing_checklist_64ic_testing_white_64ic_three_times_faster_64ic_touch_64ic_touch_id_64ic_touch_white_64ic_transparency_64ic_ui_design_desktop_64ic_ui_design_mobile_64ic_ui_design_mobile_white_64ic_umbrella_64ic_umbrella_white_64ic_up_and_down_scaling_64ic_up_and_down_scaling_64ic_users_64ic_users_white_64ic_ux_design_64ic_ux_design_desktop_64ic_ux_design_white_64ic_vehicle_64ic_web_based_search_64ic_web_based_search_white_64ic_web_browser_code_64ic_web_browser_developer_mode_64ic_web_browser_user_64ic_web_development_64ic_web_development_white_64ic_web_portals_64ic_web_portals_64ic_web_user_64ic_web_user_white64ic_workflow_64ic_workflow_steps_64ic_workflow_steps_white_64ic_workflow_white_64ic_working_environment_64

How to setup Kubernetes cluster on AWS

Running an application in the cloud without the proper tools to manage it and improve its functionality can be tricky. That is why when deploying a customer’s application you want to have the means for fast deployment, features roll out, resource management, resilience and automation of certain operations. Kubernetes is an open-source platform that gives you a set of tools to do just that. 


Today we will run Kubernetes multi-master cluster on AWS and deploy a simple application. We’ll use kops (Kubernetes Operations), which is a utility for managing Kubernetes clusters. In our opinion, currently kops is the best tool for deploying Kubernetes clusters in Amazon Web Services
.

1. Creating a zone in Route53:


aws route53 create-hosted-zone –name example.com

2. Creating an S3 bucket to store the cluster configuration:


aws s3api create-bucket   --bucket kubernetes-cluster  --region eu-west-1

We include versioning:

aws s3api put-bucket-versioning --bucket kubernetes-cluster  --versioning-configuration Status=Enabled

3. Creating our new cluster 

export KOPS_STATE_STORE=s3://kubernetes-cluster
 
kops create cluster \
--name example.com \
--master-zones eu-west-1a,eu-west-1b,eu-west-1c \
--zones eu-west-1a,eu-west-1b,eu-west-1c \
--state s3://kubernetes-cluster \
--node-count 3 \
--yes \

name                          cluster name should be identical to zone name

master-zones            zones where masters will be launched

zones                          zones where the nodes will be located 

state                            configuration storage bucket 

node-count                a number of nodes in the cluster

yes                               applies changes 

Checking availability of the cluster:

kops validate cluster

The output:

Using cluster from kubectl context: example.com
 
Validating cluster example.com
 
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	m3.medium	1	1	eu-west-1a
master-eu-west-1b	Master	m3.medium	1	1	eu-west-1b
master-eu-west-1c	Master	m3.medium	1	1	eu-west-1c
nodes			Node	t2.medium	3	3	eu-west-1a,eu-west-1b,eu-west-1c
 
NODE STATUS
NAME						ROLE	READY
ip-174-21-107-10.eu-west-1.compute.internal	node	True
ip-174-21-113-20.eu-west-1.compute.internal	master	True
ip-174-21-38-94.eu-west-1.compute.internal	node	True
ip-174-21-53-131.eu-west-1.compute.internal	node	True
ip-174-21-61-2.eu-west-1.compute.internal	master	True
ip-174-21-67-114.eu-west-1.compute.internal	master	True
Your cluster example.com is ready

Kops also creates settings for kubectl. We can also do:

kubectl get node

The output:

ip-174-21-107-10.eu-west-1.compute.internal   Ready     11d       v1.7.2
ip-174-21-113-20.eu-west-1.compute.internal   Ready     11d       v1.7.2
ip-174-21-38-94.eu-west-1.compute.internal    Ready     11d       v1.7.2

To edit nodes configuration, we do this:

kops edit ig nodes

Editing the file:

apiVersion: kops/v1alpha2
kind: InstanceGroup
metadata:
  creationTimestamp: 2017-10-02T23:10:46Z
  labels:
    kops.k8s.io/cluster: example.com
  name: nodes
spec:
  image: kope.io/k8s-1.7-debian-jessie-amd64-hvm-ebs-2017-07-28
  machineType: t2.medium -> t2.xlarge
  maxSize: 3 -> 4
  minSize: 3 -> 4
  role: Node
  subnets:
  - eu-west-1a
  - eu-west-1b
  - eu-west-1c

Saving the file and applying the configuration:

kops rolling-update cluster –yes

Checking the state of the cluster:

kops validate cluster

The output:

nodes	Node  t2.xlarge	  4	4    eu-west-1a,eu-west-1b,eu-west-1c

For convenience, let’s deploy a dashboard:

kubectl create -f https://raw.githubusercontent.com/kubernetes/kops/master/addons/kubernetes-dashboard/v1.6.3.yaml

Dashboard will be available at:

https://api.example.com/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/#!/pod?namespace=default


Now we will deploy a simple web application, with a setup for balancer with ssl and a domain name



To associate Kubernetes with Route53, we’ll need to deploy pod:


kubectl apply -f https://raw.githubusercontent.com/kubernetes/kops/master/addons/route53-mapper/v1.3.0.yml

In the IAM role, we’ll need to find the names of the nodes and add policy:


" Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "route53:ListHostedZonesByName",
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": "elasticloadbalancing:DescribeLoadBalancers",
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": "route53:ChangeResourceRecordSets",
            "Resource": "*"
        }
    ]
}

Writing a yaml file for Deployments:

apiVersion: apps/v1beta1
kind: Deployment
metadata:
  name: project-ci
spec:
  replicas: 2
  template:
    metadata:
      labels:
        projectenv: ci
    spec:
      containers:
        - name: project
          image: ecr.eu-west-1.amazonaws.com/project
          env:
           - name: DEPLOYMENT_ENV
              value: "ci"
            - name: FILEBEAT_ENABLE
              value: "yes"
          ports:
            - containerPort: 80

Now creating a yaml file for Service:

kind: Service
apiVersion: v1
metadata:
  annotations:
    domainName: "projectci.example.com."
    service.beta.kubernetes.io/aws-load-balancer-ssl-cert: "arn:aws:acm:us-west-1:659153740712:certificate/xxxxxxxx"
    service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "443"
    service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http
  name: projectci
  labels:
    projectenv: ci
    dns: route53
spec:
  selector:
    projectenv: ci
  ports:
    - name: "https"
      protocol: TCP
      port: 443
  type: LoadBalancer

After deployment, we'll see our application at https://projectci.example.com 


And in the AWS console we’ll see the newly created balancer:

That's it! 

SHARE WITH FRIENDS
You might find this interesting
Case Study
Bosch Classic Cars - Digital Engagement Platform for 19K Vintage Car Owners
Case Study
Liferay Portal Performance Tuning Services for a Major Online Gaming Software Supplier
SUCCESS-STORY
Reference: Major producer of auto electronics and spare parts
Blog post
How to Make Your Web Solution Rock: 7 Areas to Check
Blogpost
How to Motivate Your Dedicated Team to Work with Legacy Projects
Blogpost
SEO Tips & Tricks for Single Page Web Applications
Success Story
Drivelog.de — Web Marketplace for Car Owners and Service Providers
blog post
Docker: Virtualize Your Development Environment Right
eBook
How to Secure Web Product Development — FREE eBook
blog post
When Microservices Help Make Future-Ready Products
Case Study
Portal Performance Tuning For Major German Travel Agency
blog post
How to Build a Rancher & Docker Based Cloud
case study
Micro-service Architecture for New AngularJS Application - Case Study
blog post
How We Use Ansіble for Configuration of Our Environments
blog post
DevOps with Puppet: Tips on Setting it up for Configuring Servers
blog post
How We Manage Our Infrastructure with Chef
Success Story
Fast and Lightweight Mobile Application based on PhoneGap/ Cordova
blog post
Centralized Logging with Logstash, Elasticsearch & Kibana
blog post
How the QA Team Tests Your Project
blog post
4 Time-Saving Ways to Test Your Cross Platform Mobile App
blog post
Plan to Succeed: 4 Tips for Building Scalable Software
ebook
Top Tools for Cost-Effective Web Development — eBook
Blogpost
How to start services on Linux
Blog Post
Scaling software solutions - how it works
Blog Post
Angular 2.0 vs Angular 1.4. What fits you best?
Blog Post
Reasons to believe in Ionic hybrid app
Blog Post
Debunking imaginary shortcomings of cross-platform frameworks
E-book
Determining Approaches to Mobile App Development
Blog Post
Technologies that Foster Digital Transformation
Blog Post
A Guidance for Keeping Your Web Development Project Within the Budget: Three Key Pillars
Blog Post
Agile and DevOps are Key Drivers of Digital Transformation
Blog Post
Dedicated Teams for Web Development: Choice Criteria to be Checked
Blog post
Cost efficient technologies
Blog Post
Angular 4 vs React – what to choose in 2017
Blog Post
A secret formula of an agile dream team
Blog post
GoLang: Features, Pros and Cons
Blog post
K&C insights: how to make your workflow work for you
Blog post
Microservices… when do we need them?
Blog post
Use case: how to build and run Docker containers with NVIDIA GPUs
Success Story
How to apply React Native while developing heavy cross-platform mobile apps
Blog post
Cloud Deployment: Overview of Options
Success Story
Reformation of Deployment Cycle for Bosch Classic Cars Portal
Blog post
Three Authentication Approaches to Keep Your Clients Safe
Blog post
Native or Hybrid Apps: A Quick Comparison
Blog post
Big Data: Why Your Business Needs it ASAP
Blog post
Setting Up: Traefik Balancer In Rancher Cloud
Blog post
White Label: A Customized Software Solution from a Business and Tech Perspective
Blog post
Installation and setting up: Nextcloud as a local network storage on CentOS7
Blog post
How a Company Can Benefit from White Label: K&C experience
Blog post
ROCKET.CHAT as an internal messaging system and helpdesk platform
Blog post
JS Frameworks: The Trendiest Frameworks You Should Know
Blog post
Angular vs. React vs. Vue – Let the Fight Start!
Blog post
Hybrid, SaaS+PaaS, IoT: Cloud Trends to Catch in 2018
Blog post
Angular 5.0.0 – A Better Version of Itself
Stay tuned!
We'll gladly share fresh blog updates and our best practices to your email.
We protect your data and will notify you on important updates only.