Posts

Identity and access management

Video 1:  video1 SAML: video2 Oauth2 and OIDC: video3 single sign on:  part1 part2 Ultimate Guide of Identity and access management: here OIDC or SAML, which is preferred  choice for single sign on? Both OpenID Connect (OIDC) and Security Assertion Markup Language (SAML) are widely used protocols for Single Sign-On (SSO) in modern web applications. However, the best protocol for SSO depends on the specific needs and requirements of the application and the organization using it. OIDC is a modern, lightweight and flexible protocol that is designed to work well with modern web and mobile applications. It is built on top of OAuth 2.0, which makes it easier to integrate with APIs and microservices. It supports modern features such as JSON Web Tokens (JWT) and allows for more fine-grained control over access and authorization. SAML, on the other hand, is an older and more established protocol that has been around for a longer time. It is widely used in enterprise environments ...

Argo CD

Istio Service mesh

 ISTIO SERVICE MESH: The proxies are collectively called datapalane in istio

Prometheus

Image
 Prometheus: Exporters: Node Exporter(To get Linux machine metrics): Similarly we gave wmi exporter , to collect metrics of windows machines(not officialy supported) See different exporters: here PromQL: PromQL, short for Prometheus Querying Language, is the main way to query metrics within Prometheus

jenkins

Image
 Jenkins pipeline:

Authentication and Authorization

 Web Authentication Methods: HTTP Basic Authentication HTTP Digest Authentication Session-based Auth Token-Based Authentication One Time Passwords OAuth and OpenID Detailed blog:  here  and video  here (Tested with Postman) HTTP is a stateless protocol.So you need to store state using session(cookies) or tokens. Using Sessions the state is stored in the server side and sent to the clinet in response header.So when client want to talks to the server then again this session information needed to be sent using cookies. It work fine for smal applications which are hosted on single host, but when your appliation is large and requires a load balancing solution we need to store that session information in common location eg:Redis. In order to avaoid this, JWT token info in the client side only.So there is no overhead of maintaining state information on the server side JWT:(JSON Web Token) * Best video on internet: video1 , what is JWT and why we need it * Diff between ...

Kind kubernetes cluster

Kind: Must watch video: here To get config file of the cluster, use command   kind export kubeconfig --name <clustername>  kind get kubeconfig >~/.kube/config(Only if you are connected to the cluster and want to get kubeconfig of that cluster) If you want to use specific version of kubernetes with kind, specify the same using --image option while creating cluster  kind create cluster --name testcluster --image kindest/node:v1.23.10@sha256:f047448af6a656fae7bc909e2fab360c18c487ef3edc93f06d78cdfd864b2d12 Note: Images are available under github->releases. click here kind export logs --name <clustername> It copies all logs into host machine inside /tmp/randomnumbers. It containers all the