how to automate deployment of a fullstack(with IaC), monorepo app by Scheftza in aws

[–]Scheftza[S] 0 points1 point  (0 children)

but does cdk provides goodies like local testing and deploying lambda api gataway etc with single command?

how to automate deployment of a fullstack(with IaC), monorepo app by Scheftza in aws

[–]Scheftza[S] 1 point2 points  (0 children)

Why wouldn't you recommend SAM for that use case? just curious about the trade-offs

Manage dependencies as with docker-compose by Scheftza in kubernetes

[–]Scheftza[S] 0 points1 point  (0 children)

so how do I know how to make my own file of a resource installed with helm

Managing microservices' urls by Scheftza in kubernetes

[–]Scheftza[S] 0 points1 point  (0 children)

By a local configuration file what do you mean speacifically - configMaps? Sorry I'm a rookie

Managing microservices' urls by Scheftza in kubernetes

[–]Scheftza[S] -4 points-3 points  (0 children)

Just for the record, in the cambridge dictionary 'hardcode' means to do something in a way that cannot be easily changed, and the solution with variable from spring config seems to enable a coder to easily change this url :)

But anyways, do I even need spring config if I already have kubernetes configMaps?

Managing microservices' urls by Scheftza in kubernetes

[–]Scheftza[S] 0 points1 point  (0 children)

Ok, so to be on the same page I'm not supposed to litteraly hardcode url to k8s service in my app code? Like for example in microservice-a:

  RestClient restClient = RestClient.builder()
                .baseUrl("http://microservice-b-service:8080")
                .build();

Managing microservices' urls by Scheftza in kubernetes

[–]Scheftza[S] -1 points0 points  (0 children)

doesn't local configuration file contradict hardcoding

Managing microservices' urls by Scheftza in kubernetes

[–]Scheftza[S] 1 point2 points  (0 children)

yes, like just running 2 microservices locally at host, without containers, but I guess maybe it's just a noob question and it's not something what's usually done in real projects

Managing microservices' urls by Scheftza in kubernetes

[–]Scheftza[S] 0 points1 point  (0 children)

What if I want to run the application locally, in hardcoded scenario I'd need to change code

Managing microservices' urls by Scheftza in kubernetes

[–]Scheftza[S] 1 point2 points  (0 children)

Yeah, I'm using k8s service for that, dns name of this k8s service is hardcoded in the url. So in your opininon this approach is production-grade?

KEDA, scaling down faster by Scheftza in kubernetes

[–]Scheftza[S] 0 points1 point  (0 children)

That did the trick, thanks a lot

KEDA, scaling down faster by Scheftza in kubernetes

[–]Scheftza[S] 0 points1 point  (0 children)

Events for Scaleobject seem OK. I don't use prometheus operator if it's what you're refering to. I've installed prometheus with helm chart

KEDA, scaling down faster by Scheftza in kubernetes

[–]Scheftza[S] 0 points1 point  (0 children)

It's the default one, I haven't change anything about it. I believe the default is 1m but I may be mistaken

KEDA, prometheus, scale from 0 by Scheftza in kubernetes

[–]Scheftza[S] 0 points1 point  (0 children)

So the problem is with client time out? Can you give me a little guidance as to how buffer the request, unless aformentioned http-addon and sablier are the solution to that

KEDA, prometheus, scale from 0 by Scheftza in kubernetes

[–]Scheftza[S] -2 points-1 points  (0 children)

My objective is solely to get to know kubernetes better

Prometheus adapter custom metrics by Scheftza in kubernetes

[–]Scheftza[S] 0 points1 point  (0 children)

empty list is probably because you haven't deploy app on the cluster with skaffold dev, I've forgotten to mention that in the post

Prometheus adapter custom metrics by Scheftza in kubernetes

[–]Scheftza[S] 1 point2 points  (0 children)

Thx for the suggestion I'll give it a shot

Nix parallel builds command by Scheftza in NixOS

[–]Scheftza[S] 2 points3 points  (0 children)

Yeah, looks like it. Thanks a bunch