Update a note indicating current state of Federation V1 (#8165)
* Update a note indicating current state of federation V1 * change horizontal line to <br> * edit note * capitalize Kubernetes * <br> unnecessary w/ note callout
This commit is contained in:
committed by
k8s-ci-robot
parent
d623f631fd
commit
0db6882288
@@ -0,0 +1,7 @@
|
||||
**Note:** `Federation V1`, the current Kubernetes federation API which reuses the Kubernetes API
|
||||
resources 'as is', is currently considered alpha for many of its features, and there is no clear
|
||||
path to evolve the API to GA. However, there is a `Federation V2` effort in progress to implement
|
||||
a dedicated federation API apart from the Kubernetes API. The details can be found at
|
||||
[sig-multicluster community page](https://github.com/kubernetes/community/tree/master/sig-multicluster).
|
||||
{: .note}
|
||||
|
||||
@@ -4,6 +4,8 @@ title: Federated Cluster
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use Clusters API resource in a Federation control plane.
|
||||
|
||||
Different than other Kubernetes resources, such as Deployments, Services and ConfigMaps,
|
||||
|
||||
@@ -4,6 +4,8 @@ title: Federated ConfigMap
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use ConfigMaps in a Federation control plane.
|
||||
|
||||
Federated ConfigMaps are very similar to the traditional [Kubernetes
|
||||
|
||||
@@ -3,6 +3,9 @@ title: Federated DaemonSet
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use DaemonSets in a federation control plane.
|
||||
|
||||
DaemonSets in the federation control plane ("Federated Daemonsets" in
|
||||
|
||||
@@ -3,6 +3,9 @@ title: Federated Deployment
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use Deployments in the Federation control plane.
|
||||
|
||||
Deployments in the federation control plane (referred to as "Federated Deployments" in
|
||||
|
||||
@@ -2,6 +2,8 @@
|
||||
title: Federated Events
|
||||
---
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use events in federation control plane to help in debugging.
|
||||
|
||||
|
||||
|
||||
@@ -6,6 +6,8 @@ title: Federated Horizontal Pod Autoscalers (HPA)
|
||||
|
||||
{% include feature-state-alpha.md %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use federated horizontal pod autoscalers (HPAs) in the federation control plane.
|
||||
|
||||
HPAs in the federation control plane are similar to the traditional [Kubernetes
|
||||
|
||||
@@ -3,6 +3,9 @@ title: Federated Ingress
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This page explains how to use Kubernetes Federated Ingress to deploy
|
||||
a common HTTP(S) virtual IP load balancer across a federated service running in
|
||||
multiple Kubernetes clusters. As of v1.4, clusters hosted in Google
|
||||
|
||||
@@ -3,6 +3,9 @@ title: Federated Jobs
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use jobs in the federation control plane.
|
||||
|
||||
Jobs in the federation control plane (referred to as "federated jobs" in
|
||||
|
||||
@@ -3,6 +3,9 @@ title: Federated Namespaces
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use Namespaces in Federation control plane.
|
||||
|
||||
Namespaces in federation control plane (referred to as "federated Namespaces" in
|
||||
|
||||
@@ -3,6 +3,9 @@ title: Federated ReplicaSets
|
||||
---
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use ReplicaSets in the Federation control plane.
|
||||
|
||||
ReplicaSets in the federation control plane (referred to as "federated ReplicaSets" in
|
||||
|
||||
@@ -2,6 +2,8 @@
|
||||
title: Federated Secrets
|
||||
---
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use secrets in Federation control plane.
|
||||
|
||||
* TOC
|
||||
|
||||
@@ -5,6 +5,8 @@ reviewers:
|
||||
title: Cross-cluster Service Discovery using Federated Services
|
||||
---
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This guide explains how to use Kubernetes Federated Services to deploy
|
||||
a common Service across multiple Kubernetes clusters. This makes it
|
||||
easy to achieve cross-cluster service discovery and availability zone
|
||||
|
||||
@@ -4,6 +4,8 @@ reviewers:
|
||||
title: Set up Cluster Federation with Kubefed
|
||||
---
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
* TOC
|
||||
{:toc}
|
||||
|
||||
|
||||
@@ -4,6 +4,8 @@ title: Set up CoreDNS as DNS provider for Cluster Federation
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This page shows how to configure and deploy CoreDNS to be used as the
|
||||
DNS provider for Cluster Federation.
|
||||
|
||||
|
||||
@@ -4,6 +4,8 @@ title: Set up placement policies in Federation
|
||||
|
||||
{% capture overview %}
|
||||
|
||||
{% include federation-current-state.md %}
|
||||
|
||||
This page shows how to enforce policy-based placement decisions over Federated
|
||||
resources using an external policy engine.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user