chrisarnott86

I have been able to get tox to complete successfully by adding a couple of ignores to `tox.ini`. The warnings I added were for files I hadn't touched. I found...

I've reverted tox.ini back to the original in my local copy, and I'm getting failed checks again. Here's the output: ``` examples/interconnects.py:127:7: W504 line break after binary operator examples/scmb/ov_to_sm.py:152:17: W504...

Given that the travis checks are failing in relation to files unrelated to my pull request, it shouldn't hinder checking of my commits. Does anyone else find that the tox...

Definitely a new unique website. The production "The Chosen" is no longer associated with Angel Studios, so the new site "watch.thechosen.tv" is entirely new and separate from any angel studios...

@thebsdbox, indeed metallb is installed in the cluster so was running with kube-vip, I obviously didn't install kube-vip-cloud-controller as that provides effectively the same functionality as metallb. Is running metallb...

Thanks @thebsdbox. I hadn't realised that kube-vip would attempt to expose an address without kube-vip-cloud-controller being installed? Here are a couple of different people installing kube-vip and metallb together https://gist.github.com/rosswf/e5c4c85efb54a9f8d6e19a21cf09aa63...

Thanks, I specifically do need the egress function, that's the new feature I'm trying to introduce to the cluster using kube-vip. If service watching is enabled (as I have) then...

@Cellebyte, thanks very much for your input. How do I disable status update for kube-vip? I can't find that in the documentation.

Thanks @Cellebyte, I'll do some testing with that flag set and see how it goes.

@thebsdbox @Cellebyte. I've been able to add the parameter now in our production cluster. Initial signs are that the connectivity errors I saw previously are not occurring, having said that...