Professional Documents
Culture Documents
version 2021-12-06 EN
# CLI setup # Create a deployment named web, using image nginx into prod namespace
CLI tools
deploy / expose
https://ibd.sh/helm
# Retrieve logs of pods with tag app=web
kubetail -l app=web
# List available contexts
contextes
kubectx # Open a tunnel listening on 127.0.0.1:8080 to the port 80 of a pod related to deployment web
kubectl port-forward deploy/web 8080:80
# Change context to dev
kubectx dev # Create a Yaml manifest, without sending it to the cluster
kubectl create deploy web --image=nginx --dry-run=client -o yaml > web.yml
kubens
# Change namespace to prod # Retrieve detailed state of pod test # PVC manifest example
storage / volume
kubens prod kubectl describe pod test kind: PersistentVolumeClaim
help / debug
apiVersion: v1
# Create namespace test # Get all possible attributes of a resource metadata:
kubectl create ns test name: web-data
kubectl explain pod --recursive spec:
accessModes:
# Open a bash terminal in pod app
# Ingress manifest example - ReadWriteOnce
apiVersion: networking.k8s.io/v1 kubectl exec -it app -- bash resources:
kind: Ingress
metadata:
requests:
name: test-ingress
# NB : The flag --help provide help of any command storage: 42Gi
spec:
ingress
rules:
- host: foo.bar.com
# Use the config file /path/to/config rather than ~/.kube/config
Web : infraBuilder.com
Command cheasheet
by Alexis DUCASTEL
http:
paths:
- path: /testpath
export KUBECONFIG=/path/to/config
pathType: Prefix
backend: # Merge two configuration files config1 and config2 in one file config
service:
name: test KUBECONFIG=config1:config2 kubectl config view --flatten > config
port:
number: 80
tls: # Export only the current context configuration to file config
- hosts:
- foo.bar.com kubectl config view --minify --flatten > config
secretName: foobar-tls