What is EKS and How EKS can help you?

In simple line, Amazon EKS is generally available, bringing fully-managed Kubernetes to AWS.

Amazon launched Amazon EKS in November at its re:Invent 2017 conference. Till the time this article is written, Amazon EKS is available in the US East (N. Virginia) and US West (Oregon) Regions only.

The cost of running EKS is $0.20 per hour for the EKS Control Plane, apart from EC2, EBS, and Load Balancing prices for resources that run in your account.

How does Amazon EKS work?

Amazon EKS works by provisioning (starting) and managing the Kubernetes control plane for you. At a high level, Kubernetes consists of two major components – a cluster of ‘worker nodes’ that run your containers and the control plane that manages when and where containers are started on your cluster and monitors their status.

Without Amazon EKS, you have to run both the Kubernetes control plane and the cluster of worker nodes yourself. With Amazon EKS, you provision your cluster of worker nodes using the provided Amazon Machine Image (AMI) and AWS CloudFormation script and AWS handles provisioning, scaling, and managing the Kubernetes control plane in a highly available and secure configuration. This removes a significant operational burden for running Kubernetes and allows you to focus on building your application instead of managing AWS infrastructure.

Major Features of Amazon Elastic Container Service for Kubernetes (EKS)
Amazon Elastic Container Service for Kubernetes (EKS) is a managed Kubernetes service that makes it easy for you to run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane.

  1. Availability and Scalability of Nodes – Amazon EKS automatically manages the availability and scalability of the Kubernetes control plane nodes that are responsible for
    1. Starting and stopping containers,
    2. Scheduling containers on virtual machines,
    3. Storing cluster data, and other tasks.
  2. Health check of Nodes – Amazon EKS Automatically detects and replaces unhealthy control plane nodes for each cluster.
  3. Amazon EKS Integration – Great Integration with AWS networking and security services, such as Application Load Balancers for load distribution, IAM for role based access control, and VPC for pod networking.
  4. Managed Kubernetes Control Plane – Amazon EKS provides a scalable and highly-available control plane that runs across multiple AWS availability zones.
  5. Kubernetes Masters in three Availability Zones – Amazon EKS runs the Kubernetes control plane across three Availability Zones in order to ensure high availability, and it automatically detects and replaces unhealthy masters.
  6. Amazon EKS with IAM Authentication – Amazon EKS integrates Kubernetes RBAC (the native role based access control system for Kubernetes) with IAM authentication through a collaboration with Heptio. You can assign RBAC roles directly to each IAM entity allowing you to granularly control access permissions to your Kubernetes masters.
  7. Amazon EKS with VPC Support
    Your EKS clusters run in an Amazon VPC, allowing you to use your own VPC security groups and network ACLs. No compute resources are shared with other customers. This provides you a high level of isolation and helps you use Amazon EKS to build highly secure and reliable applications.
  8. Container Interface – EKS uses the Amazon VPC CNI to allow Kubernetes pods to receive IP addresses from the VPC means The Container Network Interface for Kubernetes uses Elastic Network Interfaces to provide secondary IP addresses for Kubernetes Pods.
  9. Amazon EKS Logging
    Amazon EKS is integrated with AWS CloudTrail to provide visibility and audit history of your cluster and user activity. You can use CloudTrail to view API calls to the Amazon EKS API.
  10. Amazon EKS with EBS – Kubernetes PersistentVolumes (used for cluster storage) are implemented as Amazon Elastic Block Store (EBS) volumes.
  11. Amazon EKS with Route 53 – The External DNS project allows services in Kubernetes clusters to be accessed via Route 53 DNS records. This simplifies service discovery and supports load balancing.
  12. Amazon EKS Support – Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use all the existing plugins and tooling from the Kubernetes community.

Reference
EKS Getting Started Guide
EKS Publication
EKS FAQ

Tagged : / / / / / /

Setup Docker service to use insecure(http) registry instead of https

By default docker use https to connect to docker registry. But there can be use cases to use insecure registry. Here are the steps to use insecure registry.

In ubuntu
edit the file /etc/default/docker and update DOCKER_OPTS e.g

DOCKER_OPTS='--insecure-registry 10.84.34.155:5000'

where 10.84.34.155 is ipaddress of registry and 5000 is your port on which registry is configured.

In Centos
Edit the file /etc/docker/daemon.json e.g.

{
"insecure-registries" : ["10.84.34.155:5000"]
}

where 10.84.34.155 is ipaddress of registry and 5000 is your port on which registry is configured.

Restart docker
$ service docker restart

Tagged : / / / / /

What information does the Update Service collect?

msiexpert created the topic: What information does the Update Service collect?
What information does the Update Service collect?

applicationPackaging replied the topic: Re: What information does the Update Service collect?
The Update Service collects the product name, product version, and the language in which the product is run. This is the only information needed to provide you with the correct update for the software you have installed. For more information read our privacy statement or contact your software vendor.

Tagged :

Error 1719 The Windows Installer Service could not be accessed.

InstallerGeek created the topic: Error 1719 The Windows Installer Service could not be accessed.
My computer keeps giving me this error message when I try to upload updates and other programs. I need to know what to do to fix this. Here is the whole error message:

Error 1719 The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.

msiexpert replied the topic: Re: Error 1719 The Windows Installer Service could not be accessed.
• Do you remember making any changes to the computer recently?

