Most juniors that come into an interview have recently finished a degree in IT, whether it’s security, architecture or engineering. Class was mostly what they expected: data structures, some programming, low-level process cost calculation, building virtual machines, service administration, how a datacenter works, data recovery, maybe some security as red-team and blue-team…

Or maybe you’re not that junior anymore, but you’ve been sitting in your current position too long, looking at an unchanging Zabbix panel for a day too long, and you need some fresh career choices? turns out, times have changed. Times have changed a lot.

Exploring uncharted territory

So the first thing you may notice by scavenging LinkedIn is that sysadmins are out of style. You don’t want a systems administrator anymore, or at least not someone who’s only a sysadmin. That’s separated from the development team, what’s called a “silo”, and “silos” are so last-gen. Now, DevOps is in!

In this search for something new, you’ve probably come across the word DevOps. We’ve talked about it in the Geko blog before, but here’s the gist of it: DevOps is essentially a philosophy, a way of working in your team, that makes those “silos” merge together and make development and environment management a lot more agile and fast-moving. No more patch Tuesdays, no more “deploying on Fridays” panic!

Now if you’re like most cases that either try to break into an IT field or want a new challenge, you might find yourself wanting to follow the security path. It’s a growing field, there’s plenty of work, entails exciting experiences every day… seems like it’s all positive! (as long as your client listens to your recommendations, of course), but pretty quickly you notice that cybersecurity is one of the fastest moving fields in the industry. It needs to keep up with changing in all of the IT aspects of a company. You’re in charge of protecting every asset around, whatever it happens to do.

What do these two fields have in common anyway?

If you follow that lead and give the thought a spin, there’s a conclusion you may come to pretty fast: DevOps and security are a very good match! integrating everything for automated checks can take work out of your hands, defining security requirements in every part of the process… it just makes sense that if you choose to follow security culture in the entire development process, it will probably take work out of you after the fact.

That thought recently gave way to a new job opening space that integrated security inside the development culture of DevOps, which we named DevSecOps, because the IT industry is about getting work done, not making up fancy names. At least we didn’t let AWS name it so we aren’t stuck with AWS DSO or something… yet.

So, let’s dive into it. DevSecOps, as its easy to recognize name presents, is a culture, a way of working, where we integrate security into the process of DevOps. This is better explained with an example: Imagine you have a pipeline that tests your code before you build and publish it to test if it works as intended: unit testing, code analysis…

Well, you can do something similar with the rest of the environment, like for example analyzing if the infrastructure the code is gonna run on is well configured and has no security problems by analyzing your Terraform declarations for encryption missing in a volume, or an unrestricted security group. If the alert is raised before the infrastructure is built, you don’t have to fix it later!

I like this idea. How do I implement it?

The entire idea can be summarized into a simple concept: Security isn’t a toggle you can click. You don’t apply security efficiently by installing that software the vendor recommended to you. Security is work culture. A continuous process that is better built into your development pipeline, preferably with automated checks that tell your team that something needs changing. No deployment with security holes in your ops team’s watch. But even then, maybe you don’t need ops intervention, since your developer may just get notified of this security flaw that needs fixing before deployment. This entire thought process is about breaking the concept of separated teams and making departments more connected and cohesive.

Isn’t my infra setup a bit too old-school for this?

Even if your infrastructure seems too legacy to adapt into the DevOps way of working, DevSecOps could be important. Uploading some Ansible playbooks to GitHub? Maybe pass them through a security analysis module when they get pushed out as a pre-commit hook. Built your own docker images for some specific task? Maybe you want to give them a spin through an image analyzer like Snyk or docker scan (did you know Docker had its own vulnerability analyzer? I didn’t!). Are you moving some infrastructure into terraform code? Bridgecrew integrates into pretty much any provider to alert you of that slip of “allow 22/tcp from 0.0.0.0/0”.

Any small step is a big move towards making work easier for your developers in the long run in avoiding technical debt and lifting load from your ops and admin team from these janitor tasks so they can focus on the really important tasks in your organization. Also worth noticing these tools are far cheaper than an incident response spending. Certainly in money, maybe in public image. I’d gladly take some cheap AWS Security Hub alerts over a GDPR fine.

I’m in, let’s chat.

Are you new to all this and you want to learn? Do you want to bring your DevOps knowledge to a new challenging ground? Here at Geko we’re always looking for talent from any expertise level.

