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

• Customers with columns customer_id and name
• Products with columns product_id and name

SELECT customers.customer_id, customers.name, products.product_id, products.name
FROM customers
CROSS JOIN products;

docker push NAME[:TAG]

• Version control: Tags help identify different versions of an image.
• Traceability: Tags allow you to track changes and updates to an image.
  Automation: Tags are used in automated processes, such as deploying new versions.
  Troubleshooting: Tags help pinpoint specific image versions when debugging.
  Managing large-scale projects: Tags organize images in complex projects.
  
  

docker tag [OPTIONS] IMAGE[:TAG] [REGISTRYHOST/][USERNAME/]NAME[:TAG]

docker tag 518a41981a6a myRegistry.com/myImage

The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create the resource with that URI.

If a new resource is created, the origin server MUST inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No Content) response codes SHOULD be sent to indicate successful completion of the request. If the resource could not be created or modified with the Request-URI, an appropriate error response SHOULD be given that reflects the nature of the problem.

// Add a request interceptor
axios.interceptors.request.use(function (config) {
    // Do something before request is sent
    return config;
  }, function (error) {
    // Do something with request error
    return Promise.reject(error);
  });

// Add a response interceptor
axios.interceptors.response.use(function (response) {
    // Any status code that lie within the range of 2xx cause this function to trigger
    // Do something with response data
    return response;
  }, function (error) {
    // Any status codes that falls outside the range of 2xx cause this function to trigger
    // Do something with response error
    return Promise.reject(error);
  });

• Idempotency is a property of operations or API requests that ensures repeating the operation multiple times produces the same result as executing it once.
• Safe methods are idempotent but not all idempotent methods are safe.
• 
  
• HTTP methods like GET, HEAD, PUT, DELETE, OPTIONS, and TRACE are idempotent, while POST and PATCH are generally non-idempotent.

function exampleFunction() {
    const value = 42;
    debugger; // Execution will pause here if a debugger is attached
    console.log(value);
}

exampleFunction();

node --inspect --5120 lib/app.js

Debugger listening on ws://127.0.0.1:9229/65b96f6d-6202-49db-bbe8-63b706a580a2

Visit the port on your browser and open the Node DevTools.