search

sassoftware / viya4-deployment

This project contains Ansible code that creates a baseline in an existing Kubernetes environment for use with the SAS Viya Platform, generates the manifest for an order, and then can also deploy that order into the Kubernetes environment specified.
Apache License 2.0
71 stars 64 forks source link

feat: (IAC-557) Add GKE pod subnet cidr to LOADBALANCER_SOURCE_RANGES #309

Closed jarpat closed 2 years ago

jarpat commented 2 years ago

Changes

When performing a deployment in GKE, the new tasks add the GKE pod subnet cidr to LOADBALANCER_SOURCE_RANGES to allow for N/S traffic

Tests

Additional details are contained in internal ticket

Scenario 1

Updated viya4-iac-gcp and viya4-deployment, gke_pod_subnet_cidr is automatically added to LOADBALANCER_SOURCE_RANGES Order: ***, Cadence: fast:2020, kubernetes version: 1.23.8-gke.1900 Once gke_pod_subnet_cidr was added to the LOADBALANCER_SOURCE_RANGES N/S was allowed and I was able call a Viya service via the ingress-nginx hostname

Scenario 2

Input Validation Scenarios Order: ***, Cadence: fast:2020, kubernetes version: 1.23.8-gke.1900

  1. gke_pod_subnet_cidr already in LOADBALANCER_SOURCE_RANGES (user added in ansible-vars.yaml)
  2. provider not in terraform.tfstate as an output
  3. provider is not "gcp" as an output
  4. gke_pod_subnet_cidr is not in terraform.tfstate as an output
jarpat commented 2 years ago

Reopening, this was automatically closed.

jarpat commented 2 years ago

Merging, this was approved.