Creating a Deployment in the Portal

Video Transcript

Hi, I’m Jake, the CEO and founder of Cycle.io, a container orchestration platform. I want to introduce a new feature we’re launching later today. This feature has been highly requested, and we’re excited to finally roll it out.

In Cycle, we have different environments, similar to global VPCs. Even if multiple environments share the same infrastructure, containers within one environment can’t see containers in another. This provides isolated and secure container management across various infrastructures, whether on AWS, GCP, or on-premises.

Now, let’s get into what’s new. We’ve introduced a deployment tagging system. This allows you to group containers into specific application versions. For example, we have an API container that can be accessed by any container in the environment, regardless of deployment tags. This means you can manage version-specific deployments more effectively.

Looking at our demo, we have two application versions: 1.2.3, tagged as production, and 1.4.1, our latest dev version. You can interact with these deployments directly through the Cycle UI. If you want to promote a version from dev to production, you simply update the deployment tag. This action will redirect your production traffic to the new version in one step.

If something goes wrong with the new version, rolling back is just as easy. You can revert to the previous deployment with a single action, updating all the endpoints immediately.

This feature simplifies version management, rollbacks, and multi-version deployment within your environment. We’re launching this feature today, along with several others. If you have questions or want to learn more, visit cycle.io or join our Slack community at slack.cycle.io. Thank you!