In a cluster best practices are to gather all logs in a single point through an aggregator and analyze them with a dedicated tool. For that reason in K8S, log command is quite basic. Anyway kubectl logs -h shows some options useful for you: # Display only the most recent 20 lines of output in … Read more
Since version 1.11, you can do: kubectl wait –for=condition=complete job/myjob and you can also set a timeout: kubectl wait –for=condition=complete –timeout=30s job/myjob
You can export the variable and use it while running helm install. Before that, you have to modify your chart so that the value can be set while installation. Skip this part, if you already know, how to setup template fields. As you don’t want to expose the data, so it’s better to have it … Read more
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.
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
Pods have status, which you can use to find out startTime. I guess something like kubectl get po –sort-by=.status.startTime should work. You could also try: kubectl get po –sort-by='{.firstTimestamp}’. kubectl get pods –sort-by=.metadata.creationTimestamp Thanks @chris Also apparently in Kubernetes 1.7 release, sort-by is broken. https://github.com/kubernetes/kubectl/issues/43 Here’s the bug report : https://github.com/kubernetes/kubernetes/issues/48602 Here’s the PR: https://github.com/kubernetes/kubernetes/pull/48659/files
This should work: kubectl create secret generic production-tls \ –save-config \ –dry-run=client \ –from-file=./tls.key –from-file=./tls.crt \ -o yaml | \ kubectl apply -f –