Have you been thinking about getting up to speed on your infrastructure security? Well, maybe you should. And we at Geko Cloud could help you with that. At Geko Cloud we are specialists in Internet platforms, cloud infrastructure management and microservices. Contact us without any commitment and we’ll have a chat about stepping up your operations game.

La entrada What is DevSecOps? se publicó primero en Geko Cloud.

Before we dive into Kubernetes, first of all, you need to know what container orchestration is. Container technologies have radically changed the landscape of systems and the way software is packaged and deployed. Some of the benefits that containers bring are portability, agility, speed, immutability, and fault isolation.

A container orchestrator is a software that manages and coordinates containers in an automated way. There are several container orchestration tools such as Docker Swarm, Google Container Engine, Amazon ECS, and others. However, in this post, we will focus on Kubernetes, where we will explain the concept, most notable components of the tool and discuss the benefits that Kubernetes can offer, among other points.

Definition – What is Kubernetes?

Originally developed by Google, Kubernetes, or k8s for short, is a container orchestration tool. Kubernetes facilitates the deployment and operation of applications in a microservices architecture. It does this by creating an abstraction layer on top of a cluster of hosts, so development teams can deploy their applications and let Kubernetes manage the deployment of containers.

Platforms that offer Kubernetes

There are several cloud platforms that offer Kubernetes as a service. These platforms make the job easier by providing an interface that makes it easy to deploy applications on Kubernetes without having to worry about configuring and managing the various components of the cluster. Some of them are Amazon EKS, Digitalocean, OpenShift, or Rancher, among others.

Some Kubernetes cluster elements

Kubernetes has a number of features that allow you to provision and deploy your own containerized software. If you’re new to Kubernetes, the terminology can be new, and require some extra learning. Here are some of the basics:

• Pods: The minimum unit that can be deployed with Kubernetes. Each pod can contain one to several containers running on the same shared storage/network resources as the pod.
• Nodes: A physical or virtual machine that hosts the pods that perform the workload of an application. 
• Control plane: The control plane runs the Kubernetes components that provide the core functionalities: exposing the Kubernetes API, scheduling workload deployments, managing the cluster, and direct communications throughout the system. 
• Cluster: A group of nodes working together, which run containerized applications. Clusters consist of master and worker nodes. There can be one or more master nodes and zero or more worker nodes. For example, you can have several nodes in the same cluster running the same containers.  
• Deployment: Kubernetes deployments define the scale at which you want to run your application by allowing you to set the details of how you want pods to be replicated across Kubernetes nodes. Deployments describe the number of identical pod replicas you want to run and the preferred update strategy for updating the deployment, among other things. Kubernetes will track the health of the pods, and remove or add pods as needed to bring the application deployment to the desired state. The deployment provides an abstraction layer that allows pods to be replaced easily and transparently. Pods in a deployment can be located on different nodes.
• Service: A set of pods running the same application or microservice can be grouped together to form a deployment, as we have already seen. Since these pods can be replaced and, due to the dynamic nature of Kubernetes, the different IP addresses of the pods will change, there is a need for a network resource to establish an entry point to these pods. A service abstracts away the underlying network complexity, making it possible to provide a single, unchanging entry point while making the layout of the pods that make up the deployment transparent.
• Ingress controller: It is software that provides reverse proxy functionality, configurable traffic routing, and TLS termination for Kubernetes services. A gateway driver is installed on the cluster, and then gateway rules are configured for a specific service or services.
• Kubectl: a command-line interface that sends a request to the Kubernetes API, either with specific commands, with the contents of a YAML manifest, or with data fetch requests.
• Kubelet: is a service running inside each node, which communicates with the control plane.

There are other Kubernetes components such as daemonsets, namespaces, replicaSets, secrets, and even custom resources. The ones mentioned here are the ones you are most likely to interact with when deploying applications on Kubernetes.

Learn more about when and how to use Kubernetes  

Do you want to know more about k8s? In our Youtube channel, we explain you from a business perspective, what needs it covers, its advantages, and when to use it.

Geko and Kubernetes – Why choose Geko Cloud?

If you are using or considering using containers to streamline building, scaling, and deploying your microservices-based application, Kubernetes gives you the ability to manage the infrastructure using declarative YAML files.

Container lifecycle management with Kubernetes using your deployments and operators along with a DevOps approach allows software development and IT operations to adapt to support the CI/CD channel. At Geko Cloud we are at your disposal if you are looking for a partner to implement Kubernetes, migrate to the cloud, move to a microservices model or manage your platform in the cloud. Contact us to find out more about our services.

La entrada What is Kubernetes? se publicó primero en Geko Cloud.

