redirect article and fix links

Author: cebundy

articles/container-apps/.openpublishing.redirection.container-apps.json

@@ -9,6 +9,11 @@
             "source_path_from_root": "/articles/container-apps/monitor.md",
             "redirect_url": "/azure/container-apps/logging",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/container-apps/ingress.md",
+            "redirect_url": "/azure/container-apps/ingress-overview",
+            "redirect_document_id": false
         }
     ]
 }

articles/container-apps/ingress.md renamed to articles/container-apps/ingress-how-to.md

@@ -26,7 +26,7 @@ You can set the following ingress properties:
 | `exposedPort` | (TCP ingress only) An port for TCP ingress. If `external` is `true`, the value must be unique in the Container Apps environment if ingress is external. | A port number from `1` to `65535`. (can't be `80` or `443`) | No |
 | `external` | Allow ingress to your app from outside its Container Apps environment. |`true` or `false`(default) | Yes |
 | `ipSecurityRestrictions` | IP ingress restrictions. See [Set up IP ingress restrictions](ip-restrictions.md) | array of rules | No |
-| `stickySessions.affinity` | Enables [session affinity](#session-affinity). | `none` (default), `sticky` | No |
+| `stickySessions.affinity` | Enables [session affinity](sticky-sessions.md). | `none` (default), `sticky` | No |
 | `targetPort` | The port your container listens to for incoming requests. | Set this value to the port number that your container uses. For HTTP ingress, your application ingress endpoint is always exposed on port `443`. | Yes |
 | `traffic` | Traffic weights based on revision name or labels. See [Traffic splitting](traffic-splitting.md) | array of rules | No |
 | `transport` | The transport protocol type. | auto (default) detects HTTP/1 or HTTP/2,  `http` for HTTP/1, `http2` for HTTP/2, `tcp` for TCP. | No |

articles/container-apps/ingress-overview.md

@@ -21,7 +21,7 @@ Ingress supports:
 - [IP restrictions](#ip-restrictions)
 - [Authentication](#authentication)
 - [Traffic splitting between revisions](#traffic-splitting)
-- [Session affinity](#sticky-sessions)
+- [Session affinity](#session-affinity)
 
 > [!NOTE]
 > Add diagram here,  Talked with Anthony about this.  He thought that we should consult Ahmed.  I think that we should have a diagram that shows the ingress options and how they work together.

articles/zone-pivot-groups.yml

@@ -1773,6 +1773,15 @@ groups:
     title: Azure portal
   - id: azure-resource-manager
     title: ARM template
+# Owner: cshoe
+- id: arm-portal
+  title: Interaction type
+  prompt: Select how you want to interact with Azure
+  pivots:
+  - id: azure-portal
+    title: Azure portal
+  - id: azure-resource-manager
+    title: ARM template
 # Owner: cebundy
 - id: container-apps-interface-types
   title: Interaction type