Skip to content

Commit c0afada

Browse files
ppebleppeble
committed
Update all 1.14 metadata to fix navigation
Signed-off-by: Phil Peble <[email protected]>
1 parent 5a68698 commit c0afada

File tree

118 files changed

+344
-1914
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

118 files changed

+344
-1914
lines changed

‎content/en/docs/1.14/about/_index.md

+4
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
---
2+
title: "About"
3+
weight: 10
4+
---

‎content/en/docs/1.14/about/alternatives.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Emissary vs. other software
1+
---
2+
title: "Alternatives"
3+
---
24

35
Alternatives to the Emissary fall into three basic categories:
46

‎content/en/docs/1.14/about/faq.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Frequently Asked Questions
1+
---
2+
title: Frequently Asked Questions
3+
---
24

35
## General
46

‎content/en/docs/1.14/about/features-and-benefits.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Features and benefits
1+
---
2+
title: Features and Benefits
3+
---
24

35
In cloud-native organizations, developers frequently take on responsibility for the full development lifecycle of a service, from development to QA to operations. Emissary was specifically designed for these organizations where developers have operational responsibility for their service(s).
46

‎content/en/docs/1.14/about/support.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Need help?
1+
---
2+
title: Support
3+
---
24

35
If you need help deploying Emissary at your organization, there are several different options available to you.
46

‎content/en/docs/1.14/about/why-ambassador.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Why Emissary?
1+
---
2+
title: Why Emissary?
3+
---
24

