<h2 id="automate-testing-and-secure-applications-running-on-your-kubernetes-cluster">Automate testing and secure applications running on your Kubernetes cluster</h2>Easily deploy preconfigured testing, security, and other operational tools with just a few clicks.

With 1Password Business, you can automate many common administrative tasks using the 1Password SCIM bridge. It uses the System for Cross-domain Identity Management (SCIM) protocol to connect 1Password with your existing identity provider, like Azure Active Directory or Okta, so you can:
<ul>
<li>create users and groups (including automated account confirmation),</li>
<li>grant and revoke access to groups,</li>
<li>and suspend deprovisioned users</li>
</ul>
With this 1-Click App, you’ll quickly set up and deploy the SCIM bridge on a cluster in your own environment, so the encryption keys for your account are only available to you and no one else. To set up and deploy the SCIM bridge, you’ll need:
<ul>
<li>administrative access in 1Password Business</li>
<li>this 1-Click App with publicly accessible static LoadBalancer IP address</li>
<li>a DNS record to allow for encrypted (HTTPS) communication to the SCIM bridge</li>
</ul>

Integrate 1Password with your identity provider for automatic provisioning

1Password SCIM bridge

The ngrok Ingress Controller for Kubernetes provides ingress-as-a-service to your Kubernetes applications by offloading traffic management, performance, and security to ngrok’s global network.
Because it leverages native Kubernetes tooling, you can configure the route, host, and downstream service via the standard Kubernetes Ingress object, and you can deploy it to your DigitalOcean Kubernetes (DOKS) cluster with a Helm chart.
Once deployed to your cluster, the Ingress Controller connects to ngrok’s cloud service, which provisions the resources necessary to provide the ingress—such as Web Application Firewalls, Global Server Load Balancers, local load balancers, and reverse proxies—in ngrok’s global network.
The ngrok Ingress Controller for Kubernetes equips you to serve apps and APIs without needing to configure networking details such as ELBs, IPs, network interfaces, or VPC routing, radically simplifying ingress into Kubernetes.
<img src="https://info.ngrok.com/hubfs/marketplace-listing/ngrok_kic_diagram.png" alt=""/>

The ngrok Ingress Controller for Kubernetes is our official open-source controller for adding public and secure ingress traffic to your k8s services.

ngrok Ingress Controller

<h2 id="configured-with-love,-and-with-our-engineering-team&#39;s-best-practices-in-mind">Configured with love, and with our engineering team&#39;s best practices in mind</h2>Our engineers have run Kubernetes in production for years -- not just at DigitalOcean, but at other successful startups, too. Those best practices have been included in the configuration of our 1-Click Apps for Kubernetes.

<a href="https://prometheus.io/" rel="noopener" target="_blank">Prometheus</a> is a very popular and comprehensive systems monitoring solution. It is a standalone open source project and maintained independently of any company. A big plus is the capability to monitor <code>Kubernetes</code> clusters as well, which tend to be pretty complex in nature. Prometheus eases the operational tasks that are required in setting up a monitoring stack.
The <a href="https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack/" rel="noopener" target="_blank">kube-prometheus-stack</a> is meant for <code>cluster monitoring</code>, so it is <code>pre-configured</code> to collect metrics from all <code>Kubernetes components</code>. In addition to that it delivers a default set of <code>dashboards</code> and <code>alerting</code> rules. Many of the useful dashboards and alerts come from the <a href="https://github.com/kubernetes-monitoring/kubernetes-mixin/" rel="noopener" target="_blank">kubernetes-mixin</a> project.
The <code>kube-prometheus-stack</code> consists of three main components:
<ul>
<li><code>Prometheus Operator</code>, for spinning up and managing <code>Prometheus</code> instances in your <code>DOKS</code> cluster.</li>
<li><code>Grafana</code>, for visualizing metrics and plot data using stunning dashboards.</li>
<li><code>Alertmanager</code>, for configuring various notifications (e.g. <code>PagerDuty</code>, <code>Slack</code>, <code>email</code>, etc) based on various alerts received from the Prometheus main server.</li>
</ul>
Prometheus follows a <code>pull</code> model when it comes to metrics gathering, meaning that it expects a <code>/metrics</code> endpoint to be exposed by the service in question for scraping. For every metric that is being fetched by Prometheus, a time series database is used to store the data points.
<code>Grafana</code> helps you gather data points from the Prometheus time series database, and plot everything using beautiful graphs grouped into dashboards. You can also perform queries using the <code>PromQL</code> language. To persist all the data (metrics and various settings), you need to allocate block storage for both Prometheus and Grafana instances via <code>Persistent Volumes</code> (or PVs).
The <a href="https://github.com/prometheus/alertmanager/" rel="noopener" target="_blank">Alertmanager</a> component handles alerts sent by client applications such as the Prometheus server. It takes care of <code>deduplicating</code>, <code>grouping</code>, and <code>routing</code> them to the correct <code>receiver</code> integration such as <code>email</code>, <code>PagerDuty</code>, or <code>Slack</code>. It also takes care of <code>silencing</code> and <code>inhibition</code> of alerts.
Please make sure to visit the official documentation page for each of the components to learn more:
<ul>
<li><a href="https://prometheus.io/docs/" rel="noopener" target="_blank">Prometheus</a>, to learn more about all the available features, as well as various configuration options.</li>
<li><a href="https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started.md" rel="noopener" target="_blank">Prometheus Operator</a>, which provides useful information on how to use the operator.</li>
<li><a href="https://prometheus.io/docs/alerting/latest/alertmanager/" rel="noopener" target="_blank">Alertmanager</a>, to learn more about Alertmanager and integrations with various notification platforms.</li>
</ul>
Notes:
<ul>
<li>DigitalOcean is using <code>Helm v3</code> to deploy <code>Prometheus</code> to your <code>DOKS</code> cluster.</li>
<li>This chart was formerly named <code>prometheus-operator</code> chart, now renamed to more clearly reflect that it installs the <code>kube-prometheus</code> project stack, within which <code>Prometheus Operator</code> is only one component.</li>
<li>The Prometheus stack 1-Click App also includes a $1/month block storage for both Grafana and Prometheus time series database (two <code>PVs</code> of <code>5GB</code> each, to start with).</li>
</ul>

