Operations | Monitoring | ITSM | DevOps | Cloud

DevOps

The latest News and Information on DevOps, CI/CD, Automation and related technologies.

Simplify your Code with Helmfile

You’ve got Helm deploying Charts via Codefresh but now how do you deal with Helm chart dependencies? There has to be a better solution than a Chart of Charts? How do I DRY out my Helm charts and simplify my Codefresh Pipelines for multiple environments? How do I create secrets in Codefresh? Is there another way than using Encrypted Secrets / Environment Variables?

How tech teams are making extraordinary progress in COVID-19 shutdown while working remotely?

COVID-19 has led businesses into extreme work challenges. To overcome these challenges, companies have shifted their working patterns and have embraced Remote Work to avoid any negative impact on employee’s health as well as the business. COVID-19 has made IT-sector office culture’s shift to remote work prominently. The tech teams, who already have DevOps processes in place, got huge benefits and did not get much impact while shifting their workplace from regular office to home.

Optimizing container workload infrastructure while respecting instance-level dependencies

Ocean by Spot continuously makes sure that all pods’ requirements are met so they can be scheduled by Kubernetes on the right nodes, with intelligent bin packing for optimized resource usage. In some use cases there are instance level dependencies, such as: To ensure that these instance level dependencies are met, we are pleased to share that Ocean launch specifications now supports a maximum number of instances allowed to run concurrently.

Scaling OpenShift Container Resources using Ansible

Assume you have a process to determine the optimal settings for CPU and memory for each container running in your environment. Since we know resource demand is continuously changing, let’s also assume these settings are being produced periodically by this process. How can you configure Ansible to implement these settings each time you run the associated playbook for the container in question?

Getting SRE Buy-in from C-Levels for Error Budgets and SLOs, Part 3

You now have postmortems properly implemented, automated, and well-structured. You’re generating reports and data automatically based on all your incidents. Two levels of management have agreed to your SRE buy-in efforts. That is a huge accomplishment! If you’re here, you’re making great traction adopting SRE best practices, but the battle is not won yet. The hardest but most strategic, important effort will be proving to your C-levels why they should buy into SRE.