Search for a command to run...
A focused boutique consulting partner to boot your current and future digital DevSecOps and Cloud Platform needs.
At BootLabs we are obsessed about building future-ready Intelligent Enterprise. We solve cloud automation problems with cutting-edge technologies while making sure the TCO is minimal. We enable organisational transformation to support the rapid application development and consistent releases.
No comments yet. Be the first to comment.
A Proactive Approach to Software Security in the Digital Transformation
Gatekeeper is a general-purpose policy engine based on Open Policy Agent (OPA). It allows you to define and enforce custom policies across various Kubernetes resources. Kyverno is specifically designed for Kubernetes policy management. It focuses o...
Connecting to an AWS private EC2 instance using OpenSSH requires a few prerequisites and steps. Prerequisites: Ensure you have OpenSSH installed. Make sure you have AWS CLI version 2.12.6 or above installed. Set up an EC2 instance connect endpoint...
HANDLING SECRETS AND PARAMETERS ON AWS EKS Security best practices need the protection of personal data (e.g. passwords, tokens, API Keys). These details are often saved in AWS Secrets Manager or AWS Systems Manager Parameter Store when utilising AWS...
Velero
Velero is an open-source tool for Kubernetes, to safely backup and restores the data in a cluster and disaster recovery of the cluster. With the help of velero, we can store the backup of EKS and volumes will store in a bucket and disk (in AWS).
Velero can be installed in the cluster using the helm chart in the velero namespace. Can check by kubectl get all -n velero
After installing velero we need to establish the connection between cluster and bucket and if disk(If need to take backup of volumes in a cluster) is required. And the credential file is required, by using this command
velero install --provider aws --image velero/velero:v1.8.0 --plugins velero/velero-plugin-for-aws:v1.4.0 --bucket <bucket_name> --secret-file <path_of_credential_file> --use-volume-snapshots=false<true_if_volume_required> --backup-location-config region=<region_of_the_bucket>
It will take a backup of the cluster or a particular namespace that can be backuped up based on the requirement, these backups will be stored.
velero backup create t2 (-n <name space name> if required)
These backups will be replaced when the cluster gets destroyed or some deployment fails or some release has some bucks.
If the connection is established between the EKS and S3 bucket
velero restore create <restore name> --from-backup <backup name>
With the help of velero the backup can be automated using a scheduler in velero. It will work like a label selector if the command has a selector then the command will execute in the scheduled time period. It can be of Days or Months or Minutes.
velero schedule create <schedule name> --schedule=”< time interval to take backup>“--selector app=<selector name>
The time interval contains 5 values
Author: Viswanth S