Generate deployment manifest ERROR

[dannycrief]

Generate deployment manifest ERROR

[dannycrief]

Here's my ansiblevars.yaml file:

## Cluster
NAMESPACE: sas-viya

## MISC
DEPLOY: true # Set to false to stop at generating the manifest
LOADBALANCER_SOURCE_RANGES: ["ip-address"]

## Storage
V4_CFG_MANAGE_STORAGE: true
# JUMP_SVR_RWX_FILESTORE_PATH: /export

## SAS API Access
V4_CFG_SAS_API_KEY: 'myKey'
V4_CFG_SAS_API_SECRET: 'mySecret'
V4_CFG_ORDER_NUMBER: myOrderNumber

V4_CFG_DEPLOYMENT_ASSETS: ViyaArchive.tgz
V4_CFG_CADENCE_VERSION: 2023.04
V4_CFG_CADENCE_NAME: stable

## CR Access
#V4_CFG_CR_USER: viyacregistry
#V4_CFG_CR_PASSWORD: <pass>
#V4_CFG_CR_URL: viyacregistry.azurecr.io

## Ingress
V4_CFG_INGRESS_TYPE: ingress
V4_CFG_INGRESS_FQDN: my-hostname.eastus.cloudapp.azure.com
V4_CFG_TLS_MODE: "full-stack" # [full-stack|front-door|ingress-only|disabled]

## Postgres
V4_CFG_POSTGRES_SERVERS:
  default:
    internal: true   # false

## CAS
# V4_CFG_CAS_WORKER_COUNT: 2

## LDAP
V4_CFG_EMBEDDED_LDAP_ENABLE: true

## Consul UI
V4_CFG_CONSUL_ENABLE_LOADBALANCER: false

## SAS/CONNECT
V4_CFG_CONNECT_ENABLE_LOADBALANCER: false

## Monitoring and Logging
## uncomment and update the below values when deploying the viya4-monitoring-kubernetes stack
#V4M_BASE_DOMAIN: my-hostname.eastus.cloudapp.azure.com
#V4M_STORAGECLASS: sas
#V4M_GRAFANA_PASSWORD: Password123
#V4M_KIBANA_PASSWORD: Password123
#V4M_LOGCOLLECTOR_PASSWORD: Password123

#Opendistro
V4_CFG_ELASTICSEARCH_ENABLE: true

[dhoucgitter]

Hi @dannycrief, could you try viya4-deployment 6.6.0 again but allow it to build with the default of kustomize 4.5.7? kustomize 3.7.0 is not supported with 2023.04.

See the information below regarding minimum kustomize version for SAS Viya platform 2023.02 or later in the viya4-deployment:6.2.0 release notes.

Kustomize version:
With SAS Viya platform release cadence version 2023.02, kustomize 4.5.7 is the new minimum requirement for generating Kubernetes manifest files. The default kustomize binary version that is included in the Dockerfile will now be 4.5.7. We do still provide end users the ability to build their viya4-deployment images with a specific kustomize version if the deployment cadence requires it (<=2023.01).

[jarpat]

Marking as stale/inactive. If there are further questions please open a new GitHub issue.