Kubectl expose: Difference between revisions
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
=Expose a Higher Level Controller= | =Expose a Higher Level Controller= | ||
If a replication controller, deployment or | If a replication controller, deployment or replicaset are used, the command <font color=darkgray>reads their selector and re-uses it for the service being created.</font> | ||
=Expose a Service= | =Expose a Service= | ||
Revision as of 00:07, 20 September 2020
Internal
Overview
expose dynamically exposes a resource, which can be a pod, service, replicationcontroller, deployment or replicaset as a new service.
Expose a Pod
If a pod is used, the command reads the pod's labels and creates a service with a matching selector. By default, if no type is specified, ClusterIP is assumed.
kubectl [-n <namespace>] expose pod <pod-name> --port=<port> --target-port=<target-port> --name=<service-name> [--type=ClusterIP|NodePort|...]
kubectl expose pod httpd --port=9898 --target-port=80 --name=httpd-svc
Expose a Higher Level Controller
If a replication controller, deployment or replicaset are used, the command reads their selector and re-uses it for the service being created.
Expose a Service
The default service type is ClusterIP, other type (NodePort, LoadBalancer, or ExternalName) can be specified with --type.
kubectl [-n default] expose pod pg-0 --port=5432 --target-port=5432 --name=postgres --type=NodePort
TODO: I don't seem to see the service with kubectl get services, but attempting to connect to the database works.