title: exposing mail or ssh honeypot in kubernetes cluster
body: <p>I'm experimenting with SMTP (mailoney) and SSH honeypots in a Kubernetes cluster to be exposed to the big bad WWW. I cant seem to figure out how to get it working since I'm only beginning to understand Kubernetes just recently. </p>
  
  <p>I've got some config now, for example my mailoney.yaml:</p>
  
  <pre><code>apiVersion: apps/v1
  kind: Deployment
  metadata:
    name: mailoney
  spec:
    selector:
      matchLabels:
        app: mailoney
    template:
      metadata:
        labels:
          app: mailoney
      spec:
        containers:
        - name: mailoney
          image: dtagdevsec/mailoney:2006
          ports:
          - containerPort: 25
  </code></pre>
  
  <p>and the service config:</p>
  
  <pre><code>apiVersion: v1
  kind: Service
  metadata:
    name: ingress-mailoney
    labels:
      name: mailoney
  spec:
    type: LoadBalancer
    ports:
      - name: smtp
        port: 25
        targetPort: 25
        protocol: TCP
    selector:
      name: mailoney
  </code></pre>
  
  <p>But when the loadbalancer is configured, it exposes the services on port >30000, which I know is default behaviour for Kubernetes. But how do I exactly configure the loadbalancer to allow connections on port 25 and 22 respectively and actually letting connections through to the honeypots?</p>
  
  <p>am I overlooking something really obvious?</p>
  
  <p>Any help is appreciated. </p>