|
- What is the meaning of CPU and core in Kubernetes?
To clarify what's described here in the Kubernetes context, 1 CPU is the same as a core (Also more information here)
- kubernetes - How to check if network policy have been applied to pod . . .
I'm trying to restrict to my openvpn to allow accessing internal infrastructure and limit it only by 'develop' namespace, so I started with simple policy that denies all egress traffic and see no e
- How can I trigger a Kubernetes Scheduled Job manually?
I've created a Kubernetes Scheduled Job, which runs twice a day according to its schedule However, I would like to trigger it manually for testing purposes How can I do this?
- kubernetes - Complete list of pod statuses - Stack Overflow
When you run quot;kubectl get pods -A -o wide quot; you get a list of pods and a STATUS column Where can I get a list of the possible status options? What I trying to do is generate a list of sta
- kubernetes - What is the difference between a pod and a deployment . . .
In kubernetes Pods are the smallest deployable units Every time when we create a kubernetes object like Deployments, replica-sets, statefulsets, daemonsets it creates pod
- kubernetes - Ingress configuration for k8s in different namespaces . . .
I need to configure Ingress Nginx on azure k8s, and my question is if is possible to have ingress configured in one namespace et ingress-nginx and some serivces in other namespace eg resources? My
- kubernetes - Monitoring PVC Usage with Prometheus - Stack Overflow
EDIT: These metrics are from kube-state-metrics - a service that produces Prometheus format metrics based on the current state of the Kubernetes native resources It is basically listening to Kubernetes API and gathering information about its resources and objects, in particular for PV - PV metrics and PVC - PVC metrics
- How to expose a Kubernetes service on a specific Nodeport?
kubectl delete service kubernetes-dashboard -n kube-system Expose the Dashboard deployment as a NodePort kubectl expose deployment kubernetes-dashboard -n kube-system --type=NodePort The above will assign a random port >= 30000 So use the Patch command to assign the port to a known, unused and desired port >= 30000
|
|
|