9 messages
rohitalmost 2 years ago
Is there a way to run a "virtual load balancer" inside kubernetes so one would not have to manage a cloud-native load balancer (ALB: aws, whatever gcp or azure has)?
mikoalmost 2 years ago(edited)
Status: CLOSED
Heroes: 👑@Hao Wang, @Adi
Hey guys! In AWS EKS I have deployed a StatefulSet Apache Kafka, it's working well except when I upgrade the docker image or if all the nodes goes to 0 it loses the volume data despite having
Heroes: 👑@Hao Wang, @Adi
Hey guys! In AWS EKS I have deployed a StatefulSet Apache Kafka, it's working well except when I upgrade the docker image or if all the nodes goes to 0 it loses the volume data despite having
volumeClaimTemplates defined. The full config is in the first reply!
Andrés Peña Castilloalmost 2 years ago
Hello folks, good evening from Costa Rica. I was wondering if someone here has ever had a similar question to this.
How do you usually monitor performance for an app running inside a Kubernetes/OpenShift cluster?
I just found a tool bundled within OpenShift called Performance Profile Creator, but it unknown to me if there's any Kubernetes-native solutions.
https://docs.openshift.com/container-platform/4.15/scalability_and_performance/cnf-create-performance-profiles.html
How do you usually monitor performance for an app running inside a Kubernetes/OpenShift cluster?
I just found a tool bundled within OpenShift called Performance Profile Creator, but it unknown to me if there's any Kubernetes-native solutions.
https://docs.openshift.com/container-platform/4.15/scalability_and_performance/cnf-create-performance-profiles.html
venkataalmost 2 years ago
Anyone here have recommendations on ML based tools that can help recommend or even automatically set things like: Requests, Limits, Affinity, and Anti-affinity scheduling policies?
rohitalmost 2 years ago(edited)
are there good projects to inject "chaos" pod termination/node termination, network failures into kubernetes? in order to test our applications resiliency
O
OliverSover 1 year ago(edited)
Hey I watched a CNCF webinar by someone from Werf about a tool called "nelm". I have not tried it but it is a backwards compatible fork from helm 3 to solve many important problems with helm, one of which that helm is barely evolving to fix its problems 🙂 (eg helm 4 is 2 years behind schedule and no roadmap to get there).
It's a 50 minute presentation but here is a summary slide from the end of the presentation. In particular, Werf team has maintained compatibility with helm 3, they have done away with 3-way merge in favor of k8s server-side-apply, nelm tracks resources and can rollback properly, it has improved support for CRDs and helm charts can be fetched directly from git (like terraform for modules), nelm has a dependency system, etc.
It is not yet available as a standalone package but Werf is working on it, so currently you have to install werf to get nelm.
It's a 50 minute presentation but here is a summary slide from the end of the presentation. In particular, Werf team has maintained compatibility with helm 3, they have done away with 3-way merge in favor of k8s server-side-apply, nelm tracks resources and can rollback properly, it has improved support for CRDs and helm charts can be fetched directly from git (like terraform for modules), nelm has a dependency system, etc.
It is not yet available as a standalone package but Werf is working on it, so currently you have to install werf to get nelm.
mikoover 1 year ago(edited)
Status: CLOSED
Hero: 👑@Piotr Pawlowski
Hey guys, I'm reading Cluster-level logging architectures but I can't quite understand what this means:
You can implement cluster-level logging by including a node-level logging agent on each node. The logging agent is a dedicated tool that exposes logs or pushes logs to a backend. Commonly, the logging agent is a container that has access to a directory with log files from all of the application containers on that node.
What does it mean to implement something at a node-level? Does it simply mean to run the YAML inside the cluster? What do they mean by agent? The deployment is the agent?
Hero: 👑@Piotr Pawlowski
Hey guys, I'm reading Cluster-level logging architectures but I can't quite understand what this means:
You can implement cluster-level logging by including a node-level logging agent on each node. The logging agent is a dedicated tool that exposes logs or pushes logs to a backend. Commonly, the logging agent is a container that has access to a directory with log files from all of the application containers on that node.
What does it mean to implement something at a node-level? Does it simply mean to run the YAML inside the cluster? What do they mean by agent? The deployment is the agent?
Narayanaperumal Gurusamyover 1 year ago
Is there any example of eks addons interaction with EBS?