Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding metrics server and autoscaler to eks setup #20

Merged
merged 2 commits into from
Jan 12, 2021

Conversation

juandiegopalomino
Copy link
Collaborator

No description provided.

@juandiegopalomino juandiegopalomino merged commit 1ca3732 into main Jan 12, 2021
@juandiegopalomino juandiegopalomino deleted the metris-server-and-autoscaler branch January 12, 2021 21:25
ankurd1 added a commit that referenced this pull request Jan 27, 2021
* dd module

* use correct path

* remove values. allow no api key
ankurd1 added a commit that referenced this pull request Jan 27, 2021
* initialize with some modules

* add init module

* init tf

* get everything working

* add module files + reqd providers + handle db + make image optional

* minor cleanup

* support linking

* Remove module files and play folders

* New module for k8s secrets (#2)

* k8s secret

* default value

* ignore data changes

* Making the compute and state init modules

* wip

* wip

* Removing unnecessary file creation

* Creating a module for node pools

* HPA should always be enabled

* Minor updates for k8s/project init

1. iam api needs to be enabled
2. allow k8s service accounts to be linked directly to gcp service accounts

* Switched to AWS, added istio (#8)

* Created the metrics server and autoscaler modules (#9)

and also removed an old gcp one

* opta sets up istio with ingress and dmeo service (#10)

still trying to debug grpc demo

* Setting up the hello world service. (#11)

Yeah it's using istio, but I'll be reusing a bunch of this for ambassador+linkerd and I also wanted it in git history for future lookups.

* Got aws rds set up (#12)

* Got aws rds set up

* addressing cr

* Linkerd and Nginx Setup (#13)

Few things missing but are known to be possible:
1. Force ssl redirects while keeping NLB
2. Grpc support for ingress (works fine within the mesh)

* Got k8s service module working with linkerd and nginx (#14)

* Optionally create ecr repo to host none-external images (#15)

* Add support for secrets (#16)

* Need this present when creating new account (#17)

Otherwise weird errors

* New deployment process (#18)

* Standardized the k8s service naming convention (#19)

* Standardized the k8s service naming convention

The namespace will be the layername
The service is the module name

* minor cleanup

* Dont update secrets that already exist (#21)

* Datadog module (#20)

* dd module

* use correct path

* remove values. allow no api key

* Some improvements for datadog deployment (#22)

* Some improvements for datadog deployment

1. Enable K8s event collection for nice display
2. Enable logging
3. Enable using datadog metrics for pod autoscaling
4. Enable auto-injection of datadog env, service, and version as environment variables into the containers based on labels
5. Add helm release as a datadog tag

What will the effects to the user be once I add the labels as part of the helm charts? Zero

* whoopsie

* Opta migration stuff (#23)

* Bugfixes for k8s services migration

* Datadog updates

* fixing linkerd

* bugfixing datadog

* Adding timestamp to force a new deployment every time

* Fail fast on missing image tag

* make datadog gather linkerd metrics too

* Giving k8s services iam (#24)

For more info see #35

* import tf modules and fixes to make it work

* version command

* cleanup

* fix test

* remove tf modules

* Move modules

Co-authored-by: JD <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants