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

Improve ingress patching #365

Open
jfaltermeier opened this issue Oct 28, 2024 · 0 comments
Open

Improve ingress patching #365

jfaltermeier opened this issue Oct 28, 2024 · 0 comments
Labels
enhancement New feature or request prio-medium

Comments

@jfaltermeier
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Currently the instances-ingress gets created/upgraded when running helm install/upgrade, but also gets patched by the operator if there are new appdefinitions or sessions.

This currently leads to quite some problems:
On helm upgrade we set the hosts to the same values we had before the upgrade, this will result in changed values not being applied (e.g. allWildcardInstances)
When upgrading a separate appDefinition helm chart added appDefinitions will not be updated in the ingress, hence they wont work.

This makes the upgrade process harder or even impossible. We should investigate on how we can improve this.

Describe the solution you'd like

One solution might be to handle the ingress completely by the operator.

Describe alternatives you've considered

Cluster provider

No response

Additional information

No response

@jfaltermeier jfaltermeier added enhancement New feature or request prio-medium labels Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request prio-medium
Projects
None yet
Development

No branches or pull requests

1 participant