Aaron Layfield
Aaron Layfield
@pburgisser I'll jump on this tomorrow morning.
I'm hesitant with this change as the impact is pretty big to people using it. Also, there is justifiable reasons for both. This sounds more like I should investigate why...
@sindrip Sorry, I wasn't notified via email about this :( I'll check and test over the coming next couple of days.
@sindrip I do, I will be checking shortly. I can't believe this has been open so long, sorry.
@stefanandres I will take a look at this, this week.
@aleclerc-sonrai Do you have your separated values you can provide? This looks to me like the cluster names are the same in your values, and as a result the Redis...
@jimethn Correct. It's because of the selector & headless service. I'll review your PR in a bit.
@akevdmeer I wonder how to best manage this... I think to prevent breaking changes, I'll add a debug boolean into the values you can enable to manage this. I'm not...
@amfleurke No arguments here, will need to update the Helm chart to check k8s versioning and applying labels for backwards combatibility.
@andyfeller I'll add this to the CD portion of the integration, should be relatively easy but is a very good point!