Containers and DevOps

Docker, Kubernetes and CI/CD pipelines turn application deployment into a consistent, documented process instead of manual work on the server. We set them up and manage them based on our experience in server administration and information security, because a container running with full privileges or a secret stored inside an image opens the door to a breach just like any server that was not hardened.

A laptop with code on a desk

Applications that run
the same everywhere

Containers and CI/CD pipelines let you update systems quickly and safely, with the same environment in development, testing and production. Every image is scanned before it goes to production, and secrets are kept outside the code.

  • Setup and management of Docker and Kubernetes
  • CI/CD and Infrastructure as Code
  • Image scanning, permissions and secrets management

Call +972-3-3801180

Who this is for

  • Development teams that want orderly deployment

    Teams that push releases to the server by hand, with no consistent process and no quick way to go back to the previous version (rollback).

  • Businesses with applications on old servers

    Systems that have run for years on the same server, where every update to the operating system or to a library (dependency) may break them.

  • Environments already running Docker

    Containers that were set up without planning, with full privileges, secrets inside the configuration files and no backup of the data.

Sound familiar?

These are the problems we run into in development environments and on application servers.

  • A version update is done by hand on the server, and only one person knows how
  • “It works on my machine”, and on the server it breaks
  • Passwords and API keys are stored inside Docker Compose files or inside the image (hardcoded secrets)
  • Containers run as root and with broad access to the host server
  • There is no backup of the data stored in the containers
  • Old images with known vulnerabilities (CVEs) that nobody scans

What the containers and DevOps service includes

The scope depends on the applications, the team and the infrastructure they run on.

  • Docker on managed servers

    Setup and management of Docker and Docker Compose environments, with updates, monitoring and backup of the data.

  • Kubernetes clusters

    Setup, deployment and monitoring of clusters, including resource, network and permission management.

  • Migration to containers

    Moving existing applications from a direct installation on a server to containers, in stages and with testing.

  • CI/CD

    A process in which every code change is built, tested and deployed the same way, with the option to go back to the previous version.

  • Infrastructure as Code

    Defining the infrastructure in files with Terraform and Ansible, so an environment can be rebuilt and you can see what changed.

  • Image scanning

    Checking images for known vulnerabilities before they go to production, and using official, up-to-date images.

  • Permissions and secrets

    Containers that run without root and with minimal permissions (least privilege), and secrets kept in a vault, not inside the code or the image.

  • Monitoring and documentation

    Tracking the availability, resources and logs of the containers, with an alert when something is not right.

What we take care of, in detail

Setup and management

  • Setup and management of Docker on managed servers
  • Kubernetes clusters: setup, deployment, monitoring
  • Migrating applications to containers
  • Managing environments with Portainer, Helm and Rancher
  • Backup of persistent data (volumes) and databases
  • Monitoring of resources, logs and availability

Automation and deployment

  • CI/CD, Infrastructure as Code, deployment automation
  • Build and deployment pipelines in GitHub Actions
  • Terraform and Ansible for defining infrastructure and servers
  • Separation between development, testing and production environments (dev / staging / production)
  • Quick return to a previous version (rollback)

Security

  • Container security: image scanning, permissions, secrets
  • Containers without root and restricted capabilities
  • Secrets management outside the code and outside the images
  • Network separation between containers and network policies
  • Restricting access to the Docker API and management interfaces
  • Minimal permissions (least privilege) in CI/CD pipelines and service accounts

From the first conversation to an organized routine

  1. 1

    Introductory call

    Which applications you have, how they are deployed today and what the team needs.

  2. 2

    Review and planning

    A review of the existing environment and planning of the architecture, the deployment process and security.

  3. 3

    Setup and migration

    Setting up the environment and moving the applications in stages, with testing at each stage.

  4. 4

    Ongoing management

    Monitoring, updates, security scans and support for the development team.

What to know about container security

A container is more isolated than software installed directly on the server, but that isolation depends on the configuration. Five things worth checking in every environment:

  1. A container running as root

    Unless configured otherwise, the process in a Docker container runs as root. If the application is breached and the container is configured with broad privileges, the attacker is very close to taking over the host server (container escape). Running as a regular user and restricting capabilities reduce the risk.

  2. Secrets inside an image

    A password or key that went into an image stays in its layers, even if it was deleted at a later stage. Whoever gets the image gets the secret too. Secrets should reach the container at runtime, from a secrets management mechanism.

  3. Images with known vulnerabilities

    Every image is based on an operating system and libraries, and any of them can contain a known vulnerability (CVE). Regular scanning, rebuilding when a fix is released and using official, minimal images keep the environment up to date.

  4. The data needs a separate backup

    The container can be rebuilt at any moment, its data cannot. Databases and files stored in volumes need their own backup, outside the server, with a restore test.

  5. Infrastructure as Code is also documentation

    When the infrastructure is defined in files kept in Git, you see what changed, who changed it and when, and you can build an identical environment after a failure. This replaces manual documentation that goes out of date, and makes oversight and meeting the change management requirements of ISO 27001 easier.

Frequently asked questions

About containers and DevOps.

Didn’t find an answer? +972-3-3801180

No. For a large share of the applications of small and mid-sized businesses, Docker and Docker Compose on a managed server are enough, and they are simpler to maintain. Kubernetes fits when there are many services, a need for high availability or loads that change.

CI/CD is a process in which every code change is built and tested automatically, and then deployed to the test environment or to production. That way every deployment is done the same way, there is a record of what went live and when, and you can go back to a previous version when something goes wrong.

In most cases yes, in stages. We check the application’s dependencies, the data it stores and its configuration, and move it to a test environment first. Some old applications are not suited to containers, and that becomes clear at the review stage.

Passwords and keys do not go into the code, into configuration files kept in Git or into the image. They are kept in a secrets management mechanism and passed to the container at runtime, with access only for the service that needs them.

We can set up and manage the servers on infrastructure we manage or in the public cloud, or work on the business’s existing servers. Either way, the host server needs to be hardened, updated and backed up, because a container is only as secure as the server it runs on.

Yes. The usual split is that your team writes the code, and we are responsible for the infrastructure, the deployment process and security. We define the process together, so it is convenient for the developers and meets the business’s security requirements.

Want an orderly, secure deployment process?

Tell us briefly about your business and what concerns you about your IT. We’ll get back to you to understand what you need and suggest a way of working that fits.

Business hours: Sunday to Thursday, 09:00 to 17:00

Existing client? Open a support ticket

Leave your details and we’ll get back to you

Your details are used only to get back to you. Privacy policy

Call +972-3-3801180Get in touch