Alan
05/29/2024, 11:25 PMingress:
# -- enable ingress record generation for server
enabled: true
# -- port for the ingress' main path
#servicePort: 4200
## This is supported in Kubernetes 1.18+ and required if you have more than one IngressClass marked as the default for your cluster .
## ref: <https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/>
# -- IngressClass that will be used to implement the Ingress (Kubernetes 1.18+)
className: ""
host:
# -- default host for the ingress record
hostname: ${HOST_NAME}
# -- default path for the ingress record
path: /
# -- ingress path type
pathType: Prefix
Alan
05/29/2024, 11:25 PMJamie Zieziula
05/29/2024, 11:29 PMAlan
05/29/2024, 11:30 PMAlan
05/29/2024, 11:30 PMAlan
05/29/2024, 11:30 PMmodule.prefect.helm_release.prefect_server: Modifying... [id=prefect-server]
╷
│ Error: values don't meet the specifications of the schema(s) in the following chart(s):
│ prefect-server:
│ - ingress: Additional property servicePort is not allowed
│
│
│ with module.prefect.helm_release.prefect_server,
│ on ../../tfmodules/prefect/main.tf line 1, in resource "helm_release" "prefect_server":
│ 1: resource "helm_release" "prefect_server" {
│
╵
Alan
05/29/2024, 11:31 PMJamie Zieziula
05/29/2024, 11:31 PMJamie Zieziula
05/29/2024, 11:32 PMAlan
05/29/2024, 11:32 PMAlan
05/29/2024, 11:32 PMingress:
# -- enable ingress record generation for server
enabled: true
# -- port for the ingress' main path
servicePort: 4200
## This is supported in Kubernetes 1.18+ and required if you have more than one IngressClass marked as the default for your cluster .
## ref: <https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/>
# -- IngressClass that will be used to implement the Ingress (Kubernetes 1.18+)
className: ""
host:
# -- default host for the ingress record
hostname: ${HOST_NAME}
# -- default path for the ingress record
path: /
# -- ingress path type
pathType: Prefix
Jamie Zieziula
05/29/2024, 11:32 PMAlan
05/29/2024, 11:33 PMJamie Zieziula
05/29/2024, 11:34 PMJamie Zieziula
05/29/2024, 11:34 PMAlan
05/29/2024, 11:35 PMAlan
05/29/2024, 11:35 PMJamie Zieziula
05/29/2024, 11:36 PMAlan
05/29/2024, 11:37 PMAlan
05/29/2024, 11:38 PMAlan
05/29/2024, 11:39 PMspec:
rules:
- host: prefect.ili-research.*****.com
http:
paths:
- backend:
service:
name: prefect-server
port:
name: server-svc-port
path: /
pathType: Prefix
status:
loadBalancer: {}
Alan
05/29/2024, 11:39 PMJamie Zieziula
05/29/2024, 11:40 PMJamie Zieziula
05/29/2024, 11:41 PMAlan
05/29/2024, 11:41 PMAlan
05/29/2024, 11:50 PMhttp:
paths:
- backend:
service:
name: prefect-server
port:
name: server-svc-port
path: /
pathType: Prefix
status:
loadBalancer: {}
Alan
05/30/2024, 6:47 PMAlan
05/30/2024, 6:49 PMJamie Zieziula
05/30/2024, 8:23 PMserver-svc-port
Jamie Zieziula
05/30/2024, 8:24 PMJamie Zieziula
05/30/2024, 8:25 PMAlan
05/30/2024, 8:28 PMJamie Zieziula
05/30/2024, 8:32 PMJamie Zieziula
05/30/2024, 8:32 PMAlan
05/30/2024, 8:32 PMJamie Zieziula
05/30/2024, 8:32 PMpostgres.enabled=false
to workJamie Zieziula
05/30/2024, 8:32 PMAlan
05/30/2024, 8:34 PMpostgresql:
enabled: false
auth:
# -- determines whether an admin user is created within postgres
enablePostgresUser: false
# -- name for a custom database
database: server
# -- name for a custom user
username: prefect
## This is the password for `username` and will be set within the secret `{fullnameOverride}-postgresql` at the key `password`.
## This argument is only relevant when using the Postgres database included in the chart.
## For an external postgres connection, you must create and use `existingSecret` instead.
# -- password for the custom user. Ignored if `auth.existingSecret` with key `password` is provided
password: prefect-rocks
## This secret must contain two key-value pairs where the first key is `connection-string` and the value is the
## connection string containing your password (e.g. postgresql+asyncpg://{username}:{password}@{hostname}/{database}).
## The second key-value pair has the key `password` and the value is the {password} used in the connection string
# -- Name of existing secret to use for PostgreSQL credentials.
existingSecret: ${EXISTING_SECRET}
# -- PostgreSQL container port
containerPorts:
postgresql: 5432
# externalHostname defines the address to contact an externally
# managed postgres database instance at. This is not required if
# `internalPostgres` is `true`
externalHostname: ""
# -- enable use of bitnami/postgresql subchart
useSubChart: true
## postgresql configuration below here is only used if using the subchart
## Initdb configuration
## ref: <https://github.com/bitnami/containers/tree/main/bitnami/postgresql#specifying-initdb-arguments>
primary:
initdb:
# -- specify the PostgreSQL username to execute the initdb scripts
user: postgres
## persistence enables a PVC that stores the database between deployments. If making changes to the database deployment, this
## PVC will need to be deleted for database changes to take effect. This is especially notable when the authentication password
## changes on redeploys. This is disabled by default because we do not recommend using the subchart deployment for production deployments.
persistence:
# -- enable PostgreSQL Primary data persistence using PVC
enabled: false
# -- PVC Storage Request for PostgreSQL volume
size: 8Gi
Alan
05/30/2024, 8:36 PMJamie Zieziula
05/30/2024, 8:36 PMJamie Zieziula
05/30/2024, 8:37 PMAlan
05/30/2024, 8:37 PMJamie Zieziula
05/30/2024, 8:38 PMhelm install prefect-server prefect/prefect-server --set postgresql.enabled=false --set postgresql.useSubChart=false
this works -- no postgresql pod is deployed. This is definitely confusing, i'll open an issue and we will figure out a better way. thanks for raising!Jamie Zieziula
05/30/2024, 8:41 PMAlan
05/30/2024, 8:44 PMJamie Zieziula
05/30/2024, 9:05 PMAlan
05/30/2024, 10:49 PMAlan
05/30/2024, 10:49 PMJamie Zieziula
05/31/2024, 12:20 AMMitch Nielsen
06/04/2024, 7:52 PM