K8s Initializer

Build Your Own Application-Ready Kubernetes Playground

Generate YAML configs for ingress, CI/CD, observability, authentication, and more in just 3 minutes

Ambassador
Edge Stack
for Ingress


Observability
Metrics and Distributed Tracing

Keycloak
for Authentication

Argo CD
for CI/CD

Knative
for Serverless

Step 1: Configure Ambassador Edge Stack for Ingress

Where is your Kubernetes cluster?

Select your preferred type of supported external load balancer

Do you want to terminate TLS?

Public Hostname

This hostname will be used to serve the correct certificate. It can be a * wildcard

Service Name

Email Address

This email will be shared with Let’s Encrypt when acquiring the TLS certificate

Kubernetes TLS Secret Name

Existing Kubernetes secret name with the corresponding certificate

Certificate ARN

The Amazon Resource Name (ARN) of the certificate

How do you want to handle insecure traffic?

How do you want to handle insecure traffic?

If Ambassador is not terminating TLS (because the load balancer is terminating TLS, or because there is no TLS termination), then Ambassador can only accept cleartext traffic, and thus cannot redirect cleartext (insecure) traffic to HTTPS. If you would like to do redirect or reject cleartext traffic, either choose an L7 load balancer and make the appropriate settings in the cloud console to terminate TLS at that load balancer, or terminate TLS at Ambassador.

Do you want to preserve the original client IP address in HTTP requests?

  -

Step 2: Configure Observability

 

Do you want to collect metrics?

Do you want to collect distributed traces?

Lightstep Access Token

In app.lightstep.com navigate to Settings > Access Tokens to retrieve your Lightstep Access Token

To support your observability configuration, the deployment of the OpenTelemetry Collector will allow for the aggregation and enrichment of trace data from multiple services and formats: Zipkin, Jaeger, and OpenTelemetry. It is also possible to relay trace data to both the Jaeger and Lightstep receivers as the collector supports multiple destinations all at once.
  -

Step 3: Configure Keycloak for Auth

 

Do you want to secure applications?

Temporary Keycloak Admin Password

  -

Step 4: Configure Argo CD for Continuous Delivery

 

Do you want to enable application deployments through GitOps?

Argo CD Authentication

Temporary Argo CD Admin Password

  -

Step 5: Configure Knative for Serverless

 

Do you want Serverless capabilities?

  -

0

lines of YAML

To install your Kubernetes playground, please:

Select your Kubernetes provider


Preview your custom configuration

Provider Unknown
Load Balancer Not using a Load Balancer
TLS Termination At Ambassador using Let's Encrypt
Insecure Traffic Redirect HTTP to HTTPS
Client IP The client IP address is not preserved
Hostname Will be assigned during installation