DevOps is a term derived from the combination of “development” and “operations” that represents an engineering philosophy consisting of a collaborative approach between the software development (Dev) team and the software operations (Ops) team.

In its broadest meaning, DevOps is a culture. The aim of this type of methodology is to increase communication and trust between developers and system administrators, i.e. to integrate the operations and development departments. At Geko Cloud we use agile methodologies and we integrate ourselves in all stages of the application lifecycle to deliver products as quickly as possible and manage all incidents that may arise to make the appropriate corrections in each situation. 

DevOps model

With a DevOps model, the development process, from the idea to the software in production, provides organisations an increased organisational capacity when developing an application and, as a consequence, offers an increase in speed and added value that allows companies to compete more efficiently.

DevOps practices

To establish a correct link between development and operations, DevOps engineers have to carry out different specific techniques. Some of the most recommended for the implementation of the aforementioned concepts are continuous integration and deployment, APIs or microservices, monitoring, systems as a code, communication, and collaboration. With all this, development and operations engineers will be much more efficient when working on any project and, therefore, it will make it faster to develop the overall application as a whole.

Advantages of using DevOps

As we mentioned before, applying the DevOps methodology in a company will bring many benefits when it comes to working and creating tools applying agile methodologies.

Communication and collaboration: The cornerstone of applying the DevOps methodology correctly is good communication and collaboration between developers and operators (and even other teams), establishing a workflow that improves productivity and software delivery processes through builds, validations and deployments.

Speed: Another benefit is the delivery of frequent updates, which generates less downtime and, above all, allows problems to be solved in less time. DevOps practices help to develop and improve the product faster, which directly affects its marketability and is a competitive advantage.

Agility: Development using agile methodologies is complemented by the DevOps philosophy to optimise the entire software development cycle through to deployment, with an emphasis on iterative, incremental, and evolutionary development, combined with infrastructure provisioning, continuous monitoring, and supporting applications in a production environment. All this in an automated way.

Security: With the increasing number of threats, securing the application is one of the most important aspects. With a DevOps model we can use a set of tools to perform automated security tests integrated with our continuous integration process, ensuring the security of our platform.

Customer first: Thanks to agile methodologies this is easier than ever, as by continuously integrating and deploying, changes in customer tastes can be detected quickly, adapting the application to them in a fast and agile way.

How CI and CD improve your development cycle

DevOps practices such as continuous integration and continuous delivery enable DevOps teams to deliver code quickly, regularly, securely and reliably.

Continuous integration is an agile software development practice where code changes are introduced and merged into a common repository, and the consistency of that integration is verified by automated testing to detect any bugs in the application.

On the other hand, continuous deployment goes one step further, taking care of the deployment of the new code as well as the provisioning of any necessary infrastructure, all in an automated way to make the process secure, and can even integrate an automatic rollback policy if something doesn’t go according to plan.

In summary, CI/CD enables DevOps teams to frequently validate and deliver applications to the end user through automation throughout the application lifecycle, from development to production deployment. Common tools for CI, CD or both include Jenkins or Spinnaker, as well as proprietary version control platform solutions such as Github actions or Bitbucket pipelines, to name a few.

With Geko, your deployment will stop being manual, repetitive, and error-prone and become automated, fast, and secure.

Geko and DevOps

At Geko Cloud we are specialists in Internet platforms, cloud infrastructure management and microservices. Contact us without any commitment. 

[:es]

La entrada What is DevOps? se publicó primero en Geko Cloud.

• Experience with scripting languages: To get into the DevOps world it is very important to have a solid programming base even without being an expert developer. The most relevant languages nowadays for DevOps-related tasks are Bash and Python, although at Geko we recommend having knowledge of some additional languages such as: Go, C, C++, PHP, Ruby, Node.js or PowerShell. Although we will not be programming, we will need to know the technologies that developers work with to be able to implement integration pipelines, as well as to develop our own tools for the automation of some processes.

• Containers and container orchestration: Many companies are moving away from traditional application deployment models to transition to a microservices-based environment (typically containerised systems). The advantages of using containers are manifold, from ensuring that the same thing that is tested in development will work exactly the same in all environments, to more easily automating the deployment of code in production. It is therefore important to be aware of tools for container administration and management, some of these tools include: Docker, Kubernetes, Docker Swarm, ECS and many more. 

• Security Skills: This is one of the points that add the most value as a DevOps professional. Engineers must have the skills to write secure code to protect applications from unwanted attacks. Faster development times lead to a higher risk of more vulnerabilities being introduced into the code.

