mirror of
https://github.com/dredx/prole.git
synced 2026-09-23 12:03:59 +00:00
a069989315
Itemized changes:
1. knoe-auth: New cluster-internal KDC and SSO gateway service
- Created etc/init_knoe_auth.sh based on init_kdc.sh with knoe-auth naming
- Namespace defaults to SERVICE_NAMESPACE (knoe-system)
- ConfigMap: knoe-auth-kdc-config, Secret: knoe-auth-secrets
- Legacy cleanup removes old auth/dog/authority deployments
2. Orchestration: knoe-auth initializes before CloudNativePG
- Updated prole.sh to insert init_knoe_auth.sh as step 2 (before CNPG)
- Renumbered all subsequent initialization steps
3. Kong routing: Updated init_kong.sh to route to knoe-auth in SERVICE_NAMESPACE
4. Comment/reference updates for knoe-auth
- Updated init_common_services.sh, init_service_layer.sh, init_kerberos.sh
5. prole-db renamed to knoe-db across the entire codebase
- Renamed prole-db/ directory to knoe-db/
- Renamed all prole-db Kubernetes manifests (deploy/opentofu, k8s/)
- Renamed scripts: docker-root-knoe-db.sh, docker-run-knoe-db.sh, test-cnpg-knoe-db.sh
- Renamed etc/init_prole-db-reset.sh to etc/init_knoe-db-reset.sh
- Renamed etc/prole-db-passwwd.sh to etc/knoe-db-passwwd.sh
- Renamed mock_val counterparts accordingly
- Renamed tests/etc/test_init_prole-db-reset.sh to test_init_knoe-db-reset.sh
- Renamed docs/prole-db-documentation-mcp-architecture.md to knoe-db variant
- Renamed modes/k3d/prole-db/ to modes/k3d/knoe-db/
- Renamed prole-db.iml to knoe-db.iml
6. Configuration updates
- Updated conf/dev, conf/prod, conf/test, conf/service prole.cfg files
- Updated conf/port-mapping.cfg
- Updated etc/prole_cfg.sh and mock_val/prole_cfg.sh
- Updated service/prole.cfg
7. Kubernetes manifests and deploy configuration
- Updated deploy/opentofu/k3s ArgoCD application YAMLs
- Updated kong-configmap.yaml and kustomization.yaml
- Updated k3s/kong-config.yml and prole-resources.yaml
- Updated prole-mssql-db deployment YAMLs
- Updated supabase helm render and deploy scripts
8. Infrastructure and GCP Terraform
- Updated deploy/gcp/terraform: folders, groups, IAM, service-projects
9. Python/installer code updates
- Updated knoe/core: actions, build_context, controller, env, milestones
- Updated knoe/milestone.py
- Updated knoe/ui/screens: cfg, database, database_options, deploy, docker,
navigation, security, services, validate
- Updated knoe.spec, status.py
10. Shell script updates
- Updated etc/: build_db, init_cloudnative_pg, init_cnpg_backup,
init_db_manager, init_forgejo, init_gitlab, init_monitoring, init_openbao,
init_port_forwards, init_postgrest, init_supabase_ports, status
- Updated mock_val/ counterparts for all above scripts
- Updated prole-net/init-prole-dns.sh
- Updated bin/prole-kpf.sh, gitea/deploy.sh, supabase/deploy.sh
11. Test updates
- Updated tests/etc/: test_init_cloudnative_pg*, test_init_cnpg_backup*,
test_init_kdc*, test_init_kerberos*, test_init_kong*, test_prole_cfg*
- Updated tests/installer/: test_actions_helpers, test_cfg_save_kubecontext,
test_controller, test_core_classes, test_milestones, test_milestones_extended,
test_namespace_propagation
- Updated tests/: test_database_options, test_navigation,
test_render_supabase_hostname, test_docker_build_fix,
test_all_prole_home_fixes, silent_install_test, final_test
12. Documentation updates
- Updated docs/: DOCKER-BUILD-FIX, PROLE-CFG-SECRETS, PROLE-HOME-DIRECTORY,
build-system, patent
- Updated scan/network_description.txt
- Updated pom.xml
13. Miscellaneous script updates
- Updated root-level: _adopt_replica_pvcs, _fix_replica_merlin, _import_pi,
_patch_cluster, _prebind_pvcs, _rebind_d002, _rebind_d002b, test_resolve
- Updated scripts/generate_spec.py
Co-authored-by: Junie <junie@jetbrains.com>
136 lines
5.9 KiB
Plaintext
136 lines
5.9 KiB
Plaintext
# PostgreSQL Client Authentication Configuration File
|
|
# ===================================================
|
|
#
|
|
# Refer to the "Client Authentication" section in the PostgreSQL
|
|
# documentation for a complete description of this file. A short
|
|
# synopsis follows.
|
|
#
|
|
# ----------------------
|
|
# Authentication Records
|
|
# ----------------------
|
|
#
|
|
# This file controls: which hosts are allowed to connect, how clients
|
|
# are authenticated, which PostgreSQL user names they can use, which
|
|
# databases they can access. Records take one of these forms:
|
|
#
|
|
# local DATABASE USER METHOD [OPTIONS]
|
|
# host DATABASE USER ADDRESS METHOD [OPTIONS]
|
|
# hostssl DATABASE USER ADDRESS METHOD [OPTIONS]
|
|
# hostnossl DATABASE USER ADDRESS METHOD [OPTIONS]
|
|
# hostgssenc DATABASE USER ADDRESS METHOD [OPTIONS]
|
|
# hostnogssenc DATABASE USER ADDRESS METHOD [OPTIONS]
|
|
#
|
|
# (The uppercase items must be replaced by actual values.)
|
|
#
|
|
# The first field is the connection type:
|
|
# - "local" is a Unix-domain socket
|
|
# - "host" is a TCP/IP socket (encrypted or not)
|
|
# - "hostssl" is a TCP/IP socket that is SSL-encrypted
|
|
# - "hostnossl" is a TCP/IP socket that is not SSL-encrypted
|
|
# - "hostgssenc" is a TCP/IP socket that is GSSAPI-encrypted
|
|
# - "hostnogssenc" is a TCP/IP socket that is not GSSAPI-encrypted
|
|
#
|
|
# DATABASE can be "all", "sameuser", "samerole", "replication", a
|
|
# database name, a regular expression (if it starts with a slash (/))
|
|
# or a comma-separated list thereof. The "all" keyword does not match
|
|
# "replication". Access to replication must be enabled in a separate
|
|
# record (see example below).
|
|
#
|
|
# USER can be "all", a user name, a group name prefixed with "+", a
|
|
# regular expression (if it starts with a slash (/)) or a comma-separated
|
|
# list thereof. In both the DATABASE and USER fields you can also write
|
|
# a file name prefixed with "@" to include names from a separate file.
|
|
#
|
|
# ADDRESS specifies the set of hosts the record matches. It can be a
|
|
# host name, or it is made up of an IP address and a CIDR mask that is
|
|
# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
|
|
# specifies the number of significant bits in the mask. A host name
|
|
# that starts with a dot (.) matches a suffix of the actual host name.
|
|
# Alternatively, you can write an IP address and netmask in separate
|
|
# columns to specify the set of hosts. Instead of a CIDR-address, you
|
|
# can write "samehost" to match any of the server's own IP addresses,
|
|
# or "samenet" to match any address in any subnet that the server is
|
|
# directly connected to.
|
|
#
|
|
# METHOD can be "trust", "reject", "md5", "password", "scram-sha-256",
|
|
# "gss", "sspi", "ident", "peer", "pam", "ldap", "radius" or "cert".
|
|
# Note that "password" sends passwords in clear text; "md5" or
|
|
# "scram-sha-256" are preferred since they send encrypted passwords.
|
|
#
|
|
# OPTIONS are a set of options for the authentication in the format
|
|
# NAME=VALUE. The available options depend on the different
|
|
# authentication methods -- refer to the "Client Authentication"
|
|
# section in the documentation for a list of which options are
|
|
# available for which authentication methods.
|
|
#
|
|
# Database and user names containing spaces, commas, quotes and other
|
|
# special characters must be quoted. Quoting one of the keywords
|
|
# "all", "sameuser", "samerole" or "replication" makes the name lose
|
|
# its special character, and just match a database or username with
|
|
# that name.
|
|
#
|
|
# ---------------
|
|
# Include Records
|
|
# ---------------
|
|
#
|
|
# This file allows the inclusion of external files or directories holding
|
|
# more records, using the following keywords:
|
|
#
|
|
# include FILE
|
|
# include_if_exists FILE
|
|
# include_dir DIRECTORY
|
|
#
|
|
# FILE is the file name to include, and DIR is the directory name containing
|
|
# the file(s) to include. Any file in a directory will be loaded if suffixed
|
|
# with ".conf". The files of a directory are ordered by name.
|
|
# include_if_exists ignores missing files. FILE and DIRECTORY can be
|
|
# specified as a relative or an absolute path, and can be double-quoted if
|
|
# they contain spaces.
|
|
#
|
|
# -------------
|
|
# Miscellaneous
|
|
# -------------
|
|
#
|
|
# This file is read on server startup and when the server receives a
|
|
# SIGHUP signal. If you edit the file on a running system, you have to
|
|
# SIGHUP the server for the changes to take effect, run "pg_ctl reload",
|
|
# or execute "SELECT pg_reload_conf()".
|
|
#
|
|
# ----------------------------------
|
|
# Put your actual configuration here
|
|
# ----------------------------------
|
|
#
|
|
# If you want to allow non-local connections, you need to add more
|
|
# "host" records. In that case you will also need to make PostgreSQL
|
|
# listen on a non-local interface via the listen_addresses
|
|
# configuration parameter, or via the -i or -h command line switches.
|
|
|
|
|
|
|
|
|
|
# DO NOT DISABLE!
|
|
# If you change this first entry you will need to make sure that the
|
|
# database superuser can access the database using some other method.
|
|
# Noninteractive access to all databases is required during automatic
|
|
# maintenance (custom daily cronjobs, replication, and similar tasks).
|
|
#
|
|
# Database administrative login by Unix domain socket
|
|
local all postgres peer
|
|
|
|
# TYPE DATABASE USER ADDRESS METHOD
|
|
|
|
# "local" is for Unix domain socket connections only
|
|
local all all peer
|
|
# IPv4 local connections:
|
|
host all all 127.0.0.1/32 scram-sha-256
|
|
# IPv6 local connections:
|
|
host all all ::1/128 scram-sha-256
|
|
# Allow replication connections from localhost, by a user with the
|
|
# replication privilege.
|
|
local replication all peer
|
|
host replication all 127.0.0.1/32 scram-sha-256
|
|
host replication all ::1/128 scram-sha-256
|
|
|
|
# Kerberos authentication
|
|
# host all all all gss include_realm=1 krb_realm=EXAMPLE.COM
|