Canonical introduces high-availability Micro-Kubernetes

Re:Canonical introduces high-availability Micro-Kubernetes by smarterclayton on Thursday October 15, 2020 @05:12PM (#24794029)

As the person who has worked on making sure telemetry is useful and valuable for users and customers (helping drive insight into quality of kube and close the loop on fixing persistent issues), can you provide some more details about how we’ve let you down? We tried to be as responsible as possible but obviously we’ve failed along the way - what can be done to improve it?

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by krimeo on Thursday October 15, 2020 @05:16PM (#24794098)

Make the telemetry opt-in to begin with.

The comment I am replying to is complaining about Ubuntu calling home, IBM OpenShift is the same story.

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by MichaelMoser123 on Friday October 16, 2020 @01:03AM (#24797659)

that's what they call 'opinionated default configuration'; then they tie in subscription management with telemetry so that opting out of it isn't an option to begin with; https://docs.openshift.com/container-platform/4.1/telemetry/... Several further tie ins and the system as a whole becomes barely usable. But then integration is the whole point of openshift, isn't it?

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by smarterclayton on Friday October 16, 2020 @09:44AM (#24800749)

Wow, I’d didn’t realize the 4.1 docs didn’t get updated - newer doc versions are correct in that disconnected subscriptions just manually entered via OCM. 4.1 didn’t include the support for disconnected clusters and at the time the docs were correct. Newer versions are more clear.

https://docs.openshift.com/container-platform/4.5/support/re...

I will follow up on opt-out being the default for the evaluation version of OpenShift. It is already opt-in for OKD.

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by oso2k on Thursday October 15, 2020 @06:32PM (#24795007)

Not to be snarky, but that's easy. Just disconnect your cluster from the internet. We have hundreds of customers that are running disconnected clusters.

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by krimeo on Thursday October 15, 2020 @06:53PM (#24795250)

And that applies to Ubuntu just as well. All I'm saying IBM is no better than Canonical in this regard.

Not complaining - If you want me to complain about IBM cluster technology that would be a whole different story.

And no I'm not gonna ask about disconnected clusters :).

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by oso2k on Thursday October 15, 2020 @07:58PM (#24795844)

Haha. I still work for Red Hat, and Consulting at that. My pay is determined by how many billable hours I put in and my customer reviews. Not directly by how much you buy.

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by krimeo on Thursday October 15, 2020 @08:33PM (#24796081)

I thought there is no Red Hat anymore.

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by mroche on Friday October 16, 2020 @08:40AM (#24800219)

Red Hat is a subsidiary of IBM, not acquired and absorbed. It is very much its own thing within the company as a whole.

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by krimeo on Friday October 16, 2020 @09:47AM (#24800773)

I really thought it was a merger. Is Red Hat still a seperate legal entity?

[ Parent | on HN ]

Re:Canonical introduces high-availability Micro-Kubernetes by smarterclayton on Friday October 16, 2020 @03:56PM (#24804420)

Yes, separate legal entity, combined financial entity (although I know little about the financial details).

[ Parent | on HN ]