Prometheus, Grafana, and Alertmanager preinstalled and integrated together on a DigitalOcean Kubernetes Cluster.

Kubernetes Monitoring Stack

<a href="https://github.com/kubernetes/ingress-nginx/" rel="noopener" target="_blank">NGINX</a> is an Ingress Controller, and sits at the edge of your VPC acting as an entry point for your network. It operates at layer 7 of the OSI model and handles and routes HTTP requests to your web applications.
When NGINX is deployed to your DigitalOcean Kubernetes (DOKS) cluster, a Load Balancer is created as well, through which it receives the outside traffic. Then, you will have a domain set up with <code>A</code> type records (hosts), which in turn point to your load balancer&#39;s external IP. So, data flow goes like this: <code>User Request -&amp;amp;amp;amp;gt; Host.DOMAIN -&amp;amp;amp;amp;gt; Load Balancer -&amp;amp;amp;amp;gt; Ingress Controller (NGINX) -&amp;amp;amp;amp;gt; Backend Applications (Services)</code>.
In a real world scenario, you do not want to use one Load Balancer per service, so you need a proxy inside the cluster, which is provided by the Ingress Controller. As with every Ingress Controller, NGINX allows you to define ingress objects. Each ingress object contains a set of rules that define how to route external traffic (HTTP requests) to your backend services. For example, you can have multiple hosts defined under a single domain, and then let NGINX take care of routing traffic to the correct host.
The NGINX Ingress Controller is deployed via <a href="https://helm.sh/" rel="noopener" target="_blank">Helm</a> and can be managed the usual way.
To know more about the community maintained version of the NGINX Ingress Controller, check the <a href="https://kubernetes.github.io/ingress-nginx/" rel="noopener" target="_blank">official Kubernetes documentation</a>.
Notes:
<ul>
<li>DigitalOcean uses Helm v3 to deploy the NGINX Ingress Controller to your DOKS cluster.</li>
<li>The NGINX Ingress Controller 1-Click App also includes a $12/month DigitalOcean Load Balancer to ensure that ingress traffic is distributed across all of the nodes in your Kubernetes cluster.</li>
</ul>
<h2 id="nginx-example-setup-diagram">NGINX Example Setup Diagram</h2>
Below is a diagram depicting a more complete example for an NGINX based setup:
<img src="https://raw.githubusercontent.com/digitalocean/marketplace-kubernetes/master/stacks/ingress-nginx/assets/images/arch_nginx.png" alt="NGINX Example Setup"/>
For setting up production-ready TLS certificates via Cert-Manager, see the <code>Additional Resources</code> section at the end of this quick start guide.

NGINX Ingress Controller is built around the Kubernetes Ingress resource, using a ConfigMap to store the NGINX configuration. Ingress can provide load balancing, SSL termination and name-based virtual hosting.

NGINX Ingress Controller

<h2 id="get-insights-into-your-kubernetes-cluster&#39;s-health-and-performance">Get insights into your Kubernetes cluster&#39;s health and performance</h2>Get cluster usage statistics, add a monitoring agent to your containers, or set up a service mesh.

