Ned Bellavance’s Post

🔄 GitHub Repository Update: I have completed the Terraform-Docker-Kubernetes-Multi-Env-Deployment repository. 🌟 Highlights: > Easily manage your Docker and Kubernetes deployments across five different environments using Terraform-Terragrunt. > Deploy your infrastructure easyly with go test. > Follow the step-by-step README.md file for guidance. 🛠 Tools / Software Versions: Go: 1.23.3 Terraform: 1.9.6 Terragrunt: 0.69.0 Terratest: 0.47.2 Docker: 27.2.0 Kubernetes: v1.30.2

🔄 GitHub Repository Update: I have upgraded my Terraform repository with advanced infrastructure management capabilities: 🌟 Improvements: 1. Implemented multi-environment deployments using Terragrunt 2. Added comprehensive testing framework with Terratest 3. Streamlined environment-specific configurations 🛠Tools / Softwares Versions: Go =>1.23.3 | Terraform =>1.9.6 | Terragrunt => 0.69.0 | Terratest  => 0.47.2 Link: https://lnkd.in/dXhJD-u9

𝗜 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗱 𝗮 𝗱𝗼𝗰𝗸𝗲𝗿 𝗼𝘂𝘁𝗽𝘂𝘁 𝗳𝗼𝗿𝗺𝗮𝘁𝘁𝗲𝗿 𝘁𝗼 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗲 `𝗱𝗼𝗰𝗸𝗲𝗿 𝗽𝘀` 𝗼𝘂𝘁𝗽𝘂𝘁 `docker ps` and `docker ps -a` are perhaps the most used commands for software engineers to view containers & their statuses. The output of these two commands is descriptive & well defined. Still, this list gets messy & bit unreadable when the number of containers increases & each containers have multiple ports mapping. This may sometimes lead to a line break of container information & the list gets a bit unreadable. That is why I thought to make a docker output formatter to view the list in a more organized way. 💫 𝗙𝗲𝗮𝘁𝘂𝗿𝗲𝘀: • The container list & statues are shown in a proper tabular format with proper spacing between each line to show proper separation between containers • It shows the port mappings each in a new line. So if one container has multiple port mappings, it will show you each in a comma-separated one line. This avoids the wrapping issue from the default command 🛠️ 𝗛𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀: • I wrote the formatter in Go, compiled it into an executable, and placed it in my system's executable path • Then I customized my shell configuration to create a custom command `docker fps` & `docker fps -a` which stands for "formatted ps" This is a small, practical tool that helps me quickly and clearly see the status of my Docker containers. This is nothing fancy, but I found it useful for me to view my containers list & statues. 👋 Feel free to look into the Github repo & try it out if you think it might be useful for you too! Github repo: https://lnkd.in/g-eXQvEF

Hello Everyone Good Evening, These are the important terraform commands: 1. terraform init: Command downloads plugins, set ups the backend & make directory as terraform environment 2. terraform plan: command display execution plan 3. terraform apply: command do CRUD operation of resources 4.terraform destroy: used to clean up the current tf environment/directory 5. terraform validate: validates the syntax error 6. terraform fmt: format the tf file with proper indentation 7. terraform stat: this will list all the tf resources stored in the tf state file 8. terraform import: this will help to import the configuration changes on resources which is done by manually into tf env, to synchronise the resources state 9. terraform taint: used to force recreation of already existing resources, without modifying the configuration 10. terraform untaint: opposite of tf taint 11. terraform show: display the infra details in human readable format 12. terraform graph: Generates visual representation of tf resources 13. terraform version: display the version of tf 14. terraform lock: manually lock the state file, to avoid infra conflicts note: terraform locks the tf state file by default. 15. terraform force_unlock: to remove the lock on the state file Thanks for reading .

Day 2 Terraform commands to save the output to a file. 1.Saving the Plan Output The terraform plan command generates the execution plan in terraform. To save this plan to a file for later use or review. terraform plan -out=tfplan (name of the file) You can then apply this saved plan later with: terraform apply tfplan 2. Exporting the Plan in a Readable Format terraform plan >output.txt (name of the file) 3.Saving Terraform apply logs terraform apply >apply.txt (name of the file) If we want to include both output and errors: terraform apply >apply output.txt 2>&1 4.Logging State Information To output the state of the terraform infrastructure to the file by using terraform show terraform show >state_output.txt Exporting terraform output values To save the terraform output value to a file terraform output >outputs.txt For a specific output variable: terraform output variable_name > variable_output.txt Automating with a Script To automate saving all key outputs to files, you can use a shell script: #!/bin/bash terraform plan -out=tfplan terraform show -json tfplan > plan.json terraform output > outputs.txt

