From 1ec9936158fd26ac7aec474d5c3ad5941710e22d Mon Sep 17 00:00:00 2001 From: Dario Tranchitella Date: Thu, 12 Aug 2021 10:29:56 +0200 Subject: [PATCH] docs: hostname collision is now managed at Tenant level --- docs/operator/references.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/operator/references.md b/docs/operator/references.md index ec9330ed..80774ebc 100644 --- a/docs/operator/references.md +++ b/docs/operator/references.md @@ -688,8 +688,6 @@ spec: userGroups: ["capsule.clastix.io"] forceTenantPrefix: false protectedNamespaceRegex: "" - allowTenantIngressHostnamesCollision: false - allowIngressHostnameCollision: false ``` Option | Description | Default @@ -697,8 +695,6 @@ Option | Description | Default `.spec.forceTenantPrefix` | Force the tenant name as prefix for namespaces: `-`. | `false` `.spec.userGroups` | Array of Capsule groups to which all tenant owners must belong. | `[capsule.clastix.io]` `.spec.protectedNamespaceRegex` | Disallows creation of namespaces matching the passed regexp. | `null` -`.spec.allowTenantIngressHostnamesCollision` | By default, Capsule allows Ingress hostname collision: set to `false` to enforce this policy. | `true` -`.spec.allowIngressHostnameCollision` | Toggling this, Capsule will not check if a hostname collision is in place, allowing the creation of two or more Tenant resources although sharing the same allowed hostname(s). | `false` Upon installation using Kustomize or Helm, a `default` resource will be created. The reference to this configuration is managed by the CLI flag `--configuration-name`.