You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the default cfdomain object is crated by the helm chart with a hardcodedmetadata.name of default-domain. Strictly speaking the metadata.name of each CF CR should represent its CF guid and should be a vaild uuid.
Acceptance Criteria
GIVEN I have korifi deployed
WHEN I run kubectl get -n cf cfdomains.korifi.cloudfoundry.org
THEN I see a list of domains and every domain name is a valid uuid
Dev Notes
This can be fixed in the helm chart directly by generating a uuid
The text was updated successfully, but these errors were encountered:
Blockers/Dependencies
No response
Background
Currently the default cfdomain object is crated by the helm chart with a hardcoded
metadata.name
ofdefault-domain
. Strictly speaking themetadata.name
of each CF CR should represent its CF guid and should be a vaild uuid.Acceptance Criteria
GIVEN I have korifi deployed
WHEN I run
kubectl get -n cf cfdomains.korifi.cloudfoundry.org
THEN I see a list of domains and every domain name is a valid uuid
Dev Notes
This can be fixed in the helm chart directly by generating a uuid
The text was updated successfully, but these errors were encountered: