Skip to content

Commit 99a39c5

Browse files
chalinchalin
authored
[IA] Link normalization step of (#6232)
1 parent a10dc13 commit 99a39c5

File tree

49 files changed

+143
-148
lines changed

Some content is hidden

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

49 files changed

+143
-148
lines changed

‎.htmltest.yml

+5-5
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,8 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored
7575
# TODO move into content/en/blog/2023/contributing-to-otel/index.md once https://github.com/open-telemetry/opentelemetry.io/issues/3889 is implemented
7676
- ^https://shorturl.at/vLYZ0$
7777

78-
# Temporary during IA rework
79-
# https://github.com/open-telemetry/opentelemetry.io/issues/6222
80-
- (^/docs|..)/(faas|kubernetes)\b
81-
- ^../lambda-collector/ # zh/docs/faas/lambda-manual-instrument/index.html
82-
- ^../../(helm|operator)\b # es/docs/kubernetes/collector/components/index.html
78+
# Temporary until semconv is updated to 1.30.0+
79+
- ^https://cloud.google.com/apis/design/resource_names#full_resource_name
80+
- ^https://cloud.google.com/functions/docs/concepts/exec#function_scope_versus_global_scope
81+
- ^https://developer.apple.com/documentation/uikit/uiapplicationdelegate#1656902
82+
- ^https://docs.docker.com/registry/spec/manifest-v2-2/#example-image-manifest

‎content/en/blog/2022/k8s-metadata/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ cSpell:ignore: k8sattributes k8sattributesprocessor k8sprocessor KUBE replicaset
99

1010
{{% alert title="Note" color="info" %}} The most up to date information for how
1111
to enhance telemetry with Kubernetes metadata can be found in the docs. See
12-
[Getting Started with Kubernetes](/docs/kubernetes/getting-started/) for more
12+
[Getting Started with Kubernetes](/docs/platforms/kubernetes/getting-started/) for more
1313
info. {{% /alert %}}
1414

1515
Attaching Kubernetes resource metadata to OpenTelemetry traces is useful to

‎content/en/blog/2022/k8s-otel-expose/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ in this setup are mentioned in brackets.
106106
[v1.2.1] installed.
107107
- A Kubernetes [v1.23.3] edge cluster to create a test cluster. Using
108108
[Kind](https://kind.sigs.k8s.io/) is recommended.
109-
- Installed [OpenTelemetry Operator](/docs/kubernetes/operator/) [v0.58.0] on
109+
- Installed [OpenTelemetry Operator](/docs/platforms/kubernetes/operator/) [v0.58.0] on
110110
both ends.
111111
- Installed [Jaeger Operator](https://www.jaegertracing.io/docs/1.37/operator/)
112112
[v1.37.0] on your public cluster.

‎content/en/blog/2023/contributing-to-otel/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ Feeling a little more adventurous? Then why not join one of the other OTel
145145
(SIGs)? By joining a SIG, you can contribute to things like (but not limited to)
146146
SDK development, auto-instrumentation of libraries, the
147147
[OTel Collector](/docs/collector/), and the
148-
[OTel Operator](/docs/kubernetes/operator/). You don't even need to be a regular
148+
[OTel Operator](/docs/platforms/kubernetes/operator/). You don't even need to be a regular
149149
contributor. Sometimes, contributions come out of necessity. Like maybe you
150150
found a bug in the Collector. Why not take a stab at fixing it? Or maybe there's
151151
a feature that you and your team desperately need. Again, why not take a stab at

‎content/en/blog/2023/end-user-q-and-a-03.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -156,9 +156,9 @@ others are still instrumented using the [legacy OpenTracing
156156
[using shims](/docs/migration/opentracing/).
157157

158158
The OpenTelemetry Operator is being implemented to auto-instrument Java and .NET
159-
code. Among other things, the [OTel Operator](/docs/kubernetes/operator/)
159+
code. Among other things, the [OTel Operator](/docs/platforms/kubernetes/operator/)
160160
supports injecting and
161-
[configuring auto-instrumentation](/docs/kubernetes/operator/automatic/#configure-automatic-instrumentation)
161+
[configuring auto-instrumentation](/docs/platforms/kubernetes/operator/automatic/#configure-automatic-instrumentation)
162162
in .NET, Java, Python, and Node.js. Iris hopes that Go auto-instrumentation will
163163
be available in the near-future. To track progress of auto-instrumentation in
164164
Go, see
@@ -255,7 +255,7 @@ would be a bottleneck in terms of load and single point of failure. The team
255255
currently has one
256256
[OpenTelemetry Collector agent](/docs/collector/deployment/agent/) per
257257
Kubernetes cluster. The end goal is to replace those agents with the
258-
[OTel Operator](/docs/kubernetes/operator/) instead, which allows you to deploy
258+
[OTel Operator](/docs/platforms/kubernetes/operator/) instead, which allows you to deploy
259259
and configure the OTel Collector and inject and configure auto-instrumentation.
260260

261261
Everything is then sent to a central OTel Collector (i.e. an

‎content/en/blog/2023/lambda-release.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ cSpell:ignore: adot otel-faas socha
99
The
1010
[Functions-as-a-Service (FaaS) SIG](https://docs.google.com/document/d/187XYoQcXQ9JxS_5v2wvZ0NEysaJ02xoOYNXj08pT0zc)
1111
is incredibly excited to announce that the release of OpenTelemetry Lambda
12-
layers, and associated [documentation](/docs/faas/) on how to monitor Amazon Web
12+
layers, and associated [documentation](/docs/platforms/faas/) on how to monitor Amazon Web
1313
Services (AWS) Lambdas.
1414

1515
## OTel FaaS repackaged
@@ -42,7 +42,7 @@ The FaaS SIG has addressed the above-mentioned shortcomings:
4242
Collector alongside auto-instrumentation layers for JavaScript, Java, and
4343
Python.
4444
- Added official community Lambda documentation to the OTel website under the
45-
new [FaaS section](/docs/faas/).
45+
new [FaaS section](/docs/platforms/faas/).
4646

4747
## What next
4848

‎content/en/blog/2023/opamp-status/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ with a backlog of issues created to guide further development.
105105
## OpAMP in Kubernetes
106106

107107
In OTel we have dedicated support for Kubernetes as a compute platform via the
108-
[OpenTelemetry Operator for Kubernetes](/docs/kubernetes/operator/). In this
108+
[OpenTelemetry Operator for Kubernetes](/docs/platforms/kubernetes/operator/). In this
109109
context, we're also working on OpAMP support in Kubernetes which will be
110110
available through a
111111
[bridge component](https://docs.google.com/document/d/1M8VLNe_sv1MIfu5bUR5OV_vrMBnAI7IJN-7-IAr37JY/)

‎content/en/blog/2024/prom-and-otel/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -607,7 +607,7 @@ There are a few more Collector components you can implement to monitor
607607
Kubernetes, including Kubernetes-specific ones as well as general-use
608608
processors, such as the batch, memory limiter, and resource processors. To learn
609609
more, see
610-
[Important Components for Kubernetes](/docs/kubernetes/collector/components/).
610+
[Important Components for Kubernetes](/docs/platforms/kubernetes/collector/components/).
611611

612612
After you’ve configured the components in your Collector config file, you need
613613
to enable them within the [pipelines](/docs/collector/configuration/#pipelines)

‎content/en/blog/2025/otel-collector-k8s-discovery.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -70,9 +70,10 @@ So, what if, as a Collector user, you could simply enable automatic discovery
7070
and then let your cluster users tell the Collector how their workloads should be
7171
monitored by annotating their pods properly? That sounds awesome, and it’s not
7272
actually something new. OpenTelemetry already supports auto-instrumentation
73-
through the [Kubernetes operator](/docs/kubernetes/operator/automatic/),
74-
allowing users to instrument their applications automatically just by annotating
75-
their pods. In addition, this is a feature that other monitoring agents in the
73+
through the
74+
[Kubernetes operator](/docs/platforms/kubernetes/operator/automatic/), allowing
75+
users to instrument their applications automatically just by annotating their
76+
pods. In addition, this is a feature that other monitoring agents in the
7677
observability industry already support, and users are familiar with it.
7778

7879
All this motivation led the OpenTelemetry community

‎content/en/docs/collector/installation.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ handling, `Service` configuration based on the OpenTelemetry configuration,
8989
automatic sidecar injection into deployments, and more.
9090

9191
For guidance on how to use the Collector with Kubernetes, see
92-
[Kubernetes Getting Started](/docs/kubernetes/getting-started/).
92+
[Kubernetes Getting Started](/docs/platforms/kubernetes/getting-started/).
9393

9494
## Nomad
9595

@@ -274,8 +274,8 @@ make otelcorecol
274274

275275
[data collection]: /docs/concepts/components/#collector
276276
[deployment methods]: ../deployment/
277-
[opentelemetry helm charts]: /docs/kubernetes/helm/
278-
[opentelemetry operator]: /docs/kubernetes/operator/
277+
[opentelemetry helm charts]: /docs/platforms/kubernetes/helm/
278+
[opentelemetry operator]: /docs/platforms/kubernetes/operator/
279279
[getting started with opentelemetry on hashicorp nomad]:
280280
https://github.com/hashicorp/nomad-open-telemetry-getting-started
281281
[releases]:

‎content/en/docs/collector/scaling.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -139,9 +139,9 @@ load balancer. Using a Sidecar also makes sense to avoid bringing down a crucial
139139
component for all pods in a node when one DaemonSet pod fails.
140140

141141
The sidecar pattern consists in adding a container into the workload pod. The
142-
[OpenTelemetry Operator](/docs/kubernetes/operator/) can automatically add that
143-
for you. To accomplish that, you’ll need an OpenTelemetry Collector CR and
144-
you’ll need to annotate your PodSpec or Pod telling the operator to inject a
142+
[OpenTelemetry Operator](/docs/platforms/kubernetes/operator/) can automatically
143+
add that for you. To accomplish that, you’ll need an OpenTelemetry Collector CR
144+
and you’ll need to annotate your PodSpec or Pod telling the operator to inject a
145145
sidecar:
146146

147147
```yaml
@@ -244,9 +244,9 @@ Collector. For instance, each Collector could be responsible for one Kubernetes
244244
namespace or specific labels on the workloads.
245245
246246
Another way of scaling the Prometheus receiver is to use the
247-
[Target Allocator](/docs/kubernetes/operator/target-allocator/): it’s an extra
248-
binary that can be deployed as part of the OpenTelemetry Operator and will
249-
distribute Prometheus scrape targets for a given configuration across the
247+
[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/): it’s
248+
an extra binary that can be deployed as part of the OpenTelemetry Operator and
249+
will distribute Prometheus scrape targets for a given configuration across the
250250
cluster of Collectors. You can use a Custom Resource (CR) like the following to
251251
make use of the Target Allocator:
252252

‎content/en/docs/concepts/components.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ The OpenTelemetry Operator is an implementation of a Kubernetes Operator. The
126126
operator manages the OpenTelemetry Collector and auto-instrumentation of the
127127
workloads using OpenTelemetry.
128128

129-
For more information, see [K8s Operator](/docs/kubernetes/operator/).
129+
For more information, see [K8s Operator](/docs/platforms/kubernetes/operator/).
130130

131131
## Function as a Service assets
132132

@@ -136,4 +136,4 @@ provides pre-built Lambda layers able to auto-instrument your application as
136136
well as the option of a standalone Collector Lambda layer that can be used when
137137
instrumenting applications manually or automatically.
138138

139-
For more information, see [Functions as a Service](/docs/faas/).
139+
For more information, see [Functions as a Service](/docs/platforms/faas/).

‎content/en/docs/contributing/localization.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ command:
140140

141141
```console
142142
$ npm run check:i18n
143-
1 1 content/en/docs/kubernetes/_index.md - content/zh/docs/kubernetes/_index.md
143+
1 1 content/en/docs/platforms/kubernetes/_index.md - content/zh/docs/platforms/kubernetes/_index.md
144144
...
145145
```
146146

@@ -158,11 +158,11 @@ of the corresponding English language pages by using the `-d` flag and providing
158158
the paths to your localized pages, or omit the paths to see all. For example:
159159

160160
```console
161-
$ npm run check:i18n -- -d content/zh/docs/kubernetes
162-
diff --git a/content/en/docs/kubernetes/_index.md b/content/en/docs/kubernetes/_index.md
161+
$ npm run check:i18n -- -d content/zh/docs/platforms/kubernetes
162+
diff --git a/content/en/docs/platforms/kubernetes/_index.md b/content/en/docs/platforms/kubernetes/_index.md
163163
index 3592df5d..c7980653 100644
164-
--- a/content/en/docs/kubernetes/_index.md
165-
+++ b/content/en/docs/kubernetes/_index.md
164+
--- a/content/en/docs/platforms/kubernetes/_index.md
165+
+++ b/content/en/docs/platforms/kubernetes/_index.md
166166
@@ -1,7 +1,7 @@
167167
---
168168
title: OpenTelemetry with Kubernetes

‎content/en/docs/demo/kubernetes-deployment.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,9 @@ aliases: [kubernetes_deployment]
55
cSpell:ignore: loadgen otlphttp spanmetrics
66
---
77

8-
We provide a [OpenTelemetry Demo Helm chart](/docs/kubernetes/helm/demo/) to
9-
help deploy the demo to an existing Kubernetes cluster.
8+
We provide a
9+
[OpenTelemetry Demo Helm chart](/docs/platforms/kubernetes/helm/demo/) to help
10+
deploy the demo to an existing Kubernetes cluster.
1011

1112
[Helm](https://helm.sh) must be installed to use the charts. Please refer to
1213
Helm's [documentation](https://helm.sh/docs/) to get started.

‎content/en/docs/getting-started/ops.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ following:
1717
- [What is OpenTelemetry?](../../what-is-opentelemetry/)
1818
- [How can I instrument applications without touching their code?](../../concepts/instrumentation/zero-code/)
1919
- [How can I set up a collector?](../../collector/)
20-
- [How can I get automation for Kubernetes with the OpenTelemetry Operator?](../../kubernetes/operator/)
20+
- [How can I get automation for Kubernetes with the OpenTelemetry Operator?](../../platforms/kubernetes/operator/)
2121

2222
If you are looking for a set of applications to try things out, you will find
2323
our official [OpenTelemetry demo](/ecosystem/demo/) useful.

‎content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md

+6-5
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,12 @@ cSpell:ignore: bleh targetallocator
44
---
55

66
If you’ve enabled
7-
[Target Allocator](/docs/kubernetes/operator/target-allocator/) service
8-
discovery on the [OpenTelemetry Operator](/docs/kubernetes/operator/), and the
9-
Target Allocator is failing to discover scrape targets, there are a few
10-
troubleshooting steps that you can take to help you understand what’s going on
11-
and restore normal operation.
7+
[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/)
8+
service discovery on the
9+
[OpenTelemetry Operator](/docs/platforms/kubernetes/operator/), and the Target
10+
Allocator is failing to discover scrape targets, there are a few troubleshooting
11+
steps that you can take to help you understand what’s going on and restore
12+
normal operation.
1213

1314
## Troubleshooting steps
1415

‎content/en/docs/languages/_index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,6 @@ The list above is aliased to [`/api`](/api).
5454

5555
{{% /alert %}}
5656

57-
[zero-code]: /docs/kubernetes/operator/automatic/
57+
[zero-code]: /docs/platforms/kubernetes/operator/automatic/
5858
[instrumentation]: /docs/concepts/instrumentation/
59-
[otel-op]: /docs/kubernetes/operator/
59+
[otel-op]: /docs/platforms/kubernetes/operator/

‎content/en/docs/languages/js/serverless.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ OpenTelemetry instrumentation libraries.
1313
{{% alert title="Note" color="info" %}}
1414

1515
You can also automatically instrument your AWS Lambda functions by using the
16-
[community provided Lambda layers](/docs/faas/lambda-auto-instrument/).
16+
[community provided Lambda layers](/docs/platforms/faas/lambda-auto-instrument/).
1717

1818
{{% /alert %}}
1919

‎content/en/docs/platforms/faas/_index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ linkTitle: FaaS
44
description: >-
55
OpenTelemetry supports various methods of monitoring Function-as-a-Service
66
provided by different cloud vendors
7-
redirects: [{ from: /docs/faas/*, to: ':splat' }] # cSpell:disable-line
7+
redirects: [{ from: /docs/platforms/faas/*, to: ':splat' }] # cSpell:disable-line
88
---
99

1010
Functions as a Service (FaaS) is an important serverless compute platform for

‎content/en/docs/platforms/kubernetes/_index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: OpenTelemetry with Kubernetes
33
linkTitle: Kubernetes
4-
redirects: [{ from: /docs/kubernetes/*, to: ':splat' }]
4+
redirects: [{ from: /docs/platforms/kubernetes/*, to: ':splat' }]
55
---
66

77
[Kubernetes](https://kubernetes.io/) is an open source system for automated

‎content/en/docs/platforms/kubernetes/helm/_index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ linkTitle: Helm Charts
1010
If you chose to use Helm, you can use
1111
[OpenTelemetry Helm Charts](https://github.com/open-telemetry/opentelemetry-helm-charts)
1212
to manage installs of the [OpenTelemetry Collector](/docs/collector),
13-
[OpenTelemetry Operator](/docs/kubernetes/operator), and
13+
[OpenTelemetry Operator](/docs/platforms/kubernetes/operator), and
1414
[OpenTelemetry Demo](/docs/demo).
1515

1616
Add the OpenTelemetry Helm repository with:

‎content/en/docs/platforms/kubernetes/helm/collector.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -170,8 +170,8 @@ This feature is disabled by default. It has the following requirements in order
170170
to be safely enabled:
171171

172172
- It requires the
173-
[Filelog receiver](/docs/kubernetes/collector/components/#filelog-receiver) be
174-
included in the Collector image, such as the
173+
[Filelog receiver](/docs/platforms/kubernetes/collector/components/#filelog-receiver)
174+
be included in the Collector image, such as the
175175
[Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
176176
- Although not a strict requirement, it is recommended this preset be used with
177177
`mode=daemonset`. The `filelogreceiver` will only be able to collect logs on
@@ -238,7 +238,7 @@ Due to RBAC considerations, this feature is disabled by default. It has the
238238
following requirements:
239239

240240
- It requires the
241-
[Kubernetes Attributes processor](/docs/kubernetes/collector/components/#kubernetes-attributes-processor)
241+
[Kubernetes Attributes processor](/docs/platforms/kubernetes/collector/components/#kubernetes-attributes-processor)
242242
be included in the Collector image, such as the
243243
[Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
244244

@@ -263,7 +263,7 @@ container metrics from the API server on a kubelet.
263263
This feature is disabled by default. It has the following requirements:
264264

265265
- It requires the
266-
[Kubeletstats receiver](/docs/kubernetes/collector/components/#kubeletstats-receiver)
266+
[Kubeletstats receiver](/docs/platforms/kubernetes/collector/components/#kubeletstats-receiver)
267267
be included in the Collector image, such as the
268268
[Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
269269
- Although not a strict requirement, it is recommended this preset be used with
@@ -293,7 +293,7 @@ collected by Kube State Metrics.
293293
This feature is disabled by default. It has the following requirements:
294294

295295
- It requires the
296-
[Kubernetes Cluster receiver](/docs/kubernetes/collector/components/#kubernetes-cluster-receiver)
296+
[Kubernetes Cluster receiver](/docs/platforms/kubernetes/collector/components/#kubernetes-cluster-receiver)
297297
be included in the Collector image, such as the
298298
[Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
299299
- Although not a strict requirement, it is recommended this preset be used with
@@ -321,7 +321,7 @@ The OpenTelemetry Collector can be configured to collect Kubernetes events.
321321
This feature is disabled by default. It has the following requirements:
322322

323323
- It requires the
324-
[Kubernetes Objects receiver](/docs/kubernetes/collector/components/#kubernetes-objects-receiver)
324+
[Kubernetes Objects receiver](/docs/platforms/kubernetes/collector/components/#kubernetes-objects-receiver)
325325
be included in the Collector image, such as the
326326
[Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
327327
- Although not a strict requirement, it is recommended this preset be used with
@@ -351,7 +351,7 @@ Kubernetes nodes.
351351
This feature is disabled by default. It has the following requirements:
352352

353353
- It requires the
354-
[Host Metrics receiver](/docs/kubernetes/collector/components/#host-metrics-receiver)
354+
[Host Metrics receiver](/docs/platforms/kubernetes/collector/components/#host-metrics-receiver)
355355
be included in the Collector image, such as the
356356
[Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
357357
- Although not a strict requirement, it is recommended this preset be used with

‎content/en/docs/platforms/kubernetes/helm/operator.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,14 @@ linkTitle: Operator Chart
55

66
## Introduction
77

8-
The [OpenTelemetry Operator](/docs/kubernetes/operator) is a Kubernetes operator
9-
that manages [OpenTelemetry Collectors](/docs/collector) and
8+
The [OpenTelemetry Operator](/docs/platforms/kubernetes/operator) is a
9+
Kubernetes operator that manages [OpenTelemetry Collectors](/docs/collector) and
1010
auto-instrumentation of workloads. One of the ways to install the OpenTelemetry
1111
Operator is via the
1212
[OpenTelemetry Operator Helm Chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-operator).
1313

1414
For detailed use of the OpenTelemetry Operator visit its
15-
[docs](/docs/kubernetes/operator).
15+
[docs](/docs/platforms/kubernetes/operator).
1616

1717
### Installing the Chart
1818

‎content/en/docs/platforms/kubernetes/operator/_index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@ description:
88
aliases:
99
- /docs/operator
1010
- /docs/k8s-operator
11-
- /docs/kubernetes-operator
11+
- /docs/platforms/kubernetes-operator
1212
redirects:
1313
- { from: /docs/operator/*, to: ':splat' }
1414
- { from: /docs/k8s-operator/*, to: ':splat' }
15-
- { from: /docs/kubernetes-operator/*, to: ':splat' }
15+
- { from: /docs/platforms/kubernetes-operator/*, to: ':splat' }
1616
---
1717

1818
## Introduction

0 commit comments

Comments
 (0)