Shipa is now for the first time in the Civo Marketplace. If you are unfamiliar with Civo, Civo is a Kubernetes-based cloud provider allowing for the rapid creation of Kubernetes clusters. The engineering efficiency and developer experience that Shipa brings can supercharge your Kubernetes experience on Civo. Now you can spin up a Shipa Control Plane e.g Shipa Self-Managed with a click of a button on Civo Cloud.
Typically, Infrastructure-as-Code or IaCs have had their own languages to learn. For example, if leveraging Terraform most likely you came across Terraform’s native syntax, HCL. Though as software engineers we might be more familiar with other languages of choice. Using a general-purpose computer language vs a provider level syntax does unlock the power of the language; anything you can do in the computer language potentially can be additional methods, calls, etc.
As a software engineer, I admit I am not the best at networking. Can’t connect to your app for some reason, one going joke is to “always blame DNS” e.g the Domain Name System. My personal DNS experience is usually editing a few records for my personal blog and connecting a few tools and that is it. Thanks to distributed systems, had to learn all about SRV records and some more DNS concepts.
We are really excited today at Shipa to release version 1.6 of Shipa. If you are using Shipa Cloud, you will notice that your version of the SaaS product has incremented. Let’s dig into what is new with Shipa 1.6.0 and how you can get your hands on Shipa.
If you are a software engineer like myself, two areas that I am not well versed in are networking and storage. Yes, my application has to communicate and yes my application needs to be deployed and requires some storage. Though that is usually the extent of my knowledge. Thanks to using elastic compute from cloud vendors in the last several years, the answer I usually give is “yes, attach 100gb of standard block storage per instance”.
There is a lot of the art of the possible between the GitOps Engine, Argo CD, and the Application-as-Code platform, Shipa. In a recent blog post, we outlined the power of a one-line developer experience. Though if you are unfamiliar with ArgoCD, here is a guide to get you started with Argo CD and leveraging Shipa for your first deployment.
As a software engineer, leveraging GitHub is one of those tools that transcend your personal and professional development activities. Bringing open source to the masses, GitHub is a familiar platform for many. A newer addition to the GitHub Platform is GitHub Actions which was originally a workflow engine, now expanding into CI/CD.
Does this combination of words sound somewhat new to you as well? It may be just me, but having the opportunity to work on both sides, software development and system administration, the combination above seemed somewhat new or different to me. I always saw Oracle as something that would be managed and owned by the System Administrators. Technologies such as the database, ERPs, finance systems, and more which would take quite a lot of effort and cost to implement and maintain.
If you are not familiar with CloudFormation, an easy way to define it is AWS CloudFormation is an AWS service that uses template files to automate the setup of resources. It can also be described as an infrastructure automation or Infrastructure-as-Code (IaC) tool. You can use CloudFormation to automate the configuration of workloads that run on the most popular AWS services, including their managed Kubernetes offering, the Elastic Kubernetes Service, or EKS.
DigitalOcean, or DO, brands itself as the “developer cloud,” and it’s no secret that it has a strong mind-share among developers, especially because of factors such as simple UI, performance, structured documentation, a robust community ecosystem, and last but not least, the affordable pricing. As developers started adopting microservices as the architecture of choice for their applications, DO responded quickly and launched their Managed Kubernetes offering, labeled DOKS.
