3 ms·
Your response is a massive mischaractarization of the status of kubernetes. It's FUD. 1. Service discovery. When people say service discovery, they usually me
by TheDong 10y ago
Your response is a massive mischaractarization of the status of kubernetes. It's FUD.
1. Service discovery.
When people say service discovery, they usually mean the ability for a given application to discover other copies of itself and other services & applications within a cluster.
Kubernetes has this down. It has it down better than almost any other system.
The "Service" object in the API can be used for in-cluster service discovery, the service-account tokens can be used as a powerful means of introspection and discovery, etc.
The things you link to are neither relevant. The first is about making api-servers more HA and federation better I think (unrelated to user's services) and the second is a proposal which is implemented, done, and didn't really catch on tbh. It's implemented because, well, it didn't propose any code changes on top of all the features services provide now, just some standard metadata users can opt in to adding if they want that sorta thing.
2. Secret storage
The Secret api object works great. It's done. Adding vualt support is an ongoing feature, but it is in no way a bug, it's just a feature request/enhancement. It's good that kubernetes is evolving, but that doesn't mean that the feature isn't already working.
Configuration scheme
You linked the same issue as before, typo I assume. I have no clue what you're talking about though. ConfigMaps are basically done. Downward API is nice. No clue what you think isn't "fixed".
Please quit it with your FUD. You obviously have no clue wtf you're talking about
- sandGorgon 10y agonot only are you being very liberal with your use of profanity, you are not very accurate. I am not sure what is your personal peeve on this that you had to use words which have no place in a technical conversation. I linked to bugs and proposals that we are discussing on various sigs on slack. even aspects of load balancers and Service abstraction are insufficient and im part of some of the discussions. secrets management being insufficient is the reason why there are suitable number of distributions with their own flavors of these. Your terming of Service Discovery proposal as a HA is laughable. HA in apiservers has been production ready for quite some time and well integrated in kops and kargo. Etcd recovery is still a hassle. You are mistaking documentation being marked as available with it being actually usable in lifecycle. Are you aware that full tls in kubernetes is hard because some values are hardcoded? this causes etcd breakage in lifecycles. kubernetes is not complete - im very bullish on its future, but I would recommend you stick to technical refutal more than personal ire.
- TheDong 10y agoIndeed, I'm wrong. The second link (https://github.com/kubernetes/community/blob/a1d8453e184dfd8b1c5656e1e42528125d2eb906/contributors/design-proposals/aggregated-api-servers.md https://github.com/kubernetes/community/blob/a1d8453e184dfd8...) I referred to is something like "Third party resources" (TPRs) which again has nothing to do with services. The first proposal you link is not anything that needs implementation. Please, respond to my technical answers. You're not. Listen to your own words.