mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-21 12:13:55 +09:00
A fixture with unused scheduling keys can render successfully without exercising scheduling. A skip caused by an unrelated failure can also survive after its original lookup restriction is gone. These cases need checks of the rendered result and the failure reason. Assisted-By: LLM Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
26 lines
623 B
YAML
26 lines
623 B
YAML
# A cluster right after install: nothing configured yet.
|
|
_cluster:
|
|
root-host: "example.org"
|
|
bundle-name: "paas-full"
|
|
solver: ""
|
|
issuer-name: ""
|
|
wildcard-secret-name: ""
|
|
wildcard-issue: "false"
|
|
oidc-enabled: "false"
|
|
oidc-insecure-skip-verify: "false"
|
|
keycloak-internal-url: ""
|
|
extra-keycloak-redirect-uri-for-dashboard: ""
|
|
expose-ingress: ""
|
|
expose-services: ""
|
|
cluster-domain: "cluster.local"
|
|
scheduling:
|
|
dedicatedNodesForWindowsVMs: "false"
|
|
globalAppTopologySpreadConstraints: ""
|
|
_namespace:
|
|
etcd: ""
|
|
ingress: ""
|
|
gateway: ""
|
|
monitoring: ""
|
|
seaweedfs: ""
|
|
host: "example.org"
|