PRODUCT RELEASE

Ambassador adds ClickOps support for Emissary, Telepresence, and Argo

Manage your cloud native workflow using Telepresence, Argo, and Emissary-ingress with just a few clicks in Ambassador Cloud

Today, we’re releasing a major update to Ambassador Cloud that enables developers to code, ship, and run Kubernetes services with just a few clicks, using the Cloud Native Computing Foundation (CNCF) tools that you’re already using. Ambassador Cloud now provides a graphical, web-based interface for developers that use Telepresence (development & testing), Argo (continuous delivery), and Emissary-ingress (API Gateway).

Create a free Ambassador Cloud account now, or continue reading to learn more about these new capabilities in Ambassador Cloud.

Developers just want to code

We built Ambassador Cloud for one reason: developers just want to write great code.

Yet, the power of Kubernetes and its ecosystem adds significant complexity to the development process: containers, YAML, microservices, continuous deployment, and more. The learning curve for developers to master this complexity is steep. The reality is that this is a mountain that most developers don’t want to climb — and they shouldn’t have to.

Code with Telepresence and Cloud

Telepresence is a CNCF project that lets you set up a local dev environment that connects to a remote Kubernetes cluster — enabling you to use your existing tools & workflow for development. You can make a code change locally and immediately see the effects of that code change remotely.

Historically, Telepresence has been managed using a command-line interface and requires a working knowledge of Kubernetes.

$ telepresence connect
$ telepresence list
$ telepresence intercept my-service -n my-namespace --mount my-volume
$ telepresence leave my-service

Ambassador Cloud simplifies this workflow. You now:

1. Start a Telepresence session from a list of Kubernetes services
2. Get a secure URL to view any code changes in real-time.
3. Ensure any collaborators who want to preview your code are part of your GitHub or GitLab organization so you can work with them in real-time.

Using Ambassador Cloud’s point and click UI to reroute remote traffic to a localService

Generating a secured Preview URL to share access to your local development environment, via Ambassador Cloud

Deploy with Argo

Argo is a CNCF project for continuous deployment, integrating with your existing continuous integration and deployment workflows. With Argo, you can orchestrate canary releases over time.

Argo is typically managed using a declarative, GitOps-style workflow similar to the way you manage Kubernetes:

1. Create a rollout resource as a CRD:

apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
name: my-rollout
spec:
replicas: 5
workloadRef:
apiVersion: apps/v1
kind: Deployment
name: my-deployment
strategy:
canary:
steps:
- setWeight: 20
- pause: {duration: 10s}

2. Open a pull request to your GitOps repository with this configuration.

3. Merge the pull request.

4. Monitor the performance and error rate of the canary release vs stable in your observability system of choice.

5. If there’s an issue, pause the rollout: kubectl argo rollouts pause ROLLOUT_NAME

Ambassador Cloud simplifies this workflow, enabling you to manage the entire canary release workflow via Argo from a single pane of glass:

1. Open a pull request with the necessary configuration:
2. Review and merge the pull request.
3. Monitor the canary release directly in Ambassador Cloud’s UI
4. If there’s an issue, press the pause button

Create a Pull Request from Ambassador Cloud

Monitoring a Kubernetes Service Canary Release via Ambassador Cloud

Pausing a Kubernetes Canary Release via Ambassador Cloud

Run with Emissary-ingress

Emissary-ingress is a CNCF project that implements an Envoy-powered ingress controller and API Gateway. With Emissary-ingress, you can manage and observe traffic from the Internet to your Kubernetes services.

Like Kubernetes and Argo, Emissary-ingress is typically managed using a declarative, GitOps-style workflow. To publish a service via Emissary-ingress:

1. Create a Mapping resource as a CRD:
2. Read the documentation for timeouts, mappings, rate limiting, …
3. Write the YAML based on the documentation.
4. Set up (if you haven’t already) a local Kubernetes instance with Emissary-ingress to test & validate the YAML. Debug the YAML.
5. Open a pull request to your GitOps repository with this configuration.
6. Merge the pull request.

Ambassador Cloud simplifies this workflow, enabling you to create a Mapping straight from the Cloud as a pull request.

1. Open a pull request with the necessary configuration:
2. Merge the pull request.

Generating a Mapping configuration and creating a Pull Request using Ambassador Cloud’s point and click UI

A Mapping resource has a plethora of options: timeouts, rate limiting, load balancing, and more. Many of these options are critical for ensuring availability and resilience. Remembering every single option (and its format) can be challenging, so we do it for you in Cloud. The Mappingscreated by Cloud automatically include our best practice recommendations, including timeouts and rate limits.

Check out this video from Edidiong that demonstrates all of these new features in Ambassador Cloud working together to help you embrace ClickOps across code, ship, and run with Kubernetes:

This is only the beginning of ClickOps support for CNCF projects within Ambassador Cloud as we continue our mission of helping developers adopt Kubernetes. If you have particular open source tools or workflows you’d like to see integrated, join our community Slack group and let us know!

Learn More

• Get started with Ambassador Cloud
• Platform Engineering: What Is It, Where Is It Going, and Why Should You Care?
• Hear what the experts have to say
• Get access to the Kubernetes Architect Library
• Join our remote-first team — we’re growing across all departments!