This may happen if the Windows Installer files that are on your hard disk are damaged or are missing.
You install or remove a program that uses the Windows Installer Microsoft Software Installation (MSI) package file (.msi). For example, this may occur when you try to install Microsoft Office on your computer.

Method 1
First I would suggest that you check if the Windows installer service is running on the computer.

1. Go to “Start” – “Run” type “services.msc” and press on “Enter” button.

2. Double-click on the service named “Windows Installer”

3. Check the value in the “Startup type” field. If it’s currently set to “Disabled”, then this is the problem. Change it by selecting “Manual” from the drop-down box.
Make sure that the service is started and set to Manual.

Method 2
If the above step fails then unregister Windows Installer, and then reregister Windows Installer

To do this, follow these steps:

1. On the “Start” menu, click “Run”

2. In the “Open” box, type “msiexec /unreg”, and then press ENTER

3. On the “Start” menu, click “Run”

4. In the “Open” box, type “msiexec /regserver” and then press ENTER

If the above steps fail then I would suggest that you install the latest version of Windows installer on the computer, refer the below link.

www.microsoft.com/downloads/details.aspx…6f9f4&displaylang=en

msiexpert replied the topic: Re: Error 1719 The Windows Installer Service could not be accessed.
• Do you remember making any changes to the computer recently?

This may happen if the Windows Installer files that are on your hard disk are damaged or are missing.
You install or remove a program that uses the Windows Installer Microsoft Software Installation (MSI) package file (.msi). For example, this may occur when you try to install Microsoft Office on your computer.

Method 1
First I would suggest that you check if the Windows installer service is running on the computer.

1. Go to “Start” – “Run” type “services.msc” and press on “Enter” button.

2. Double-click on the service named “Windows Installer”

3. Check the value in the “Startup type” field. If it’s currently set to “Disabled”, then this is the problem. Change it by selecting “Manual” from the drop-down box.
Make sure that the service is started and set to Manual.

Method 2
If the above step fails then unregister Windows Installer, and then reregister Windows Installer

To do this, follow these steps:

1. On the “Start” menu, click “Run”

2. In the “Open” box, type “msiexec /unreg”, and then press ENTER

3. On the “Start” menu, click “Run”

4. In the “Open” box, type “msiexec /regserver” and then press ENTER

If the above steps fail then I would suggest that you install the latest version of Windows installer on the computer, refer the below link.

www.microsoft.com/downloads/details.aspx…6f9f4&displaylang=en

Tagged :

Windows Service does not appear in Windows Service Control Manager

msiexpert created the topic: Windows Service does not appear in Windows Service Control Manager
Hi
I am building a windows service with VS2010 Beta 2. I created a windows service project in vb. I added a ServiceController object to the service designer, I also added a ServiceInstaller and ServiceProcessInstaller and configured the ServiceInstaller.ServiceName = Service Project Name. I also added a deployment project with the correct Primary output project and the necessary additional dll and xml files I am using.

When I install using the .msi file the project installed successfully under the correct application directory and I get successful install message, however the service does not show up in the Service Control Manager. The platform is Vista Premium Service Pack 2. Also when I build the thing in VS2010 I always get the following warning message:

Warning 1 Item ‘Microsoft .NET Framework 4 Client Profile (x86 and x64)’ could not find any of dependent items ‘Microsoft.Windows.Installer.3.1, Microsoft.Windows.Installer.4.5’.

All the components used in the service are .NET 2.0 or lower. I have set the complier options to .NET 2.0 through to .NET 4.0 Beta. I always get the warning message. Any ideas why the Service Control Manager is not picking up my service? Any help much appreciated.

InstallerGeek replied the topic: Re: Windows Service does not appear in Windows Service Control Manager
Sounds like an overly complicated project. I recommend reading this article:
visualstudiomagazine.com/Articles/2005/1…Windows-Service.aspx

I found the code in that article to be overly complicated for my service application needs, so I developed a simple version which I will post in a separate reply.

Not sure if this information will help, but simpler is usually better.

Tagged :

Installing JBoss as a service

applicationPackaging created the topic: Installing JBoss as a service
I’m evaluating the Advanced Installer product, and I’m trying to create a simple installer that will install jboss as a service. I added the unzipped jboss distribution to the “Files and Folders”, created an entry under “Java Products” to create an executable to launch Jboss, and created an entry under “Services to Install” to install it as a service. After verifying that the correct Windows account is selected to start the service and the correct permissions are assigned to the product installation directory, I receive an error saying that the service didn’t respond within the timeout of 30000 ms. No jboss log files are generated, and I’m not sure how to get additional debugging information. If I double click the .exe that is generated for the “Java Product”, it doesn’t seem to take any action (although I do believe it is launching the jvm since I initially received some errors due to memory configuration that I was able to correct). I’m evaluating Advanced Installer to see if we can get off the old InstallShield X that we’re currently using which relies on JavaService.exe to install jboss as a service. This works fine and I’m guessing this might be an alternative way of installing jboss as a service using Advanced Installer custom actions, but I was really hoping to use the “Java Products” and “Services” to do this so that I can take advantage of the Advanced Installer features to start/stop services. If anyone has successfully created an installer to install jboss as a service, I’d appreciate some help (or a sample project if available).

applicationPackaging replied the topic: Re: Installing JBoss as a service
On the Java Products page, select your java product, go to Settings tab and make sure “Win32 Service” is selected in the “Type” field under the “Application” group.

Please let me know how this worked for you.

Tagged :