From 3ff8ba579e5783790dc3e5ca990851bf66288c9e Mon Sep 17 00:00:00 2001 From: jarpat Date: Tue, 30 Jan 2024 10:54:40 -0500 Subject: [PATCH] remove experimental --- docs/user/PostgreSQL.md | 4 ++-- roles/baseline/defaults/main.yml | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/user/PostgreSQL.md b/docs/user/PostgreSQL.md index 969578f0..9c2f1279 100644 --- a/docs/user/PostgreSQL.md +++ b/docs/user/PostgreSQL.md @@ -2,7 +2,7 @@ * [PostgreSQL](#postgresql) * [Use IAC To Create an External PostgreSQL Database Cluster](#use-iac-to-create-an-external-postgresql-database-cluster) - * [Post Data Transfer Steps for viya4-deployment (Experimental)](#post-data-transfer-steps-for-viya4-deployment-experimental) + * [Post Data Transfer Steps for viya4-deployment](#post-data-transfer-steps-for-viya4-deployment) * [Crunchy Data 5](#crunchy-data-5) * [Crunchy Data 4](#crunchy-data-4) @@ -18,7 +18,7 @@ To use the IAC project to create an external PostgreSQL database cluster, refer [GCP PostgreSQL Cluster](https://github.com/sassoftware/viya4-iac-gcp/blob/main/docs/CONFIG-VARS.md#postgres-servers) -## Post Data Transfer Steps for viya4-deployment (Experimental) +## Post Data Transfer Steps for viya4-deployment After you complete the steps outlined in the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) to move your data from an internal PostgreSQL server to an external PostgreSQL cluster, you can use the viya4-deployment project to manage your installation again. diff --git a/roles/baseline/defaults/main.yml b/roles/baseline/defaults/main.yml index 3c052391..76d8e97c 100644 --- a/roles/baseline/defaults/main.yml +++ b/roles/baseline/defaults/main.yml @@ -80,6 +80,8 @@ INGRESS_NGINX_AWS_NLB_CONFIG: service: annotations: service.beta.kubernetes.io/aws-load-balancer-type: nlb + service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: "foobar=test,env=jarpat" + # Ingress-nginx - CVE-2021-25742 Mitigation INGRESS_NGINX_CVE_2021_25742_PATCH: