Deprecation complete: secrets/index ... (#3554)

docs/concepts/configuration/secret.md

@@ -2,6 +2,9 @@
 assignees:
 - mikedanese
 title: Secrets
+redirect_from:
+- "/docs/user-guide/secrets/index/"
+- "/docs/user-guide/secrets/index.html"
 ---
 
 Objects of type `secret` are intended to hold sensitive information, such as

docs/concepts/ecosystem/thirdpartyresource.md

@@ -2,6 +2,9 @@
 assignees:
 - IanLewis
 title: Third Party Resources
+redirect_from:
+- "/docs/user-guide/thirdpartyresources/"
+- "/docs/user-guide/thirdpartyresources.html"
 ---
 
 * TOC

docs/concepts/overview/working-with-objects/annotations.md

@@ -1,5 +1,8 @@
 ---
 title: Annotations
+redirect_from:
+- "/docs/user-guide/annotations/"
+- "/docs/user-guide/annotations.html"
 ---
 
 {% capture overview %}

docs/concepts/policy/pod-security-policy.md

@@ -2,6 +2,9 @@
 assignees:
 - pweil-
 title: Pod Security Policies
+redirect_from:
+- "/docs/user-guide/pod-security-policy/"
+- "/docs/user-guide/pod-security-policy/index.html"
 ---
 
 Objects of type `PodSecurityPolicy` govern the ability

docs/concepts/policy/security-context.md

@@ -4,6 +4,9 @@ assignees:
 - mikedanese
 - thockin
 title: Security Context
+redirect_from:
+- "/docs/user-guide/security-context/"
+- "/docs/user-guide/security-context.html"
 ---
 
 A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. See [security context design](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/security-context-constraints.md) for more details.

docs/concepts/services-networking/service.md

@@ -2,6 +2,9 @@
 assignees:
 - bprashanth
 title: Services
+redirect_from:
+- "/docs/user-guide/services/"
+- "/docs/user-guide/services/index.html"
 ---
 
 Kubernetes [`Pods`](/docs/user-guide/pods) are mortal. They are born and when they die, they