Issue 1:
I have the following use case:

I need to route from non-kubernetes servers to Kubernetes ClusterIPs. I already have the routes set up properly to FORWARD to pod IP addresses, and this works perfectly (I can access pod IP addresses from outside the cluster). But nothing I've tried seems to get the service routing to work properly.

How can I set this up properly? Is this something that potentially should be included in Kubernetes?

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.0", GitCommit:"ec7364b6e3b155e78086018aa644057edbe196e5", GitTreeState:"clean"}

Server Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.0", GitCommit:"ec7364b6e3b155e78086018aa644057edbe196e5", GitTreeState:"clean"}

Environment:

Cloud provider or hardware configuration: vmware

OS (e.g. from /etc/os-release): CentOS Linux release 7.2.1511 (Core)

Kernel (e.g. uname -a): Linux localhost.localdomain 3.10.0-327.28.3.el7.x86_64 #1 SMP Thu Aug 18 19:05:49 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Install tools:manually

Others:

What happened:

when run command kubectl create -f kubernetes-dashboard.yaml, error message from

/var/log/messages

Error while initializing connection to Kubernetes apiserver. This most likely means that the cluster is misconfigured (e.g., it has invalid apiserver certificates or service accounts configuration) or the --apiserver-host param points to a server that does not exist. Reason: the server has asked for the client to provide credentials

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else do we need to know:

I edit kubernetes-dashboard.yaml and added something

kind: Deployment

apiVersion: extensions/v1beta1

metadata:

labels:

app: kubernetes-dashboard

name: kubernetes-dashboard

namespace: kube-system

spec:

replicas: 1

selector:

matchLabels:

app: kubernetes-dashboard

template:

metadata:

labels:

app: kubernetes-dashboard

spec:

containers:

- name: kubernetes-dashboard

image: 192.168.100.20:5000/kubernetes-dashboard-amd64

imagePullPolicy: Always

ports:

- containerPort: 9090

protocol: TCP

args:

# Uncomment the following line to manually specify Kubernetes API server Host

# If not specified, Dashboard will attempt to auto discover the API server and connect

# to it. Uncomment only if the default does not work.

- --apiserver-host=https://192.168.6.22:6443

livenessProbe:

httpGet:

path: /

port: 9090

initialDelaySeconds: 30

timeoutSeconds: 30

volumeMounts:

- mountPath: /etc/kubernetes/pki

name: ssl-certs-kubernetes

readOnly: true

- mountPath: /etc/pki

name: ssl-certs-host

readOnly: true

volumes:

- hostPath:

path: /etc/kubernetes/pki

name: ssl-certs-kubernetes

- hostPath:

path: /etc/pki

name: ssl-certs-host

kind: Service

apiVersion: v1

metadata:

labels:

app: kubernetes-dashboard

name: kubernetes-dashboard

namespace: kube-system

spec:

type: NodePort

ports:

port: 80

targetPort: 9090

selector:

app: kubernetes-dashboard

when i comment "- --apiserver-host=https://192.168.6.22:6443",another error "certificate is valid for 192.168.6.22, not 10.254.0.1"