Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Kubernetes Kustomize KEP Kerfuffle

gravitational.com

Post reply on HN
Print view View original

1–10 of 51 posts

Re: The Kubernetes Kustomize KEP Kerfuffle

#3

Post by warp_factor »

If I understood correctly the article, the claim is that Google can introduce features more easily into Kubernetes just because they are Google?

And I would answer: Why are you surprised? I worked a bit with Kubernetes and it's mostly dominated by Google or by a top-level set of contributors that are all friends and think alike. This is also probably the reason why Google released Kubernetes as open-source. It allows them to indirectly control this project.

Re: The Kubernetes Kustomize KEP Kerfuffle

#4

Post by jacques_chester »

I've been on both sides of this sort of divide, as both insider and outsider.

It's easy to see it as politics. I do, pretty much all the time, but that's because I have a background in politics. I'm primed to assume the worst.

I think the explanation is simpler. If you are a Googler, you mostly talk to Googlers, you mostly come to quick consensus that way, and it all makes sense to you and the Googlers you had casual whiteboarding sessions with. So you just go ahead with the to-you-obviously-best decision and get surprised when non-Googlers are mad at being presented with a fait accompli.

There is no ill-will and no conspiracy required. Some of the personnel allocations are driven by corporate strategy, but folks engineering on the line are all reasonable human beings. It's just simple personal dynamics. You talk mostly to the people closest to you unless sustained effort is made to keep stuff in the open.

Re: The Kubernetes Kustomize KEP Kerfuffle

#6

Post by justicezyx »

jacques_chester wrote: post #4

I've been on both sides of this sort of divide, as both insider and outsider. It's easy to see it as politics. I do, pretty much all the time, but that's because I have a background in politics. I'm primed to assume the worst. I think the explanation is simpler. If you are a Googler, you mostly talk to Googlers, you mostly come to quick consensus that way, and it all makes sense to you and the Googlers you had casual…

You missed the key part.

This is why it was open sourced, as a balance between control leverage and adoption.

Re: The Kubernetes Kustomize KEP Kerfuffle

#7

Post by the_duke »

aberoham wrote: post #2

Author here. This was an extremely hard topic to write about. Happy to answer questions but really hoping those from sig-cli and sig-architecture chime in here. Is this Kerfuffle the root of the sudden resurgence of KEPs?

Your writing style is hilarious, bordering on poetic.

It is somewhat hard to follow the actual information though, and non-native speakers will probably struggle quite a bit.

Re: The Kubernetes Kustomize KEP Kerfuffle

#8

Post by justinsb »

aberoham wrote: post #2

Author here. This was an extremely hard topic to write about. Happy to answer questions but really hoping those from sig-cli and sig-architecture chime in here. Is this Kerfuffle the root of the sudden resurgence of KEPs?

Not the cause. The release team asked for KEPs for all new features in the next release and the deadline was today.

Re: The Kubernetes Kustomize KEP Kerfuffle

#9

Post by aberoham »

justinsb wrote: post #8
aberoham wrote: post #2

Author here. This was an extremely hard topic to write about. Happy to answer questions but really hoping those from sig-cli and sig-architecture chime in here. Is this Kerfuffle the root of the sudden resurgence of KEPs?

Not the cause. The release team asked for KEPs for all new features in the next release and the deadline was today.

Indeed, someone in a separate channel explained that new sig-pm staffing is at the root of the resurgence of KEPs. Thanks justinsb, no relation to GCP's Justin Santa Barbara?

Re: The Kubernetes Kustomize KEP Kerfuffle

#10

Post by the_duke »

aberoham wrote: post #2

Author here. This was an extremely hard topic to write about. Happy to answer questions but really hoping those from sig-cli and sig-architecture chime in here. Is this Kerfuffle the root of the sudden resurgence of KEPs?

Question: one of the main advantages of helm (for me) is the pruning of dead resources.

As in, my chart contains 3 services , I remove one of them including some related things like secrets, configmaps, etc and deploy, helm will clean up everything redundant.

Does Kustomize handle this problem?

Post reply on HN