Recent Updates

• 2023.09.18.1

  The V1 Load Balancer Moves Closer to Prod Ready And Containers Get More Flexible

  There's a building excitement around our V1 load balancer beta which now supports websockets, streaming requests, and more metric collections. These updates move the load balancer even closer to production ready status! We've also introduced two new container configuration options in update and a new state in healthcheck. The portal sees a nice collection of UI/UX improvements.

  • improvement

    V1 LB: Websockets, Streaming, and Metrics

    The V1 load balancer now supports websockets, streaming requests, and collects a wider range of metrics.

  • improvement

    Containers: Update Policy

    Users can now define a more verbose update strategy that allows for a stagger time to be set, further helping confirm system readiness on reimage.

  • improvement

    Additional AWS Server Types Supported

    Cycle now supports a much wider range of AWS EC2 instances.

  • improvement

    Websockets: Improved Heartbeat Logic

    Platform and Portal websockets have gotten an upgrade to connection status management, resulting in more reliable connections and reconnections to essential notifications.

  • improvement

    Containers: New Reimaging Process

    Reimage container functionality has been reworked so that images are fully downloaded, extracted, and verified before shutdown signal is sent to any instance.

  • improvement

    Healthcheck: Delay

    Users can now set a delay for their healthcheck configuration. This delay will wait a duration before healthchecks will start after a container has been started. They also support the health state of unknown, which enables users to implement probe-like patters.

  • fixed

    Notifications: Fixed Potential Deadlock

    During periods where an extreme number of notifications were being generated, the platform could occasionally deadlock. This issue has been resolved.

  • improvement

    [Portal] Server: CPU Charts

    The portal will now show usage CPU usage on the server telemetry graph as a percentage.

  • improvement

    [Portal] Billing: Re-Attempt Invoice

    Users can now manually re-attempt payment of an invoice through the portal.

  • fixed

    [Portal] Container: 'Current' Image Badge

    An issue existed where the current container image being used was not properly showing when interacting with the reimage form. This issue has been resolved.

  • improvement

    [Portal] UI Improvements

    Users will notices some nice UI improvements in the portal such as: instance health state on container modal and graph font size standardization.

• 2023.08.24.1

  Launch of a Brand New Interface for Cycle

  After months of development we've launched a new portal into production. With it comes a swath of new features, enhancements, and fresh design that will bring better information and productivity to our customers. Alongside the portal release, users will also notice meaningful platform updates to stacks, VPN, and image name validation.

  • improvement

    Portal Released

    A new portal is released featuring a modern style, increased speed, more reliable state and websocket connections, and much more.

  • improvement

    Stack Services

    Users can now define VPN and load balancer services in stacks, bringing additional flexibility to the format.

  • added

    VPN Config: API

    Users can now programmatically interact with the VPN configuration.

  • improvement

    Notifications Optimization

    The notification pipeline has been improved to further handle large spikes in notifications without any reduction in functionality.

  • fixed

    Image Name Validation

    Previously, certain images with periods in the image name would fail form validation. This issue has been resolved.

• 2023.08.04.1

  A New Image Source Type & Big CPU Changes

  This update will provide meaningful updates to server/host CPU's and the visibility, configuration, and effectiveness of those resources. We've also made a new round of fixes to the v1 Cycle load balancer for those who've opted into its use, and finally a new image source type of OCI Registry has been added.

  • improvement

    Server/Host CPU Utilization

    The platform now tracks CPU utilization for the host itself. Previously, the platform would only track load, RAM, and storage usage.

  • improvement

    Core Ranges for CPU Pinning

    Users can now designate a core range x-y for pinning a container to CPU cores.

  • improvement

    Improved CFS Scheduler Period

    Increased period to match the default which will be a better balance of throughput and latency while decreasing overhead.

  • fixed

    V1 Native Loadbalancer Fixes

    Fixed a panic that occurred when the LB failed to properly route traffic to a destination.

  • added

    Image Source: OCI Registry

    Added the ability to add OCI registries as image sources. This is a new feature in Cycle that provides support for any image registry conforming to the OCI spec. As a part of this, you can now natively add AWS ECR registries as sources to the platform.

