Merge branch 'main' into licensem-management-10-2023

 Conflicts:
	content/en/getting-started/api-key.md
	content/en/references/configuration.md
	content/en/user-guide/aws/elastic-compute-cloud/index.md
	content/en/user-guide/ci/circle-ci/index.md
	content/en/user-guide/tools/cloud-pods/getting-started/index.md

.github/workflows/github-pages.yml

@@ -23,7 +23,7 @@ jobs:
           extended: true
 
       - name: Setup Node
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
           node-version: '16'
 

.github/workflows/markdown.links.config.json

@@ -33,12 +33,15 @@
         {
             "pattern": "http://localstack_main:4566"
         },
+        {
+            "pattern": "http://localstack-main:4566"
+        },
         {
             "pattern": "(.*)localhost.localstack.cloud(.*)"
         },
         {
             "pattern": "https://localhost:4566/(.*)"
-        }
+        },
         {
             "pattern": "https://localhost:45139/"
         }

.github/workflows/preview-build.yml

@@ -22,7 +22,7 @@ jobs:
           extended: true
 
       - name: Setup Node
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
           node-version: '16'
 

CODEOWNERS

@@ -115,4 +115,4 @@
 /content/en/user-guide/aws/transcribe/ @sannya-singal @ackdav
 
 # xray
-/content/en/user-guide/aws/xray/ @joe4dev
+/content/en/user-guide/aws/xray/ @joe4dev

content/en/contributing/integration-tests.md

@@ -147,16 +147,14 @@ region=eu-central-1
 -   Use the client `fixtures` and other fixtures for resource creation instead of methods from `aws_stack.py`
     -   While using the environment variable `TEST_TARGET=AWS_CLOUD`, the boto client will be automatically configured to target AWS instead of LocalStack.
 -   Configure your AWS profile/credentials:
-    -   When running the test, set the environment variable `AWS_PROFILE` to the profile name you chose in the previous step. Eexample: `AWS_PROFILE=ls-sandbox`
+    -   When running the test, set the environment variable `AWS_PROFILE` to the profile name you chose in the previous step. Example: `AWS_PROFILE=ls-sandbox`
 -   Ensure that all resources are cleaned up even when the test fails and even when other fixture cleanup operations fail!
 -   Testing against AWS might require additional roles and policies.
 
 Here is how a useful environment configuration for testing against AWS could look like:
 
 ```bash
-EDGE_BIND_HOST=0.0.0.0;
-DEBUG=1;
-DNS_ADDRESS=0;
+DEBUG=1;  # enables debug logging
 TEST_DISABLE_RETRIES_AND_TIMEOUTS=1;
 TEST_TARGET=AWS_CLOUD;
 AWS_DEFAULT_REGION=us-east-1;

content/en/getting-started/faq.md

@@ -83,10 +83,10 @@ ports:
        …
 ```
 
-Furthermore, use either the default name `localstack_main` for the container, or alternatively configure the environment variable `MAIN_CONTAINER_NAME` to point to the correct name.
+Furthermore, use either the default name `localstack-main` for the container, or alternatively configure the environment variable `MAIN_CONTAINER_NAME` to point to the correct name.
 
 ```yaml
-container_name: localstack_main
+container_name: localstack-main
 ```
 
 Ensure that `127.0.0.1` is configured as the target DNS server for the `bigdata` container:
@@ -117,23 +117,10 @@ sudo sysctl -w net.ipv4.ip_forward=1
 
 ### Why can't my other Docker containers reach LocalStack?
 
-Using LocalStack inside a Docker network with multiple other containers can lead to connectivity issues from/to those containers. For example, a container which attempts to deploy a stack and interact with the services directly, from within the same Docker network.
+Using LocalStack inside a Docker network with multiple other containers can lead to connectivity issues from/to those containers.
+For example, a container which attempts to deploy a stack and interact with the services directly, from within the same Docker network.
 
-To resolve this, set `HOSTNAME_EXTERNAL` for correct response values for endpoints. Use network aliases to ensure resolution of `localhost.localstack.cloud` to the correct container:
-
-```yaml
-...
-    networks:
-      default:
-        aliases:
-          - localhost.localstack.cloud
-  sdkstack:
-    image: ubuntu
-    command: ["bash", "-c", "apt update && apt install -y curl && sleep 5 && curl -v http://localhost.localstack.cloud:4566/_localstack/health"]
-...
-```
-
-Note the missing `network: bridge` here! The default bridge network does not support DNS name resolution.
+Refer to our [network troubleshooting guide]({{< ref "references/network-troubleshooting" >}}) covering several scenarios.
 
 ### How to resolve the pull rate limit issue for LocalStack's Docker image?
 

content/en/getting-started/installation.md

@@ -244,7 +244,7 @@ version: "3.8"
 
 services:
   localstack:
-    container_name: "${LOCALSTACK_DOCKER_NAME-localstack_main}"
+    container_name: "${LOCALSTACK_DOCKER_NAME-localstack-main}"
     image: localstack/localstack
     ports:
       - "127.0.0.1:4566:4566"            # LocalStack Gateway
@@ -261,7 +261,7 @@ version: "3.8"
 
 services:
   localstack:
-    container_name: "${LOCALSTACK_DOCKER_NAME-localstack_main}"
+    container_name: "${LOCALSTACK_DOCKER_NAME-localstack-main}"
     image: localstack/localstack-pro  # required for Pro
     ports:
       - "127.0.0.1:4566:4566"            # LocalStack Gateway

content/en/overview/_index.html

@@ -15,6 +15,22 @@
 
 <div class="doc-overview-grid container section-index">
 
+  <div class="pageinfo pageinfo-primary">
+    <p class="banner-title"><b>LocalStack v3!</b></p>
+    <p>
+      We are excited to announce that we are once more <b>preparing a major release of LocalStack</b>.
+      This release will introduce a lot of great new features, but will also clean up some legacy code and configurations.
+      This <a href="https://discuss.localstack.cloud/t/upcoming-changes-for-localstack-v3/576" target="_blank">Discuss Post</a> is meant to give you a heads-up on the upcoming changes such that you can already prepare your LocalStack setup accordingly.
+    </p>
+    <ul>
+      <li><b>Thursday November 9., 2023</b>: The release candidate for v3.0.0 will be released
+        into the latest Docker image tags. This will put into effect all breaking
+        changes that we are introducing for v3, and will affect your pipeline if you
+        are using latest.</li>
+      <li><b>Thursday November 16., 2023</b>: The v3.0.0 tagged release images will be published.</li>
+    </ul>
+  </div>
+
   <div class="row mb-3 justify-content-center">
     <div class="col-auto mb-2">
       <img src="/images/localstack.svg" alt="LocalStack logo" width="75px">