From 694b519af88e86399fadf3a4f308f7f43a44ed10 Mon Sep 17 00:00:00 2001 From: Dario Tranchitella Date: Sat, 31 Jul 2021 23:18:22 +0200 Subject: [PATCH] build(helm): hostname collision is now managed at Tenant level --- charts/capsule/crds/capsuleconfiguration-crd.yaml | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/charts/capsule/crds/capsuleconfiguration-crd.yaml b/charts/capsule/crds/capsuleconfiguration-crd.yaml index 84269b78..a36d8952 100644 --- a/charts/capsule/crds/capsuleconfiguration-crd.yaml +++ b/charts/capsule/crds/capsuleconfiguration-crd.yaml @@ -30,14 +30,8 @@ spec: spec: description: CapsuleConfigurationSpec defines the Capsule configuration properties: - allowIngressHostnameCollision: - default: true - description: Allow the collision of Ingress resource hostnames across all the Tenants. - type: boolean - allowTenantIngressHostnamesCollision: - description: "When defining the exact match for allowed Ingress hostnames at Tenant level, a collision is not allowed. 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). \n The JSON path of the resource is: /spec/ingressHostnames/allowed" - type: boolean forceTenantPrefix: + default: false description: Enforces the Tenant owner, during Namespace creation, to name it using the selected Tenant name as prefix, separated by a dash. This is useful to avoid Namespace name collision in a public CaaS environment. type: boolean protectedNamespaceRegex: