3 ms·
not 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
by sandGorgon 10y ago
not 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.