35
Emissary gives platform engineers a comprehensive, self-service edge stack for managing the boundary between end-users and Kubernetes. Built on the [Envoy Proxy](https://www.envoyproxy.io) and fully Kubernetes-native, Emissary is made to support multiple, independent teams that need to rapidly publish, monitor, and update services for end-users. A true edge stack, Emissary can also be used to handle the functions of an API Gateway, a Kubernetes ingress controller and a layer 7 load balancer (for more, see [this blog post](https://blog.getambassador.io/kubernetes-ingress-nodeport-load-balancers-and-ingress-controllers-6e29f1c44f2d)).
46

‎content/en/docs/1.14/community.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,7 @@
1-
# Community
1+
---
2+
title: Community
3+
weight: 50
4+
---
25

36
## Contributor's guide
47
Please review our [contributor's guide](https://github.com/emissary-ingress/emissary/blob/master/DEVELOPING.md)

‎content/en/docs/1.14/doc-links.yml

-222
This file was deleted.

‎content/en/docs/1.14/howtos/index.md ‎content/en/docs/1.14/howtos/_index.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,7 @@
1-
# "How-to" guides
1+
---
2+
title: "How-to guides"
3+
weight: 20
4+
---
25

36
These guides are designed to help users quickly accomplish common tasks. The guides assume a certain level of understanding of Emissary. Many of these guides are contributed by third parties; we welcome contributions via Pull Request at https://github.com/emissary-ingress/emissary.
47

‎content/en/docs/1.14/howtos/advanced-rate-limiting.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Advanced rate limiting
1+
---
2+
title: Advanced rate limiting
3+
---
24

35
Ambassador Edge Stack integrates a flexible, high-performance Rate Limit Service (RLS). Similar to Emissary, the RLS features a decentralized configuration model so that individual teams can manage their own rate limits. For example:
46

‎content/en/docs/1.14/howtos/auth-kubectl-keycloak.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Kubernetes SSO with OIDC and Keycloak
1+
---
2+
title: Kubernetes SSO with OIDC and Keycloak
3+
---
24

35
Developers use `kubectl` to access Kubernetes clusters. By default `kubectl` uses a certificate to authenticate to the Kubernetes API. This means that when multiple developers need to access a cluster, the certificate needs to be shared. Sharing the credentials to access a Kubernetes cluster presents a significant security problem. Compromise of the certificate is very easy and the consequences can be catastrophic.
46

‎content/en/docs/1.14/howtos/basic-auth.md

+3-9
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,6 @@
1-
import Alert from '@material-ui/lab/Alert';
2-
3-
# Basic authentication (for Emissary)
4-
5-
<Alert severity="info">
6-
This guide applies to Emissary, use of this guide with Ambassador Edge Stack is not recommended. Ambassador Edge Stack does <a href="../ext-filters">authentication using the Filter resource</a> instead of the AuthService resource as described below.
7-
</Alert>
8-
9-
1+
---
2+
title: Basic Authentication
3+
---
104

115
Emissary can authenticate incoming requests before routing them to a backing
126
service. In this tutorial, we'll configure Emissary to use an external third

‎content/en/docs/1.14/howtos/cert-manager.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Using cert-manager
1+
---
2+
title: Using cert-manager
3+
---
24

35
Emissary has simple and easy built-in support for automatically using ACME to create and renew TLS
46
certificates; configured by the [`Host` resource](../../topics/running/host-crd/). However, it only supports ACME's

‎content/en/docs/1.14/howtos/client-cert-validation.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Client certificate validation
1+
---
2+
title: Client certificate validation
3+
---
24

35
Sometimes, for additional security or authentication purposes, you will want
46
the server to validate who the client is before establishing an encrypted

‎content/en/docs/1.14/howtos/consul.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
1-
2-
import Alert from '@material-ui/lab/Alert';
3-
4-
# Consul integration
1+
---
2+
title: Consul integration
3+
---
54

65
<div class="docs-article-toc">
76
<h3>Contents</h3>

‎content/en/docs/1.14/howtos/dist-tracing.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Explore distributed tracing and Kubernetes monitoring
1+
---
2+
title: Distributed Tracing
3+
---
24

35
The Kubernetes monitoring and distributed tracing landscape is hard to grasp. Although this conceptual approach to [observability is nothing new](https://blog.getambassador.io/distributed-tracing-with-java-microdonuts-kubernetes-and-the-ambassador-api-gateway-ace15b62a89e) — companies like New Relic revolutionized single-application performance monitoring (APM) over a decade ago — it took a few years and the [Dapper publication](https://research.google/pubs/pub36356/) for this idea to migrate to distributed applications. The importance of this technology is only increasing, as more and more of us are building [“deep systems”](https://lightstep.com/deep-systems/).
46

‎content/en/docs/1.14/howtos/ext-filters.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
import Alert from '@material-ui/lab/Alert';
2-
3-
# Basic authentication
1+
---
2+
title: Basic Authentication
3+
---
44

55
<Alert severity="info">
66
This guide applies to Ambassador Edge Stack, use of this guide on the Emissary is not recommended. API Gateway does <a href="../basic-auth">authentication using the AuthService resource</a> instead of the Filter resource as described below.

‎content/en/docs/1.14/howtos/external-dns.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
import Alert from '@material-ui/lab/Alert';
2-
3-
# ExternalDNS with Emissary
1+
---
2+
title: ExternalDNS
3+
---
44

55
[ExternalDNS](https://github.com/kubernetes-sigs/external-dns) configures your existing DNS provider to make Kubernetes resources discoverable via public DNS servers by getting resources from the Kubernetes API to create a list of DNS records.
66

‎content/en/docs/1.14/howtos/grpc.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# gRPC Connections
1+
---
2+
title: gRPC
3+
---
24

35
Emissary makes it easy to access your services from outside your application. This includes gRPC services, although a little bit of additional configuration is required: by default, Envoy connects to upstream services using HTTP/1.x and then upgrades to HTTP/2 whenever possible. However, gRPC is built on HTTP/2 and most gRPC servers do not speak HTTP/1.x at all. Emissary must tell its underlying Envoy that your gRPC service only wants to speak to that HTTP/2, using the `grpc` attribute of a `Mapping`.
46

‎content/en/docs/1.14/howtos/istio.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Istio integration
1+
---
2+
title: Istio
3+
---
24

35
Emissary and Istio: Edge Proxy and Service Mesh together in one. Emissary is deployed at the edge of your network and routes incoming traffic to your internal services (aka "north-south" traffic). [Istio](https://istio.io/) is a service mesh for microservices, and is designed to add application-level Layer (L7) observability, routing, and resilience to service-to-service traffic (aka "east-west" traffic). Both Istio and Emissary are built using [Envoy](https://www.envoyproxy.io).
46

‎content/en/docs/1.14/howtos/knative.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# Knative Serverless Framework
1+
---
2+
title: Knative
3+
---
24

35
[Knative](https://knative.dev/) is a popular Kubernetes-based platform for managing serverless workloads with two main components:
46

0 commit comments

Comments
 (0)