Skip to main content

Cheatsheet: Kubernetes (K8s)


Namespaces:

- Namespaces are used as a means to separate k8s resources

Create Namespace

kubectl create ns <--namespace-->

Get all namespaces

kubectl get namespaces

Pod:

- Pod allows you to run the application in a container
- Usually the config for pods are defined in YAML, but you can create a quick pod using "run" command.

kubectl run <--pod-name--> --image=nginx:2.3.5 --restart=Never --port=80 --namespace=<--namespace-->

View pods details

kubectl get pod -n <--namespace-->

Describe pod:
- This will provide much deeper insight into the pod

kubectl describe pod -n <--namespace-->

Modify pod

*Replace xyzPod with your pod name below
 
kubectl set image pod xyzPod xyzPod=nginx --namespace=<--namespace-->

Check Pod status:

kubectl get pod -n <--namespace-->

Shell into container:

kubectl exec <--pod-name--> -it --namespace=<--namespace--> -- /bin/sh

- exit from shell

#exit

Access Pod logs:

kubectl logs <--pod-name--> -n <--namespace-->

Delete K8s Resources:

- Pod:
kubectl delete pod <--pod-name--> --namespace=<--namespace-->

- namespace:
kubectl delete namespace <--namespace-->

Force delete - K8s tries to gracefully delete the resources, if you want to speed-up the process and want to force delete the resources. Use the following command-line option.

     --grace-period=0 --force


Happy coding ðŸ‘¨‍💻

Comments

Popular posts from this blog

Spring Boot - RestTemplate PATCH request fix

  In Spring Boot, you make a simple http request as below: 1. Define RestTemplate bean @Bean public RestTemplate restTemplate () { return new RestTemplate (); } 2. Autowire RestTemplate wherever you need to make Http calls @Autowire private RestTemplate restTemplate ; 3. Use auto-wired RestTemplate to make the Http call restTemplate . exchange ( "http://localhost:8080/users" , HttpMethod . POST , httpEntity , String . class ); Above setup works fine for all Http calls except PATCH. The following exception occurs if you try to make a PATCH request as above Exception: I / O error on PATCH request for \ "http://localhost:8080/users\" : Invalid HTTP method: PATCH ; nested exception is java . net . ProtocolException : Invalid HTTP method: PATCH Cause: Above exception happens because of the HttpURLConnection used by default in Spring Boot RestTemplate which is provided by the standard JDK HTTP library. More on this at this  bug Fix: This can b...

Settings.xml for Maven, JFrog

For development and deployment of applications we always use an artifactory in real-time world to host artifacts needed for your build and also as a target to deploy artifacts generated in the build process. For Maven, to communicate with artifactory we need a settings.xml file which is usually located at "/User/rake/.m2/settings.xml" this file consists of how to authenticate to the artifactory servers and authorizations to read/ write to different locations like release, snapshots e.t.c... Settings.xml can be generated using the artifactory you're using which in my case is JFrog , but here's a sample settings file for your reference incase you're feeling lazy☺ <?xml version="1.0" encoding="UTF-8"?> <settings xsi:schemaLocation= "http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns= "http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi= "http://www.w3.org/2001/XM...

Stored Procedures in ADF

One of the common requirements for ADF programmers is to invoke Stored Procedures and Functions. Implementing this is so simple with few lines of code in Java classes used under business components. Following code snippets from fusion guide  will help execute different procedures with and without arguments. Execute stored procedure with No Arguments: public void callProcWithNoArgs() { getDBTransaction().executeCommand( "begin devguidepkg.proc_with_no_args; end;"); } Execute stored procedure with only IN arguments: Procedures often take arguments in order to process some business logic. Arguments are limited from none to many. In order to use stored procedures with argument mode we need to use JDBC PreparedStatement object. How To: Create connection Create a JDBC PreparedStatement with procedure details wrapped in a PL/SQL begin..end block. Assign the values to arguments if any. Execute the statement. Close the statement. protected void callStoredPr...