ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
Context Harvester v1.3–1.4 officially supports single-node clusters for development and edge scenarios. The installer provisions an embedded etcd member and sets the Longhorn default replica count to 1. For production HA, the documented path requires at least three server nodes, a 3-member etcd cluster, and a Longhorn default replica count of 3 with anti-aff
System component metrics can give a better look into what is happening inside them. Metrics are particularly useful for building dashboards and alerts. Kubernetes components emit metrics in Prometheus format . This format is structured plain text, designed so that people and machines can both read i
I have been using the Kubernetes and Helm for a while and have now come across Kustomize for the first time. But what exactly is the difference between Kustomize and Helm? Are both simply different solutions for bundling K8s elements such as services, deployments, ...? Or does it make sense to use both Helm and Kustomize together?
Note: This section links to third party projects that provide functionality required by Kubernetes. The Kubernetes project authors aren't responsible for these projects, which are listed alphabetically. To add a project to this list, read the content guide before submitting a change. More informatio
I have a local kubernetes cluster on my local docker desktop. This is how my kubernetes service looks like when I do a kubectl describe service Name: helloworldsvc Namespace: test Labels: app=helloworldsvc Annotations: kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"helloworl
By default, containers run with unbounded compute resources on a Kubernetes cluster. Using Kubernetes resource quotas , administrators (also termed cluster operators ) can restrict consumption and creation of cluster resources (such as CPU time, memory, and persistent storage) within a specified nam
How do I make an optional block in the values file and then refer to it in the template? For examples, say I have a values file that looks like the following: # values.yaml foo: bar: "something" And then I have a helm template that looks like this: {{ .Values.foo.bar }} What if I want to make the foo.bar in the values file optional? An error is raised if the
I had the below YAML for my Ingress and it worked (and continues to work): apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: test-ingress namespace: test-layer annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: mylocalhost.com http: paths: - path: / backend: serviceName: test-app servicePort: 5000 However, it
This page outlines the differences in how resources are managed between Linux and Windows. On Linux nodes, cgroups are used as a pod boundary for resource control. Containers are created within that boundary for network, process and file system isolation. The Linux cgroup APIs can be used to gather
rancher