Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ingress object should be created conditionally #226

Closed
Tracked by #223
ppawlowski opened this issue Nov 20, 2023 · 3 comments
Closed
Tracked by #223

Ingress object should be created conditionally #226

ppawlowski opened this issue Nov 20, 2023 · 3 comments
Assignees
Labels
needs-triage Needs looking at to decide what to do task A piece of work that isn't necessarily tied to a specific Epic or Story.

Comments

@ppawlowski
Copy link
Contributor

ppawlowski commented Nov 20, 2023

With default chart values, the creation of an ingress object fails with the error:

Error: INSTALLATION FAILED: 1 error occurred:
	* Ingress.extensions "flowforge-ingress" is invalid: spec.rules[0].host: Invalid value: "forge.": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

We should either provide some proper default values or create an ingress object only if forge.domain or forge.entryPoint have values.

@ppawlowski ppawlowski changed the title Add default domain name Ingress object should be created conditionally Nov 20, 2023
@ppawlowski ppawlowski added the needs-triage Needs looking at to decide what to do label Nov 20, 2023
@ppawlowski ppawlowski self-assigned this Nov 20, 2023
@ppawlowski ppawlowski added the task A piece of work that isn't necessarily tied to a specific Epic or Story. label Nov 20, 2023
@hardillb
Copy link
Contributor

This is deliberate, the system won't work without a valid domain and every install will have it's own bespoke domain, so failing if it's not set is correct (the values-schema.json should have it marked as required so it should fail before trying to render the templates, if it doesn't that is the fix here)

@hardillb
Copy link
Contributor

Yep, domain is marked as required

"required": [
"domain",

@ppawlowski
Copy link
Contributor Author

In YAML if a key doesn't have a value it will be set to an empty string. I have created a PR which introduced validation of this field.

the system won't work without a valid domain (...) , so failing if it's not set is correct

I can't really argue with that. I will close this issue once a related PR is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Needs looking at to decide what to do task A piece of work that isn't necessarily tied to a specific Epic or Story.
Projects
Archived in project
Development

No branches or pull requests

2 participants