• 2023.07.26.6

  Setting the Foundation for the Future

  With this update, we introduce the foundations for the next major phase of our roadmap and mission. From the beta release of Cycle's first native load balancer and parallel pipeline builds to a beta release of our new portal and more, this update contains a number of components that have been in development for the last 6+ months. For those looking to gain access to the beta portal, please reach out to our team!

  • improvement

    Parallel Pipelines

    Pipelines can now run in parallel. For pipelines that depend on the same resource, a new state of "Acquired" has been created that signifies a pipeline is waiting for that resource before starting.

  • improvement

    CFS Scheduler Optimization

    Increased the quota period so that the CFS scheduler creates less overhead when managing a server with high CPU usage.

  • added

    Cycle Load Balancer v1

    Users can now opt into using Cycle's newly developed load balancer. For now the Cycle load balancer is meant to be a 1:1 replacement for the HAProxy load balancer that is provisioned by default, but we expect a plethora of additional tooling, observability, deployment mechanics, and scaling tooling to be built onto it in the coming months.

  • added

    IAL for Auxiliary Native Providers

    Users can now add additional accounts from the same natively supported provider (AWS, Vultr, Equinix, GCP) through IAL mechanics.

  • improvement

    SDN Limit Increase

    The limit for environments connected to a single SDN has been increased from 5 to 8.

  • improvement

    Search Indexing Extended

    The search indexing, through the platform, now returns more objects faster than it previously did.

  • improvement

    Notifications: Previous State

    Added a field on notifications that is state_previous that tells you what the previous state was for a given resource that has been updated.

  • improvement

    GCP Regions Extension

    Cycle now supports GCP regions Turin, Italy and Dohar, Qatar.

  • improvement

    Duration Strings

    All durations are expressed as strings instead of ints giving the user better readability and simpler mechanics when setting longer timeframes.

• 2023.05.25.1

  Image Caching Layer, New Image Source Type, Identifiers, and Much More

  This update includes 7 weeks worth of improvements across a number of areas, but most significantly: images. Users now have an image caching layer, support for pushing local images, simplified resource identification, backup retention policy, and container deletion prevention. The team also fit in some wonderful enhancements and needed fixes.

  • added

    Image Caching Layer

    The image caching layer will allow for the use of images as they are built on the factory instead of waiting for the image to be fully uploaded to our backend image storage service. This update should greatly reduce the time it takes larger image to become live and also have a significant impact on reducing errors in uploads to the backend service, which, previously, could cause the entire image import to fail.

  • added

    Image Source: Bucket

    A new image source type has been added to the API called the "bucket" type. This type will allow users to upload images from their local machine directly to Cycle without needing to first push that image to a registry.

  • added

    Resource Identifiers

    Environments, hubs, pipelines, and image sources will now support identifiers. Identifiers give users a simpler way to name a given resource without using the ID.

  • improvement

    Container Command Override

    Users can now wrap long blocks of commands in quotes when setting a container override command, giving greater flexibility to this utility.

  • added

    Backups Retention Policy

    Backups will now have a retention policy that will default to one year, but that can be set by the user. This policy is how long a backup will be kept for a given container.

  • added

    Containers Lock

    Users can now take advantage of the containers "Lock" field, a boolean where true means the container will not be able to be deleted.

  • fixed

    GCP GPU Pricing

    An issue that prevented the correct price from being shown on certain GCP GPU's has been resolved.

  • fixed

    Pipelines: Stack Builds

    An issue that would cause stack builds to panic when created as part of a pipeline has been resolved.

• 2023.04.04.1

  Unique VXLan Tags and New Filters on Activity

  Our first release of April brings a fix to VXLan tagging that guarantees uniqueness of the tag among environments. Also, users of the API can now filter by events for security/hub activity.

  • fixed

    VXLan Tag Uniqueness

    VXLan tags are now guaranteed to be unique between environments.

  • added

    Activity Filtering

    Users can now filter API returns for security/hub activity events.