Please enable JavaScript.

Coggle requires JavaScript to display documents.

All things devops - Coggle Diagram

- - - - Exposes a service within the Kubernetes cluster, making it accessible to other pods and services internally.
    - - Exposes a service on a specific port on all nodes of the cluster. This allows you to access the service from outside the cluster using the node's IP address and the assigned port.
    - - x Exposes a service externally using a cloud provider's load balancer
    - - An ExternalName service is a special type of Kubernetes service that maps a service name within the cluster to an external DNS name.
  - - - pods template: image, ports
      - no replicas
      - update strategies
  - - - describe desired states using yaml file manifest
      - each yaml manifest for each service will have a different structure of declaration
    - - run kubectl to achieve a desired states
  - - - deprecated
    - - csi: container storage interface
      - create mysql with persistence storage using aws ebs volume
        
        persistence volume chain
        
        config map
        
        Deployment, Environment Variables, Volumes, VolumeMounts
        
        clusterip service
    - - secrects
      - init containers
      - liveliness and readiness probes
    - - drawback of using mysql server
        
        mysql server expert and knowledge
      - My ExternalName Services
        
        use to connect MySQL to ARDS
  - - - Kubelet uses liveness probes to know
        when to restart a container
    - - Kubelet uses readiness probes to know
        when a container is ready to accept traffic
    - - Kubelet uses startup probes to know when
        a container application has started
  - - - soon to be deprecated
    - - external name service
        
        external dns service account
  - - - follow security standard to run production workload on eks
    - - Contains Kubernetes
        Master components
        like etcd, kubeapiserver, kubecontroller.
        It’s a managed
        service by AWS
    - - group of ec2 instance
    - - instead running application on ec2 instance, run on severless fargate
  - - - key components include
        
        host name
        
        path: rule for handling different url path
        
        target services
        
        ingress controller
        
        monitor
        
        configure
        
        traffic mangement
    - - user enter external traffics
      - resolve to ip address of Ingress Controler
      - Ingress Controller examine the hostname , request against the predefined Ingress Rules
      - Route to Backend Service
- - - - machine or containers that run jobs
    - - unit testing
      - integration testing
      - ui testing
      - security testing