• Web servers: Web servers are used to satisfy users’ requests for content on a website. If you are interested in the DevOps world you have probably heard that there are different types of web servers, so we mention the most popular ones: Nginx, Apache, IIS and Tomcat.

• Infrastructure implementation as code: Regardless of the environment or operating system, good DevOps must have a solid knowledge of infrastructure and operating system management, and be able to automate the deployment and configuration of infrastructure using infrastructure tools as code. The most relevant tools in this sector are Terraform and CloudFormation, although the latter is only suitable for AWS.

• Configuration automation as code: Whether it’s provisioning applications and their configurations, creating users, resources, automating system administration tasks, configuration automation tools allow you to maintain a consistent state over time and across the managed infrastructure. Some of the most popular tools for this automation are Ansible, Chef, Puppet and Salt.

• Implementation of CI/CD deployments: For this role you will need a deep understanding of the essence of DevOps: the implementation of deployments, known as CI/CD. All code is merged and finally the build is executed and tests are automated. Deployment to production will mostly require the creation of new containers, automating the processes through scripting. Some tools you should be aware of are: Gitlab CI, GitHub Actions, Bamboo, Azure DevOps, Jenkins, Travis CI, TeamCity and Circle CI.

• Cloud Computing: Cloud and DevOps usually go hand in hand. A DevOps engineer is expected to know how to handle the different cloud platforms and their tools to better adapt to the needs, and find solutions for each client or project. In addition, they will also need to know the different cloud platforms to weigh the pros and cons of using IaaS versus PaaS services, and other managed services to design and recommend solutions. Platforms such as AWS, Azure, Google Cloud Platform, etc. should be familiar tools for a DevOps engineer.

• Infrastructure monitoring: One of the fundamental parts of the DevOps job is to know what is going on at all times in the development process. Therefore, monitoring the infrastructure is an essential task, as it allows users to visualize events and receive real-time alerts. Some of the DevOps tools for monitoring, which help development and operations teams work together effectively, are: Prometheus, Grafana, Sensu, SysDig, and New Relic Infrastructure. 

• Agile methodologies: A DevOps engineer must master agile methodologies that allow iterative and incremental development. The core of this methodology is iterative development with an incremental and evolutionary approach. This means that software development is divided or fragmented into sprints or smaller tasks. For this reason, there are methods such as Kanban or Scrum, and tools that offer this type of methodology such as Jira.

• Soft skills: It is not enough to be good at coding and automation. A DevOps profile also implies that you must have soft skills such as communication, flexibility, learning, among others. As a DevOps engineer, you have to collaborate with developers, the QA team, operations teams and high-level stakeholders in the company. You may also have to involve third parties and, of course, the end customer. For that reason, soft skills are just as important as technical skills.

• • Collaboration and Communication: Given his or her position, a DevOps engineer must have the ability to work as part of a team, so collaboration and communication are crucial. A DevOps engineer must provide cross-functionality, i.e. break down the barriers between IT operations and development. This means that DevOps engineers have to work closely with software engineers. This requires excellent communication and collaboration skills for anyone wishing to perform this key role of a DevOps engineer.

• • Flexibility: To be a good DevOps engineer, being flexible is one of the most important characteristics, having the ability to continuously develop and integrate new systems and operations while adapting to changes in the code. In addition, engineers must be comfortable working in different areas as required in the application development process.

In conclusion, a DevOps profile can be a developer who has entered the world of system administration, gaining experience in operating system management, networking, software provisioning and configuration, etc.; or it can be a sysadmin who has entered the world of development, knowing at least a couple of programming languages and the requirements to make the software work. As you can see, the DevOps engineer profile is very versatile.  At Geko, we consider a good DevOps has to be someone who has knowledge of both worlds, regardless of their background.

From Geko, these are some of the skills and knowledge that we believe a DevOps expert should have, what would you add or remove from this list?

In Geko Cloud we are experts in DevOps methodologies, if you want to know all the possibilities of having a DevOps team at your disposal, do not hesitate to contact us. 

La entrada Some skills that every DevOps expert should have se publicó primero en Geko Cloud.

1. Source code management
Using the DevOps strategy, one of the initial steps when developing an application is to build the code. All applications have a code that runs in the background and must be updated according to some previous requirements, therefore, it is essential to manage the source code. The most notorious tools in this section are:
2. Containers
Containerisation is the method by which developers package applications and their dependencies within a container, which allows them to isolate the entire application environment so that there is no interference with other environments or libraries, and allows them to reduce the resources required as they reuse the operating system layer (unlike virtual machines). This reuse also reduces the start-up time by several orders of magnitude, which accelerates the scaling speed, and therefore decreases the response time to load surges. Some of the most popular containers are the following:

