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
Hi,
I have a binding issue that I am not sure if the result is expected or it is an issue.
I have two charts, chart1 created an exchange, and chart2 created a binding with the exchange as the source. Both charts were installed in the same Kubernetes namespace. After the chart1 was uninstalled. When I described the binding from by kubectl, its status is still True and the reason is SuccessfulCreateOrUpdate. However, the binding did not exist when I checked it from rabbitmq port and the binding is not able to be recovered after re-install chart1. My question is should the operator get the binding recovered after the exchange re-created?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I have a binding issue that I am not sure if the result is expected or it is an issue.
I have two charts, chart1 created an exchange, and chart2 created a binding with the exchange as the source. Both charts were installed in the same Kubernetes namespace. After the chart1 was uninstalled. When I described the binding from by kubectl, its status is still True and the reason is SuccessfulCreateOrUpdate. However, the binding did not exist when I checked it from rabbitmq port and the binding is not able to be recovered after re-install chart1. My question is should the operator get the binding recovered after the exchange re-created?
Beta Was this translation helpful? Give feedback.
All reactions