Kubernetes ReplicaSets - ReplicationController

By -
We have seen the word 'replicas' in the Docker Swarm services definition time.

How to work with ReplicaSet?

  What does ReplicaSet do?

ReplicaSet will define the group of pods. You can tell how many replicas of pods for your application. The template section will define how many pods and their specification will be defined. Defining ReplicaSet allows you to deploy podand keep it alive as per configuration.


How to create ReplicaSet?

ReplicaSet relationship with Pod 

        apiVersion: apps/v1
        kind: ReplicaSet
        metadata:
          name: my-tcat-rs
          labels:
            version: "3.0"
        spec:
          replicas: 2
          selector:
            matchLabels:
              project: MyWeb
              role: frontend
          template:
            metadata:
              labels:
                project: MyWeb
                role: frontend
                env: dev
        
            spec:
              containers:
              - name: mytomcat
                image: tomcat:latest
                resources:
                 requests:
                  cpu: 100m
                  memory: 256Mi
                ports:
                - containerPort: 8080
Create the replicaset using the YAML manifestat file. 
kubectl create -f replicasets.yml
2. Describe the ReplicaSet
In the spec, section is where the important things happen: we have defined a set of labels for the ReplicaSet, but we have also defined a pod template (in this case, with a single container) and specified that we want two pod instances of it (replicas: 2). 
        kubectl -n vybhava describe rs
        # another option to see the replicaset
        kubectl -n vybhava describe replicaset my-tcat-rs
3. How to Scale the ReplicaSet?

a. Scale-up ReplicaSet

You can specify the increased number for replicas configuration 
        kubectl -n vybhava scale --replicas=6 rs my-tcat-rs
        kubectl -n vybhava get all
b. Scale down ReplicaSet

You cna brought down the replicas to 0 as well. 
        kubectl -n vybhava scale --replicas=0 rs my-tcat-rs
        kubectl -n vybhava get all
4. Print wide output of the ReplicaSet
The regular kubectl command with get sub-command using -o wide option will give more details this we can use with alias name rs as well.
kubectl get rs -o wide or
  kubectl get replicasets -o wide
Kubernetes replicaset listing with wide output


5. Delete the ReplicaSet

Deleting the ReplicaSet using 'delete' sub-command provide the name of the replicaset. 
kubectl -n vybhava delete rs my-tcat-rs
kubectl -n vybhava get rs   
	
6.
6. How to get the ReplicaSets output to YAML or JSON format?

Hope you guys enjoyed this simple story about ReplicaSet commands and their outputs. Note that The Kubernetes docs explicitly suggest using a deployment rather than a ReplicaSet directly.

References


Comments

Post a Comment

Popular posts from this blog

Ansible 11 The uri module with examples

By -
Image
 Hey DevSecOps Automation specialist, Welcome back to the DevOps Hunter blog. In this post, I made it for learning more about all possible parameters that we can use when an application validation is done with the Ansible 'uri' module.  Why uri module? Web Application returns status HTTPCode 200 for success, 404 for failures, and also for 503 for Server internal issues. When you work on the restart of a web application we need to know the status of the application to proceed with the next move. So this uri module is most important for reboot and restart of web applications using ansible. The uri module parameters Supported parameters include: attributes, backup, body, body_format, client_cert, client_key, content, creates, delimiter, dest, directory_mode, follow, follow_redirects, force, force_basic_auth, group, headers, http_agent, method, mode, owner, regexp, remote_src, removes, return_content, selevel, serole, setype, seuser, src, status_code, timeout,...
Read more

Jenkins Active choices parameter - Dynamic input

By -
Image
Hello DevOps team!! Today I've revisited the experiment with the Jenkins ACTIVE CHOICE Parameter  to get the Dynamic parameters effect on the Build Job parameters. Installation Active Choice parameter - Groovy Script Prerequisite: Jenkins installed Up and running on your target master machine. Jenkins URL accessible   Step 1: Install Active Choice plugin On the Jenkins Dashboard, select the Manage Jenkins, Plugin- Manager, In the Available tab search for word 'Active', where you can see Active Choice plugin and choose installation option, and this will enables three different parameters in the "Add Paramters" list. They are : 1. Active choice parameter 2. Active Choice Reactive parameter 3. Active choice Reactive Reference parameter Here In my example I will use two of them, Firstly Active Choice Parameter for "environment". Create new item Name: active_project select a freestyle project click OK button. In the General tab, select the checkbo...
Read more

DevOps Weapons

By -
Image
To achieve faster application delivery and stable environments, the right tools must be used in DevOps environments. There is no single tool that fits all your needs such as server provisioning, configuration management, automated builds, code deployments, and monitoring. Many factors determine the use of a particular tool in your infrastructure.   In this article, we will look into core tools which can be used in a typical Devops environment. Version Control Tools: Git - An awesome tool to version your source code and collaborate. Terraform  - A tool used in building, changing, and versioning the infrastructure across platforms. Build Orchestration/Continuous Integration Tools: Jenkins - It is an open-source, lightweight CI tool written in Java, with high extensibility and a fast release cycle. Buildbot  - An open-source framework for automating software build, test and release process. CruiseControl  - A CI server written in  # Ruby ...
Read more