The k8s clusters are provisioned using our IaC templates. Clusters are automatically created with cost-saving options while maintaining the appropiate amount of availability based on the environment. Cluster resource usage in production environments are periodically reviewed to set the optimal balance of node types. Some customization can be applied as needed.
The pipeline uses GitOps. The "deploy" directory is added to repositories with definitions for deployment to different environments. Git branches are deployed to review environments, the master branch is deployed to staging, and git tags are deployed to production and integration. All environments are optional (simply don't define the environment to skip it).
Each pipeline comes with a build, test, and deploy stage with a corresponding job in each. Those jobs, as well as additional special jobs for testing and analysis, can be enabled or disabled by adding environment variables to the pipeline.
The k8s clusters are provisioned with the following:
You are given read-only kubectl access to the clusters for debugging. In addition, you will have the ability to exec into your application pods as well as restart them.
Polymatic Systems is truly a complete end-to-end solution. We install a VPN and a VCS. Access is controlled through the use of the VPN and oauth integrations with the VCS.
The pipeline is designed to deploy some database services for the purpose of review environments. They are not highly available / reliable and should not be used in production.
Some highly available / reliable database services that have kubernetes operators can be manually installed by us for you, however, support for these database services (such as modifying or updating the installation) incur additional support costs that are billled by the hour. Ask us to get a list of which database services we can currently install for you.
Sign up and someone will be in contact with you shortly, after which your clusters will be provisioned. You will then recieve access to all your tools and our documentation. Then you can start configuring your git repositories to deploy to your clusters immediately.
The purpose of the phone call is determine how much support you will need to begin migrating your applications. It's often best to get support with your first repository to get the hang of things. This can be done in as little as a day.
Charges occur monthly. Your final cost is based off of your infrastructure usage plus a tiered premium.
The platform is continually kept up to date. This includes pipeline improvements, new features, dependency tool updates and kubernetes version updates.
Usage questions can be posted in our slack chat which will often receive a reply the same day.
Any issues that arise directly related to the plaform (like a feature not working) will also be addressed as soon as possible.
We will provide a free analysis of what is required to migrate your application and an estimate of how long that will take.
You can hire us to perform the migration of your applications at an additional cost. This support is billed hourly. The most cost effective strategy is to have us configure your repository and provide instructions on how to make the switch, however we can perform the actual migration if needed (that often requires providing us credentials to your existing infrastructure).
We constantly monitor the clusters and tools for any issues and will notify you if we find any. We will NOT notify you of any issues caused by application failures. We provide you with all the necessary tools to debug those issues as well as receive alerts when they are occurring.