kubectl logs -f <pod_name>

kubectl rollout restart deployment

kubectl get deploy deploymentname -o yaml

kubectl create configmap <name-configmap> --from-env-file=.env

kubectl get configmap <name-configmap> -o yaml

kubectl edit configmap <name-configmap>

          envFrom:
            - configMapRef:
                name: <name-configmap>

• when calling the kubectl get pods -n dev, you're retrieving the list of the pods located under the namespace 'dev'.
• when calling the kubectl get deployments -n dev, you're retrieving the list of the deployments located under the namespace 'dev'.

1. Create a context named 'context-dev'.
2. Specify the namespace='dev' for this context.
3. Set the current-context='context-dev'.

• kubectl get pods
• kubectl get deployments

kubectl config get-contexts

kubectl config delete-context <context-name>

kubectl create namespace <name>

Namespaces

gcloud auth login
gcloud config set project YOUR_PROJECT_ID
gcloud container clusters get-credentials YOUR_CLUSTER_NAME --zone YOUR_CLUSTER_ZONE

ollama pull llama3.2

ollama run llama3.2

• kubectl get deployments: List all the running deployments.
• kubectl describe deployment <deploy name>: Print out details about a specific deployment
• kubectl apply -f <config file name>: Create a deployment out of a config file.
• kubectl delete deployment <deploy name>: Delete a deploy
• kubectl rollout restart deployment <deploy name>: Restart all pods created by deployment.

• Cluster: A collection of nodes + master to manage them.
• Node: Virtual machine to run our containers
• Pod: More or less a running container. Technically,  a pod can run multiple containers.
• Deploy: Monitors a set of pods, make sure they are running and restarts them if they crashed.
• Service: Provides an easy-to-remember URL to access to a running container.

• Pending: The pod has been accepted by the Kubernetes system but hasn't started running yet. This could mean that Kubernetes is still scheduling the pod to a node, or it’s waiting for resources (like storage or network) to become available.
• Running: The pod has been successfully scheduled to a node, and at least one of its containers is running.
• Succeeded: All containers in the pod have completed successfully, and the pod’s restartPolicy is set to Never or OnFailure.
• Failed: All containers in the pod have terminated, and at least one container exited with a non-zero status, indicating an error.
• CrashLoopBackOff: A container in the pod is repeatedly failing to start. Kubernetes is trying to restart it, but it continues to fail, resulting in a “crash loop.”

select 
  us.product_id,
  ROUND(SUM(us.units * p.price)::numeric / SUM(us.units), 2) AS average_price 
from Prices p
left join UnitsSold us on us.product_id = p.product_id and us.purchase_date between p.start_date and p.end_date
group by us.product_id
order by us.product_id

export const displayRoute = (route: string, t: (key: string) => string): string => {  
  const accountDetailRegex = /^\/accounts\/[0-9a-fA-F-]{36}$/;

  if (accountDetailRegex.test(route)) return t('accountDetails');
};