3. Testing
The next step, when an application is developed, is to check that it works correctly. This is one of the most important stages for the development and implementation of software in a fast and agile way, as it is carried out throughout the life cycle and allows us to know if there are any errors. During the life cycle of the code, various tests and quality controls can be performed, but basically it is checked to find out if there are any errors in the application and to resolve them. If there are any, the application returns to the software development life cycle. Within software testing there are different levels of testing divided into automated testing and manual testing. Some of the tools are described below:
4. Database automation
The database is a fundamental aspect in any type of application implementation process. As it is inefficient for developers to systematically perform management tasks on them, automated processes are implemented for their configuration, data entry, etc., thus reducing errors in deployments, improving speed and increasing reliability. Some of the most commonly used tools for this purpose are:
5. Continuous integration
Continuous integration is an agile software development practice. In continuous integration, code changes are introduced and merged into a common repository. Each addition is verified and run through various levels of automated testing to check the application for bugs or damage. Some of the most commonly used continuous integration servers are shown below:
6. Analytics
Analytics is used to evaluate the data stored by an application. The use of these tools is mainly to analyse and generate reports. There are currently many tools that are used to analyse data, but the best known in the DevOps industry are:

7 . Deployment
Once the application has been analysed and is ready to go into production, the next stage is deployment. In this phase, different tools are used based on the structure of the application. The main tools used in this stage are:
8. Cloud
Of all the services used in computing today, file storage in the cloud is perhaps the most important. All data can be accessed, run and stored in the cloud. There are many providers today, but here are some of the most popular ones that can be used.

9. Monitoring
Once the application goes into production, it is imperative to examine the application to make sure that it is performing well, that all functionalities and highlights are working as intended, among other things. Therefore, the following tools can be used to constantly monitor applications:

10. Release Orchestration
Release orchestration is a way to organise, automate and manage the end-to-end release of software. These tools help automate CI/CD processes, and also allow you to exploit to the fullest extent the tools that may have been used during software development. Some of the release orchestration programs are:
11. Configuration management
Configuration management is a method by which different changes can be dealt with on an ongoing basis. This cycle ensures that integrity is maintained at all times and that the current state of the system is in the best possible state. The following are the main tools used in configuration management:

12. Collaboration
Collaboration across applications is important in today’s market. If you only use one application for one purpose it is not very useful, but if you create a collaboration between different pieces of software, it is much more beneficial for both. So here are the main tools you can use to collaborate with your software:
13. Security
With the increasing number of threats or dangers, protecting your application is one of the most important aspects. There are different strategies and technologies that can protect your application from different types of attacks. The main tools that can be used to secure the application are:
14. Artificial Intelligence Operations
The term AIOps is used to denote the analysis of big data and learning from other AI technological advances. It can be used to analyse information from an application by using different concepts, such as Big Data and Machine Learning. Some of the most prominent tools on the market today for AIOps are:
With this, we come to the end of the periodic table of DevOps tools, these were some of the most used by DevOps professionals in each phase of the lifecycle in the development of an application or program. Now you just have to choose the DevOps tool that best suits your needs depending on the stage you are in.

Let us know in the comments which DevOps tools you use the most, or if you have doubts about which tools to use, let us know and we will advise you which ones can best suit your needs.

La entrada Discover the periodic table of DevOps tools se publicó primero en Geko Cloud.

The DevOps methodology, as you probably already know, unifies the work of software development (“dev”) and the operations part of it (“ops”), in order to cause an exhaustive monitoring and automation in all stages of the software of any type of product. That is why any company (ecommerce, Fintech, pharmaceutical, consulting, training…) is susceptible to turn to “DevOps as a service“, as it will cause a development of any type of software faster and with better quality.

But…

Why is it a good decision to have an external DevOps team?

1. Hiring a team of DevOps specialists internally can be a very complex and costly task. Bearing in mind that, as the project progresses, you may need different skills from this profile, having a DevOps consultancy means that you can have at your disposal different experts in tools and technologies that are undoubtedly being updated every day. You may decide to migrate your platform to the cloud with the provider Amazon Web Services or Azure, but at a more advanced stage of the project you may also decide to implement Kuberentes, something that the DevOps consultancy will be able to satisfy with one of its experts who have the necessary certificates and experience more easily than it would take you to train an internal employee or hire a new specialist.
2. Outsourcing DevOps consulting will improve the productivity of your development team thanks to the progressive optimisation of their work, while your development team is focused on improving the product and implementing new features, the DevOps team will be dedicated to managing it in the cloud, making the product more stable and efficient, offering continuous support.

