登录查看更多内容

How do you test and validate your containerized applications and orchestrators before and after deployment?

由人工智能和领英社区提供技术支持

Containerization and orchestration are two key concepts in modern application architecture, but how do you ensure that your applications run smoothly and reliably in different environments and scenarios? In this article, you will learn how to test and validate your containerized applications and orchestrators before and after deployment, using some best practices and tools.

在这篇协作文章中查找专家回答

由社区从 8 条内容中精选。了解更多

1 Choose the right testing framework

The first step is to choose a testing framework that suits your needs and preferences. There are many options available, such as Jest, Mocha, PyTest, or NUnit, depending on the programming language and the level of testing you want to perform. A good testing framework should allow you to write unit tests, integration tests, end-to-end tests, and performance tests, as well as generate reports and coverage metrics.

添加您的观点

Paul Sweatte
举报内容
A testing framework which is written in a domain specific language (DSL) is an option if you want portability, since many DSLs have implementations in several programming languages. The Test Anything Protocol (TAP), ShellSpec, and Gherkin are examples which can be used individually or combined as part of your testing framework.

已翻译

赞
Giovanni Guarino

CyberSecurity Passionate & CISO
举报内容
You can create a testing kubernetes cluster following you needing. I have created a master and two workers nodes. This is the easy way

已翻译

赞

2 Mock and isolate dependencies

The second step is to mock and isolate the dependencies of your containerized applications, such as databases, APIs, or other services. This will help you to test your applications in isolation, without relying on external factors or network connectivity. You can use tools such as Docker Compose, MockServer, or WireMock to create mock services and networks, and run them locally or in a CI/CD pipeline.

添加您的观点

Paul Sweatte
举报内容
Critical dependencies should be tested in isolation without mocking, such as expired certificates, insufficient disk space, or revoked credentials. These are important to test in order to document and implement failsafe mechanisms proactively.

已翻译

赞

3 Test your containers and images

The third step is to test your containers and images, to ensure that they are built correctly, configured properly, and comply with the best practices and standards. You can use tools such as Dockerfile Linter, Container Structure Test, or Hadolint to check the syntax, structure, and security of your Dockerfiles and images. You can also use tools such as Docker Bench, Anchore, or Clair to scan your images for vulnerabilities and compliance issues.

添加您的观点

Paul Sweatte
举报内容
Testing containers from a hardware requirements standpoint is important as well. Gather the CPU, memory, and storage required to build an image by testing the build process locally on multiple machines, from a system on a chip to a dedicated server. This will allow you to estimate the costs, especially if your continuous integration process is in the cloud.

已翻译

赞

4 Test your orchestrators and clusters

The fourth step is to test your orchestrators and clusters, to ensure that they can manage and scale your containerized applications effectively and efficiently. You can use tools such as Kubernetes Test, Helm Test, or Kubeval to test the functionality, configuration, and validation of your Kubernetes resources and charts. You can also use tools such as Prometheus, Grafana, or Jaeger to monitor and troubleshoot your orchestrators and clusters.

添加您的观点

Paul Sweatte
(已编辑)
举报内容
Depending on your disaster recovery strategy, how you test your backup, failover and recovery mechanisms will vary. If your cluster includes persistent storage, compliance with legal restrictions may need to be taken into consideration as well.

已翻译

赞

5 Test your deployment and delivery

The fifth step is to test your deployment and delivery, to ensure that your containerized applications and orchestrators can be deployed and updated smoothly and reliably. You can use tools such as Jenkins, Travis CI, or GitHub Actions to automate your CI/CD pipeline and run your tests in different stages and environments. You can also use tools such as Argo CD, Flux, or Spinnaker to implement GitOps and continuous delivery for your containerized applications and orchestrators.

添加您的观点

Paul Sweatte
举报内容
Test the cost of your deployment process in addition to the technical aspects. This is critical to ensure you have predictable costs in addition to predictable delivery.

已翻译

赞

6 Test your user experience and feedback

The final step is to test your user experience and feedback, to ensure that your containerized applications and orchestrators meet the expectations and requirements of your customers and stakeholders. You can use tools such as Selenium, Cypress, or Puppeteer to automate your UI testing and browser compatibility testing. You can also use tools such as Google Analytics, Hotjar, or UserTesting to collect and analyze user feedback and behavior data.

添加您的观点

Paul Sweatte
举报内容
Performance issues that are raised during testing require in-depth knowledge of the chosen architecture as well as the underlying hardware. Intermittent crashes and process failures in particular are potential showstoppers during the testing process. In order to build confidence within the team and across the organization, it is critical to focus on stress testing as a development team before moving on to user experience testing as a cross-functional exercise.

已翻译

赞

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Paul Sweatte
举报内容
Subscribe to the official common vulnerabilities and exposures (CVE) feed for Kubernetes to stay aware of security vulnerabilities. If possible, prepare a security incident response runbook in advance and go through a dry run on an annual or quarterly basis.

已翻译

赞

Application Development

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you test and validate your containerized applications and orchestrators before and after deployment?

1

2

3

4

5

6

7

1 Choose the right testing framework

2 Mock and isolate dependencies

3 Test your containers and images

4 Test your orchestrators and clusters

5 Test your deployment and delivery

6 Test your user experience and feedback

7 Here’s what else to consider

Application Development

给文章评分

感谢您的反馈

更多Application Development相关文章

更多相关阅读内容