First time at Zeet?

4 Apr
min read

Changelog 4.4.24 - Linode Clusters, Networking Changes, Group Cleanup, Branch Changes, and more.

Big week of launches, from Linode Cluster Provisioning, Networking Changes to Ports, Git-to-Zeet Branch Changes, Group Cleanup on Subgroup removal, and more.

Jack Dwyer


Share this article

So What's New?

Linode Clusters

With Zeet's new Cluster Provisioning in Linode LKE, you can now launch fully managed Kubernetes clusters directly from your Zeet dashboard with just one click. No more fiddling with Linode's Resource Manager templates or clicking through pages in the Linode portal. Just create an access token in Linode and Zeet will handle the rest.

Check out the docs for more information on this feature.

Networking Changes

The networking tab in your Project Settings just got a functionality and face-lift: you can now customize your internal and external port, and also expose it publicly. The Port configures what your container is listening on, the External Port is the a port used to access via an internal endpoint or load balancer, and the Host Port is used to expose it publicly.

Subgroup Cleanup

This is a change to the default behavior in Zeet. Previously, if you deleted all the Subgroups in a Group, or deleted all Projects within all Subgroups in a Group, the now-empty Group would remain. Now, we'll auto-cleanup that Group so you don't have an empty Group cluttering your UI. Similarly, if you delete a Group, all Subgroups within will be deleted. You can turn off the Auto-cleanup via the APi or in the Group Settings.

Branch Changes

We've made some big changes to the way Zeet branches operate. Previously they were 1:1 with git branches, but that's no longer the case. You can now map one git branch to multiple Zeet Branches, switch Zeet Branches on a Git-based container app without being forced to have two branches deployed—we'll auto-kill the old one while spinning up the new one—and point your Zeet branches to older git commits, say, in the case of an emergency.

Ephemeral Environments Upgrades

We released Ephemeral Environments about a month ago, and just rolled out a couple important updates to them, including the ability to re-name the Envrionment name by setting the `ZEET_GROUP_NAME` env var, or by passing `--group-name` to the start stop and comment commands. Additionally, when stopping an enviroment, the associated Subgroup will now clean itself up.

Anything Else???

Group Permissions Are Live!

If you missed it, we released a blog post detailing everything.

You can now set access on Groups and Subgroups so only select members of your team can perform actions in a Group or Subgroup. These permissions supersede general Zeet-level permissions.

More Blueprints, more features, more Zeet:

  • Sidebar Refresh
  • Cluster Precheck

That's all for this week! Got feedback, or something you'd like to see? Hit us up on Twitter or shoot us an email!

Happy Shipping!

Subscribe to Changelog newsletter

Jack from the Zeet team shares DevOps & SRE learnings, top articles, and new Zeet features in a twice-a-month newsletter.

Thank you!

Your submission has been processed
Oops! Something went wrong while submitting the form.