You can get YAML from the kubectl create configmap command and pipe it to kubectl apply, like this: kubectl create configmap foo –from-file foo.properties -o yaml –dry-run | kubectl apply -f –
The simplest answer is to ensure that your pod or replication controller yaml/json files add the pod IP as an environment variable by adding the config block defined below. (the block below additionally makes the name and namespace available to the pod) env: – name: MY_POD_NAME valueFrom: fieldRef: fieldPath: metadata.name – name: MY_POD_NAMESPACE valueFrom: fieldRef: … Read more
In Kubernetes 1.16 some apis have been changed. You can check which apis support current Kubernetes object using $ kubectl api-resources | grep deployment deployments deploy apps true Deployment This means that only apiVersion with apps is correct for Deployments (extensions is not supporting Deployment). The same situation with StatefulSet. You need to change Deployment … Read more
Removing old replicasets is part of the Deployment object, but it is optional. You can set .spec.revisionHistoryLimit to tell the Deployment how many old replicasets to keep around. Here is a YAML example: apiVersion: apps/v1 kind: Deployment # … spec: # … revisionHistoryLimit: 0 # Default to 10 if not specified # …
I think that this PR contains the change you’re asking about. `Ingress` and `IngressClass` resources have graduated to `networking.k8s.io/v1`. Ingress and IngressClass types in the `extensions/v1beta1` and `networking.k8s.io/v1beta1` API versions are deprecated and will no longer be served in 1.22+. Persisted objects can be accessed via the `networking.k8s.io/v1` API. Notable changes in v1 Ingress objects … Read more
The issue is that your kubeconfig is not right. To auto-generate it run: gcloud container clusters get-credentials “CLUSTER NAME” This worked for me.
You can use the event command of kubectl. To filter for a specific pod you can use a field-selector: kubectl get event –namespace abc-namespace –field-selector involvedObject.name=my-pod-zl6m6 To see what fields are possible you can use kubectl describe on any event.
In the official documentation I found this: https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#accessing-the-api-from-a-pod Apparently I was missing a security token that I didn’t need in a previous version of Kubernetes. From that, I devised what I think is a simpler solution than running a proxy or installing golang on my container. See this example that gets the information, from the … Read more
From the docs PVs are resources in the cluster. PVCs are requests for those resources and also act as claim checks to the resource. So a persistent volume (PV) is the “physical” volume on the host machine that stores your persistent data. A persistent volume claim (PVC) is a request for the platform to create … Read more
Based on this comment , the supported way to list all resources is to iterate through all the api versions listed by kubectl api-resources: kubectl api-resources enumerates the resource types available in your cluster. this means you can combine it with kubectl get to actually list every instance of every resource type in a namespace: … Read more