What to look for in a DevOps team?

• Good communication: it is essential to have fluent and ongoing communication between the development team and the DevOps team for the correct execution of good practices in the day-to-day development of the product. At Geko, we maintain agile and continuous communication channels with each client, which allow us to know the status of the developments, as well as the state of the business at all times, working in an aligned and coherent way.
• A dedicated Technical Account Manager: having a DevOps reference for the project increases the stability and knowledge of the project. The DevOps consultancy can assign the person who is an expert in the technologies that best suits your project, such as an expert in Kuberentes or an expert in Azure, etc. At Geko we have experts certified in the main cloud providers and with experience in designing and building architectures.
• Adaptability: when hiring a DevOps service there are no closed options, it is about finding experts who adapt at any time to the needs of your product, according to its development cycle, using the technologies and cloud providers that best suit the characteristics and needs of the product. At Geko we are not sellers of any cloud provider, we develop a plan tailored to your needs in order to obtain the best results.
• Continuous monitoring: A DevOps expert should set up all kinds of automatic testing for your platform instead of employing a person to check every page of your application. This will foresee problems in the development cycle, deployments, servers, performance and vulnerabilities. At Geko, we also have 24×7 support that guarantees the solution of incidents in a maximum time of one hour.

Conclusion

Having “DevOps-as-a-service” allows you to take advantage of delegating all the tasks related to the management and maintenance of the system to the DevOps consulting company. You will achieve the automation of solid processes that will allow you to eliminate bottlenecks in software development so that the team can go full speed ahead with its sprints.

At Geko we are at your disposal to make a first assessment of your architecture without obligation and see if we can help you.

Contact us at sales@geko.cloud!

La entrada Why outsource DevOps? se publicó primero en Geko Cloud.

You probably already know something about what Kubernetes is, or you’ve heard of it, but if you don’t quite understand the advantages of this powerful tool, in Geko we want to guide you.

As you may already know, Kuberentes is a container orchestrator that allows you to deploy your production applications to the cloud in an automated way. It was developed by Google and subsequently donated to the community, making it an Open Source project.

With Kubernetes, multiple parts of the same application can run in isolated containers, so if one part of an application becomes inoperative, only that part can be restored instead of the entire server. This saves time and increases productivity when developing applications and putting them into production.

At Geko Cloud we are experts in Kubernetes and the use of microservices architectures, something that addresses both the need to make better use of computing resources and the need to maintain increasingly complex web applications.

What are the advantages of using Kubernetes in your business?

We will tell you some of them:

• Unify the deployment model.
• Increases accountability and autonomy of the development team.
• Achieves high-speed horizontal growth, i.e. scalability, in addition to vertical node autoscaler and HPA.
• DRP or business continuity.
• Kubernetes is a cutting-edge technology, but it has been around long enough to warrant its use, and there is a large community behind it to support it.
• There are a number of cloud-managed K8s platforms that allow you to eliminate complexity.
• It is cloud agnostic, offering scalability between environments and infrastructures.
• It provides tracking and security.

But you also need to know when not to use Kubernetes

As we indicated at the beginning, we want to guide you on when to use or not to use Kubernetes and what to consider when using it.

• You should keep in mind that Kubernetes needs an initial implementation and operational cost.
• It is advisable to implement it as a business model not as a platform.
• Operating a Kuberentes cluster without Cloud as the management layer adds some complexity, if a whole K8S cluster goes down, everything will go down.
• It is a platform that was designed for small stateless apps and their interconnection, not designed to deploy DB infrastructure or other high-risk infrastructures. But with the improvements in high availability and new features it allows more and more structures to be brought in internally. The new stateful support mitigates this.

Learn more about when and how to use Kubernetes in our webinar

Watch it here:

We hope you find it useful to learn more about Kubernetes and we encourage you to subscribe to stay up to date with new content.
At Geko Cloud we are at your disposal if you are looking for a partner to implement Kubernetes, migrate to the cloud, switch to a microservices model or manage your platform in the cloud.

Contact us to learn more about our services, thank you for reading and leave us your comments!

La entrada What is Kubernetes and when to use it se publicó primero en Geko Cloud.