#helm - CVE-2024-26147 - CVSS 7.5 "Helm is a package manager for Charts for Kubernetes. Versions prior to 3.14.2 contain an uninitialized variable vulnerability when Helm parses index and plugin yaml files missing expected content. When either an `index.yaml` file or a plugins `plugin.yaml` file were missing all metadata a panic would occur in Helm. In the Helm SDK, this is found when using the `LoadIndexFile` or `DownloadIndexFile` functions in the `repo` package or the `LoadDir` function in the `plugin` package. For the Helm client this impacts functions around adding a repository and all Helm functions if a malicious plugin is added as Helm inspects all known plugins on each invocation. This issue has been resolved in Helm v3.14.2. If a malicious plugin has been added which is causing all Helm client commands to panic, the malicious plugin can be manually removed from the filesystem. If using Helm SDK versions prior to 3.14.2, calls to affected functions can use `recover` to catch the panic." Latest releases : https://lnkd.in/ezxhkDK6 Current version : 3.14.2 Link to nist website : https://lnkd.in/e-khSaRz

🔍 Recently came across an insightful article on 𝚍𝚘𝚝𝚗𝚎𝚝–𝚜𝚞𝚋𝚜𝚎𝚝 by Ted Spence. He shared, "Using this approach, I was able to shrink my build times from 400 seconds down to about 120 — and in some cases, as little as 30 seconds!" 🕒💡 Glad to see it's benefiting others in streamlining their Docker workflow with .NET applications. Your feedback motivates me to keep refining it. 💪 Stay updated on new versions by starring the GitHub repository: https://lnkd.in/enb3Pu4U 🌟 𝚍𝚘𝚝𝚗𝚎𝚝–𝚜𝚞𝚋𝚜𝚎𝚝 has been downloaded 274K times since its release 20 months ago. 📈 For the full article, check out Ted's insights here: https://lnkd.in/eRmvAAGR 📚✨ Let's continue enhancing our Docker experience together! 💻 #DOTNET #Docker #Optimization

The decision-making process involving the use of RUN, CMD, and ENTRYPOINT, along with the choice between shell and exec forms, showcases Docker’s intricate nature. Each command serves a distinct purpose in the Docker ecosystem, impacting how containers are built, operate, and interact with their environments.

Inspired by the Kubernetes itself and ArgoCD I was working on the Deployment and GitOps orchestrator for the single host Docker daemon. Features I like: - Reconciliation loop for containers and GitOps - Embedded DNS server discovering new containers - Apply definitions to the remote server via mTLS - Declarative definitions for containers, gitops, configuration, resource... Often stuff is deployed on cheap virtual machines and I missed the elegance of the deployment and overview since I got used to the Kubernetes itself a lot. Docker compose itself doesn't provide a declarative way to do things around the remote hosts and also doesn't have GitOps. So I made something usable (still pretty unstable) but it's getting shape, to upgrade the experience. Documentation is still scarce but there are traces of it. Quick start guide: https://lnkd.in/ezJKdFQ4 Github repository: https://lnkd.in/eqFB4dhe

Below are the some useful commands in terraforms. 1. Terraform init: Initializes a Terraform working directory by downloading the necessary provider plugins and setting up the backend. terraform init 2. Terraform plan: Creates an execution plan showing what Terraform will do when you apply the configuration. It compares the current state with the desired state. terraform plan 3. T apply: Applies the changes specified in the Terraform configuration to reach the desired state terraform apply 4. Terraform destroy: Destroys the infrastructure defined in the Terraform configuration, effectively tearing down all resources. terraform destroy 5. Terraform validate: Validates the Terraform configuration for syntax errors and other basic errors. terraform validate 6. terraform fmt: Rewrites Terraform configuration files to a canonical format with consistent indentation and formatting. terraform fmt 7. Terraform show: Outputs the current state or a saved plan in a human-readable format. terraform show 8. Terraform state: Performs operations on the Terraform state, such as listing resources or moving resources to a different state file. terraform state list