<a href="https://github.com/kubernetes-sigs/metrics-server" rel="noopener" target="_blank">Metrics server</a> is an open source metrics API implementation, created and maintained by the Kubernetes SIG. Main purpose of metrics-server is to help the Kubernetes <a href="https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale" rel="noopener" target="_blank">Horizontal Pod Autoscaler</a> to automatically scale up or down your application workloads based on external factors (such as heavy HTTP traffic). In a nutshell, metrics-server works by collecting resource metrics from Kubelets and exposing them via the Kubernetes API Server to be consumed by the Horizontal Pod Autoscaler (aka HPA). Metrics API can also be accessed by <code>kubectl top</code>, making it easier to debug autoscaling pipelines.
Although you can query metrics-server for resource utilization metrics such as CPU and memory, it&#39;s not advised to do so. This is due to the fact that provided metrics data may not be very accurate. For better results you would want to use a dedicated monitoring solution like <a href="https://prometheus.io" rel="noopener" target="_blank">Prometheus</a>.
Please make sure to check metrics-server <a href="https://github.com/kubernetes-sigs/metrics-server/blob/master/README.md" rel="noopener" target="_blank">official documentation</a> for more details.
Note:
DigitalOcean is using Helm v3 to deploy metrics-server to your DOKS cluster.
<h2 id="metrics-server-and-hpa-overview-diagram">Metrics-Server and HPA Overview Diagram</h2>
Below diagram shows a high level overview of how HPA (Horizontal Pod Autoscaling) works in conjunction with metrics-server:
<img src="https://raw.githubusercontent.com/digitalocean/marketplace-kubernetes/master/stacks/metrics-server/assets/images/arch_hpa.png" alt="Metrics-Server and HPA Overview"/>

Metrics Server is a scalable, efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.

Kubernetes Metrics Server

Netdata is a highly optimized open source monitoring agent you install on all your systems and containers. Netdata provides unparalleled insights, in real-time, of everything happening on the systems it runs in (including web servers, databases, applications), using highly interactive web dashboards.
Netdata can run autonomously, without any third party components, or it can be integrated to existing monitoring tool chains (Prometheus, Graphite, OpenTSDB, Kafka, Grafana, etc). Netdata is fast* and efficient, designed to permanently run on all systems (physical &amp; virtual servers, containers, IoT devices) without disrupting their core function.*
Netdata is free, open-source software, and can be found at <a href="https://github.com/netdata" rel="noopener" target="_blank">https://github.com/netdata</a> and 
<a href="https://www.netdata.cloud/" rel="noopener" target="_blank">https://www.netdata.cloud</a>.

Distributed, real-time, performance and health monitoring for systems and applications

Netdata

<a href="https://linkerd.io/?utm_source=DigitalOcean&amp;utm_campaign=Marketplace" rel="noopener" target="_blank">Linkerd</a> is an ultralight service mesh for Kubernetes. It makes running services easier and safer by giving you runtime debugging, observability, metrics, reliability, and security without requiring any code changes. The Linkerd 1-Click app configures and performs a deployment of Linkerd2 onto a DigitalOcean Kubernetes cluster in the <code>linkerd</code> namespace. As a part of a recommended deployment, this app includes Grafana and Prometheus in the <code>linkerd</code> namespace.
This stack is open source and community supported, and can be found at <a href="https://github.com/digitalocean/marketplace-kubernetes/tree/master/stacks/linkerd2" rel="noopener" target="_blank">github.com/digitalocean/marketplace-kubernetes/tree/master/stacks/linkerd2</a>. If you have large production needs, see the <a href="https://buoyant.io/commercial-support/?utm_source=DigitalOcean&amp;utm_campaign=Marketplace" rel="noopener" target="_blank">Buoyant Enterprise Support</a>.
Notes:
<ul>
<li>The Linkerd2 CLI is recommended to interact with Linkerd2 and instructions are provided to add your specific service.</li>
<li>This stack requires a minimum configuration of 2 nodes at the $10/month plan (2GB memory/1 vCPU).</li>
</ul>

A recommended deployment of Linkerd2 and the viz extension on a DigitalOcean Kubernetes cluster.

Linkerd

Stop spending hours editing YAML and Helm charts. Instead, use these popular, preconfigured solutions to add apps to your Kubernetes cluster in minutes instead of days.

1-Click Apps for managing Kubernetes environments

Focus on building great things, while you use these 1-Click Apps to build your business.

These 1-Click Apps make it simple to deploy and manage your clients' infrastructure. Save time and resources, while reducing headaches and passing the value onto your clients.

Apps for agencies and website development shops

Work more effectively from home or remotely with these 1-Click Apps.

Work more effectively from home or remotely

Stay focused on teaching and learning, instead of managing infrastructure. 

1-Click Apps for students and educational institutions

SaaS Add-Ons make your DigitalOcean infrastructure better! Check out the full list of SaaS Add-Ons here!  

New Feature Alert: Introducing Software License Subscriptions on DigitalOcean Marketplace!

We now support Droplet 1-Click updates via API. See documentation for the details

Check out Tabnine, the AI coding assistant that accelerates & simplifies software development.

Kubernetes administration and operations

Automate testing and secure applications running on your Kubernetes cluster

Configured with love, and with our engineering team's best practices in mind

Get insights into your Kubernetes cluster's health and performance