kubernetes-apiserver

问题 I'm using AWS' EKS which is Kubernetes v1.10 and I'm using client-go v7.0.0. What I'm trying to do is parse a .yml file with multiple Kubernetes resource definitions in a file and submit those resources to the Kubernetes API. I can successfully parse the files using this code scheme.Codecs.UniversalDeserializer().Decode , and I get back an array of runtime.Object . I know that all the Kubernetes resources conform to the runtime.Object interface, but I can't find a way to submit the generic

问题 I'm using AWS' EKS which is Kubernetes v1.10 and I'm using client-go v7.0.0. What I'm trying to do is parse a .yml file with multiple Kubernetes resource definitions in a file and submit those resources to the Kubernetes API. I can successfully parse the files using this code scheme.Codecs.UniversalDeserializer().Decode , and I get back an array of runtime.Object . I know that all the Kubernetes resources conform to the runtime.Object interface, but I can't find a way to submit the generic

问题 I am trying to create an HA cluster with HAProxy and below 3 master nodes. On the proxy I am following the official documentation High Availability Considerations/haproxy configuration. I am passing the ssl verification to the Server Api option ssl-hello-chk . Having said that I can understand that on my ~/.kube/config file I am using the wrong certificate-authority-data that I picked up from the prime master node e.g.: apiVersion: v1 clusters: - cluster: certificate-authority-data:

问题 I am trying to create an HA cluster with HAProxy and below 3 master nodes. On the proxy I am following the official documentation High Availability Considerations/haproxy configuration. I am passing the ssl verification to the Server Api option ssl-hello-chk . Having said that I can understand that on my ~/.kube/config file I am using the wrong certificate-authority-data that I picked up from the prime master node e.g.: apiVersion: v1 clusters: - cluster: certificate-authority-data:

问题 I am trying to create an HA cluster with HAProxy and below 3 master nodes. On the proxy I am following the official documentation High Availability Considerations/haproxy configuration. I am passing the ssl verification to the Server Api option ssl-hello-chk . Having said that I can understand that on my ~/.kube/config file I am using the wrong certificate-authority-data that I picked up from the prime master node e.g.: apiVersion: v1 clusters: - cluster: certificate-authority-data:

问题 I am trying to create an HA cluster with HAProxy and below 3 master nodes. On the proxy I am following the official documentation High Availability Considerations/haproxy configuration. I am passing the ssl verification to the Server Api option ssl-hello-chk . Having said that I can understand that on my ~/.kube/config file I am using the wrong certificate-authority-data that I picked up from the prime master node e.g.: apiVersion: v1 clusters: - cluster: certificate-authority-data:

问题 I am trying to create an HA cluster with HAProxy and below 3 master nodes. On the proxy I am following the official documentation High Availability Considerations/haproxy configuration. I am passing the ssl verification to the Server Api option ssl-hello-chk . Having said that I can understand that on my ~/.kube/config file I am using the wrong certificate-authority-data that I picked up from the prime master node e.g.: apiVersion: v1 clusters: - cluster: certificate-authority-data:

来源： https://stackoverflow.com/questions/58783939/using-client-go-to-kubectl-apply-against-the-kubernetes-api-directly-with-mult

来源： https://stackoverflow.com/questions/58783939/using-client-go-to-kubectl-apply-against-the-kubernetes-api-directly-with-mult

来源： https://stackoverflow.com/questions/58783939/using-client-go-to-kubectl-apply-against-the-kubernetes-api-directly-with-mult