Exposing Applications

Expose Applications using Kubernetes Services

Internal Services
Internal, cluster local services should be configured as regular ClusterIP services.
Public Services
Exposing services to the Internet is done by deploying a LoadBalancer service type with an annotation to allocate a public IP for the service.
sshd-public-service.yaml
apiVersion: v1
kind: Service
metadata:
  annotations:
    metallb.universe.tf/address-pool: public
    metallb.universe.tf/allow-shared-ip: default
  name: sshd
spec:
  type: LoadBalancer
  externalTrafficPolicy: Local
  ports:
    - name: sshd
      port: 22
      protocol: TCP
      targetPort: sshd
  selector:
    app.kubernetes.io/name: sshd
For most public services, ensure that externalTrafficPolicy: Local is set on the service. This load balances ingress traffic from the Internet directly to the  nodes running the  application.
​

CoreWeave Kubernetes - Previous

Storage

Next - CoreWeave Kubernetes

Serverless

Last updated 1 month ago