A ClusterIP exposes the following: spec.clusterIp:spec.ports[*].port You can only access this service while inside the cluster. It is accessible from its spec.clusterIp port. If a spec.ports[*].targetPort is set it will route from the port to the targetPort. The CLUSTER-IP you get when calling kubectl get services is the IP assigned to this service within the … Read more
It was my bad. Due to following blog post: https://kubernetes.io/blog/2018/04/13/local-persistent-volumes-beta/ Note that there’s a new nodeAffinity field in the PersistentVolume object: this is how the Kubernetes scheduler understands that this PersistentVolume is tied to a specific node. nodeAffinity is a required field for local PersistentVolumes. and my value was incorrect. I changed it to my … Read more
It would appear that you are attempting to deploy Kubernetes leveraging kubeadm but have skipped the step of Installing a pod network add-on (CNI). Notice the warning: The network must be deployed before any applications. Also, CoreDNS will not start up before a network is installed. kubeadm only supports Container Network Interface (CNI) based networks … Read more
Depending on how often you need to do this you might look at the df-pv plugin for kubectl https://github.com/yashbhutwala/kubectl-df-pv It does exactly what you are asking across all the pvs in a namespace or cluster. Once you’ve got it installed, just run kubectl df-pv and you are set.
Using EFS without automatic provisioning The EFS provisioner may be beta, but EFS itself is not. Since EFS volumes can be mounted via NFS, you can simply create a PersistentVolume with a NFS volume source manually — assuming that automatic provisioning is not a hard requirement on your side: apiVersion: v1 kind: PersistentVolume metadata: name: … Read more
What you’re looking for is – name: ENV_NAME valueFrom: secretKeyRef: name: <secrets name> key: <secrets key> optional: true You can find type definition here Edit: similarly for envFrom envFrom: – secretRef: name: secname optional: true
In addition to Jonas’ answer above; If you have more than one namespace, you need to specify the namespace your pod is currently using i.e kubectl exec -n <name space here> <pod-name> -it — /bin/sh After successfully accessing your pod, you can go ahead and navigate through your container.
How can I list, show all the charts installed by helm on a K8s? helm list –all-namespaces Where does helm keep the which repository installed etc? By default in Secret objects in the same namespace as the release, but this can be changed. Can I somehow export the helm’s repository list and history Not really. … Read more