k8s-aws | A kops wrapper script for bootstrapping Kubernetes on AWS | AWS library

by coder-society Python Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | k8s-aws Summary

k8s-aws is a Python library typically used in Cloud, AWS applications. k8s-aws has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

A kops wrapper script for bootstrapping Kubernetes on AWS

Support

Quality

Security

License

Reuse

Support

k8s-aws has a low active ecosystem.

It has 33 star(s) with 18 fork(s). There are 8 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 3 have been closed. On average issues are closed in 31 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of k8s-aws is current.

Quality

k8s-aws has 0 bugs and 0 code smells.

Security

k8s-aws has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

k8s-aws code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

k8s-aws is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

k8s-aws releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of k8s-aws

Get all kandi verified functions for this library.

k8s-aws Key Features

No Key Features are available at this moment for k8s-aws.

k8s-aws Examples and Code Snippets

No Code Snippets are available at this moment for k8s-aws.

Community Discussions

Trending Discussions on k8s-aws

AWS Load Balancer Controller successfully creates ALB when Ingress is deployed, but unable to get DNS Name in CDK code

Terraform: Deploying a Docker Compose app on EKS/ECS

Get authentication token from AWS EKS using the AWS Java SDK v2

QUESTION

AWS Load Balancer Controller successfully creates ALB when Ingress is deployed, but unable to get DNS Name in CDK code

Asked 2021-Jun-13 at 20:44

I originally posted this question as an issue on the GitHub project for the AWS Load Balancer Controller here: https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2069.

I'm seeing some odd behavior that I can't trace or explain when trying to get the loadBalacnerDnsName from an ALB created by the controller. I'm using v2.2.0 of the AWS Load Balancer Controller in a CDK project. The ingress that I deploy triggers the provisioning of an ALB, and that ALB can connect to my K8s workloads running in EKS.

Here's my problem: I'm trying to automate the creation of a Route53 A Record that points to the loadBalancerDnsName of the load balancer, but the loadBalancerDnsName that I get in my CDK script is not the same as the loadBalancerDnsName that shows up in the AWS console once my stack has finished deploying. The value in the console is correct and I can get a response from that URL. My CDK script outputs the value of the DnsName as a CfnOutput value, but that URL does not point to anything.

In CDK, I have tried to use KubernetesObjectValue to get the DNS name from the load balancer. This isn't working (see this related issue: https://github.com/aws/aws-cdk/issues/14933), so I'm trying to lookup the Load Balancer with CDK's .fromLookup and using a tag that I added through my ingress annotation:

...

ANSWER

Answered 2021-Jun-13 at 20:23

I think that the answer is to use external-dns.

ExternalDNS allows you to control DNS records dynamically via Kubernetes resources in a DNS provider-agnostic way.

Source https://stackoverflow.com/questions/67955013

QUESTION

Terraform: Deploying a Docker Compose app on EKS/ECS

Asked 2020-Apr-21 at 15:31

TL;DR

I use an open-source server application running on Docker Compose. It has a few services, including PostgreSQL DB and Redis.

How can I best deploy this application to AWS in full IaC with Terraform?

Solutions so far 1. AWS ecs-cli

ecs-cli now supports sending docker compose configs in Amazon ECS.

However, I do not think it could be integrated with the Terraform workflow (which is maybe not a big fuss). What I know for sure is that ecs-cli is not supported in CloudFormation, as per this issue, still open at this time. So I assume it cannot easily be added to Terraform either.

2. The hard EKS way

Take your docker-compose.yml file, translate it to kubectl YAML.
(Prepare to doing so every time the package upgrades).
Deploy using Terraform's + EKS APIs (minimal example).

But that is not fully IaC yet. And you have to retranslate your config each time the docker-compose changes in the source repository. And it sounds like a lot of work.

3. Using a Helm chart

Write a Helm chart for the application.
Run Terraform to start a cluster.
Still run Terraform with a helm provider to install the application with Helm on the cluster.

4. [Not OK] k8s Kompose

I read Kompose can automagically translate a Docker Compose configuration to a k8s configuration, but they don't appear to be ported on AWS, not to talk about Terraform.

5. [Not OK] The dirty AMI solution

Build a custom EC2 AMI with Packer.
Using Terraform, set up the DB, Redis and all permissions / network / etc.
Start an EC2 instance with the custom AMI.
The AMI contains (customized) application code, especially the docker-compose.yml. And the Docker images.
The AMI starts a Docker Compose systemctl service.

That would kind of hurt: long builds, difficult monitoring, no scaling.

Side notes

I mentioned I need full IaC. What I mean by it is:
1. The written config (and it only) on master tells you what is deployed.
2. The deploy will complete without my team having to run any other command. It basically works either on CI/CD or on single-push'n'go.
3. Monitoring and alerting are easily configured in the IaC.
I wish to replace some services with AWS components (namely, the PostgreSQL service by an RDS, and the Redis service with an ElastiCache).
The application happens to be Apache Superset. However I am also wondering what is considered the best general approach to this Docker Compose problem.

...

ANSWER

Answered 2020-Apr-20 at 14:22

1. Wait and See

Who knows, ecs-cli-v2 might be better integrated with CloudFormation and/or Terraform.

2. Use a Helm chart

As mentioned in the question. Probably the best solution, albeit requiring a (little) effort to parametrize Helm.

Vulnerabilities

No vulnerabilities reported

Install k8s-aws

You can download it from GitHub.
You can use k8s-aws like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: