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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: