From d392ad445853c0ba648d7287e85554579a3b8703 Mon Sep 17 00:00:00 2001
From: Alex Parker <7272359+ajp-io@users.noreply.github.com>
Date: Tue, 22 Oct 2024 16:57:26 -0400
Subject: [PATCH 1/5] Doc new --cidr flag
---
docs/reference/embedded-cluster-install.mdx | 18 +++++-------------
docs/vendor/embedded-disaster-recovery.mdx | 2 +-
2 files changed, 6 insertions(+), 14 deletions(-)
diff --git a/docs/reference/embedded-cluster-install.mdx b/docs/reference/embedded-cluster-install.mdx
index 22541ff058..176e483aea 100644
--- a/docs/reference/embedded-cluster-install.mdx
+++ b/docs/reference/embedded-cluster-install.mdx
@@ -74,7 +74,7 @@ sudo ./APP_SLUG install --license LICENSE_FILE [flags]
To ensure your application's internal cluster communication is not proxied, use fully qualified domain names like `my-service.my-namespace.svc` or `my-service.my-namespace.svc.cluster.local`.
- | `--service-cidr` |
-
- The range of IP addresses that can be assigned to Services, in CIDR notation. **Default:** By default, the Service CIDR is `10.96.0.0/12`.
- **Limitation:** The `--service-cidr` flags is not supported on Red Hat Enterprise Linux (RHEL) 9 operating systems.
+ The range of IP addresses that can be assigned to Pods and Services, in CIDR notation. **Default:** By default, the CIDR is `10.244.0.0/16`.
|
@@ -130,8 +122,8 @@ Where:
* `HOST:PORT` is the host and port of the proxy server
* `LIST_OF_HOSTS` is the list of hosts to not proxy. For example, the IP address of the node where you are installing. Or, for multi-node clusters, the list of IP addresses for all nodes in the cluster, typically in CIDR notation.
-### Set IP Address Range for Pods
+### Set IP Address Range for Pods and Services
```bash
-sudo ./my-app install --license license.yaml --pod-cidr 172.16.136.0/16
+sudo ./my-app install --license license.yaml --cidr 172.16.136.0/16
```
\ No newline at end of file
diff --git a/docs/vendor/embedded-disaster-recovery.mdx b/docs/vendor/embedded-disaster-recovery.mdx
index ab048853ba..c76016b431 100644
--- a/docs/vendor/embedded-disaster-recovery.mdx
+++ b/docs/vendor/embedded-disaster-recovery.mdx
@@ -142,7 +142,7 @@ To restore from a backup:
* If the installation is behind a proxy, the same proxy settings provided during install must be provided to the restore command using `--http-proxy`, `--https-proxy`, and `--no-proxy`. For more information, see [Install Behind a Proxy](/enterprise/installing-embedded#proxy).
- * If the `--pod-cidr` and `--service-cidr` flags were used during install to the set IP address ranges for Pods and Services, these flags must be provided with the same CIDRs during the restore. If these flags are not provided or are provided with different CIDRs, the restore will fail with an error message telling you to rerun with the appropriate flags and values. However, it will take some time before that error occurs. For more information, see [Set IP Address Ranges for Pods and Services](/enterprise/installing-embedded#set-ip-address-ranges-for-pods-and-services).
+ * If the `--cidr` flag was used during install to the set IP address ranges for Pods and Services, this flag must be provided with the same CIDR during the restore. If this flag is not provided or is provided with a different CIDR, the restore will fail with an error message telling you to rerun with the appropriate value. However, it will take some time before that error occurs. For more information, see [Set IP Address Ranges for Pods and Services](/enterprise/installing-embedded#set-ip-address-ranges-for-pods-and-services).
* If the `--local-artifact-mirror-port` flag was used during install to change the port for the Local Artifact Mirror (LAM), you can optionally use the `--local-artifact-mirror-port` flag to choose a different LAM port during restore. For example, `restore --local-artifact-mirror-port=50000`. If no LAM port is provided during restore, the LAM port that was supplied during installation will be used. For more information, see [Change Admin Console and LAM Ports](/enterprise/installing-embedded#adm-lam-ports).
From c517cccb4bac00040ddad26663d3b701900781d8 Mon Sep 17 00:00:00 2001
From: replicated-ci <90716069+replicated-ci@users.noreply.github.com>
Date: Wed, 23 Oct 2024 03:21:24 +0000
Subject: [PATCH 2/5] App Manager v1.119.1 release notes (#2762)
Co-authored-by: replicated-ci-kots
---
docs/release-notes/rn-app-manager.md | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/docs/release-notes/rn-app-manager.md b/docs/release-notes/rn-app-manager.md
index d06209fab4..dff32b6a24 100644
--- a/docs/release-notes/rn-app-manager.md
+++ b/docs/release-notes/rn-app-manager.md
@@ -18,6 +18,16 @@ The following table lists the versions of Kubernetes that are compatible with ea
+## 1.119.1
+
+Released on October 22, 2024
+
+Support for Kubernetes: 1.29, 1.30, and 1.31
+
+### Bug Fixes {#bug-fixes-1-119-1}
+* Fixes an issue that causes proxy settings to be removed on `kotsadm admin-console upgrade`.
+* Fixes an issue that causes `--strict-security-context` to be removed on `kotsadm admin-console upgrade`.
+
## 1.119.0
Released on October 18, 2024
From 45e723da0010db0eb4c48a6c178cbcc7275bdaf5 Mon Sep 17 00:00:00 2001
From: Alex Parker <7272359+ajp-io@users.noreply.github.com>
Date: Wed, 23 Oct 2024 11:25:35 -0500
Subject: [PATCH 3/5] Mention that we add node IP to no-proxy
---
docs/reference/embedded-cluster-install.mdx | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/reference/embedded-cluster-install.mdx b/docs/reference/embedded-cluster-install.mdx
index 176e483aea..4076131d86 100644
--- a/docs/reference/embedded-cluster-install.mdx
+++ b/docs/reference/embedded-cluster-install.mdx
@@ -70,11 +70,11 @@ sudo ./APP_SLUG install --license LICENSE_FILE [flags]
`--no-proxy` |
Comma-separated list of hosts for which not to use a proxy.
- For single-node installations, pass the IP address of the node where you are installing. For multi-node installations, when deploying the first node, pass the list of IP addresses for all nodes in the cluster (typically in CIDR notation).
+ For single-node installations, pass the IP address of the node where you are installing. For multi-node installations, when deploying the first node, pass the list of IP addresses for all nodes in the cluster (typically in CIDR notation). The default network interface's subnet will automatically be added to the no-proxy list if the node's IP address isn't already included.
The following are never proxied:
- Internal cluster communication (`localhost`, `127.0.0.1`, `.cluster.local`, `.svc`)
- - The CIDR used for assigning IPs to Kubernetes Pods and Services. By default, the CIDR is `10.244.0.0/16`. For information about how to change this default, see [Set IP Address Ranges for Pods and Services](#set-ip-address-ranges-for-pods-and-services).
+ - The CIDR block used for assigning IPs to Kubernetes Pods and Services. By default, the CIDR block is `10.244.0.0/16`. For information about how to change this default, see [Set IP Address Range for Pods and Services](#set-ip-address-range-for-pods-and-services).
To ensure your application's internal cluster communication is not proxied, use fully qualified domain names like `my-service.my-namespace.svc` or `my-service.my-namespace.svc.cluster.local`.
@@ -84,7 +84,7 @@ sudo ./APP_SLUG install --license LICENSE_FILE [flags]
|
| `--cidr` |
- The range of IP addresses that can be assigned to Pods and Services, in CIDR notation. **Default:** By default, the CIDR is `10.244.0.0/16`.
+ The range of IP addresses that can be assigned to Pods and Services, in CIDR notation. **Default:** By default, the CIDR block is `10.244.0.0/16`.
|
From df549b84e30aebe28eabe793ecf90ea40de58f76 Mon Sep 17 00:00:00 2001
From: Alex Parker <7272359+ajp-io@users.noreply.github.com>
Date: Thu, 24 Oct 2024 07:54:08 -0700
Subject: [PATCH 4/5] Update embedded-cluster-install.mdx
---
docs/reference/embedded-cluster-install.mdx | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/reference/embedded-cluster-install.mdx b/docs/reference/embedded-cluster-install.mdx
index 4076131d86..369886a996 100644
--- a/docs/reference/embedded-cluster-install.mdx
+++ b/docs/reference/embedded-cluster-install.mdx
@@ -70,7 +70,7 @@ sudo ./APP_SLUG install --license LICENSE_FILE [flags]
`--no-proxy` |
Comma-separated list of hosts for which not to use a proxy.
- For single-node installations, pass the IP address of the node where you are installing. For multi-node installations, when deploying the first node, pass the list of IP addresses for all nodes in the cluster (typically in CIDR notation). The default network interface's subnet will automatically be added to the no-proxy list if the node's IP address isn't already included.
+ For single-node installations, pass the IP address of the node where you are installing. For multi-node installations, when deploying the first node, pass the list of IP addresses for all nodes in the cluster (typically in CIDR notation). The network interface's subnet will automatically be added to the no-proxy list if the node's IP address isn't already included.
The following are never proxied:
- Internal cluster communication (`localhost`, `127.0.0.1`, `.cluster.local`, `.svc`)
@@ -126,4 +126,4 @@ Where:
```bash
sudo ./my-app install --license license.yaml --cidr 172.16.136.0/16
-```
\ No newline at end of file
+```
From b8fef8ba6f006c20ca674242525169c43a37d5c9 Mon Sep 17 00:00:00 2001
From: Paige Calvert
Date: Thu, 24 Oct 2024 10:38:36 -0600
Subject: [PATCH 5/5] Update embedded-cluster-install.mdx
---
docs/reference/embedded-cluster-install.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/reference/embedded-cluster-install.mdx b/docs/reference/embedded-cluster-install.mdx
index 369886a996..8164a52702 100644
--- a/docs/reference/embedded-cluster-install.mdx
+++ b/docs/reference/embedded-cluster-install.mdx
@@ -70,7 +70,7 @@ sudo ./APP_SLUG install --license LICENSE_FILE [flags]
`--no-proxy` |
Comma-separated list of hosts for which not to use a proxy.
- For single-node installations, pass the IP address of the node where you are installing. For multi-node installations, when deploying the first node, pass the list of IP addresses for all nodes in the cluster (typically in CIDR notation). The network interface's subnet will automatically be added to the no-proxy list if the node's IP address isn't already included.
+ For single-node installations, pass the IP address of the node where you are installing. For multi-node installations, when deploying the first node, pass the list of IP addresses for all nodes in the cluster (typically in CIDR notation). The network interface's subnet will automatically be added to the no-proxy list if the node's IP address is not already included.
The following are never proxied:
- Internal cluster communication (`localhost`, `127.0.0.1`, `.cluster.local`, `.svc`)
| |