apiVersion: v1 kind: Service metadata: name: frontend labels: name: frontend spec: type: NodePort ports: - port: 80 - protocol: “TCP” - targetPort: 80 selector: name: frontend use NodePort or LoadBalancer in “type” (Called ServiceType). If you don’t specify any value, then the default value is ClusterIP, which allows connections only from within cluster. NodePort proxies port. NodePort is chosen randomly from a pre-configured range, or can be specified in the definition. The service is then available on each host on which a pod is running at NodePort. NodePort can be

the following information is needed: URL of secure private registry Choose expert mode Choose NodePort for the service Take a note of the service port of the SLC Bridge. It is needed for the installation https://kubernetes.github.io/ingress-nginx/deploy/#bare- metal . Create the nginx-ingress controller as a nodePort service according to the Ingress nginx documentation: $ kubectl apply -f https://raw.githubusercontent CLUSTER-IP EXTERNAL-IP PORT(S) AGE ingress-nginx-controller NodePort 10.43.86.90 80:31963/ TCP,443:{di_version}06/TCP 53d In our example here,

sample shows a post that is published in the WordPress application that can be accessed with the nodeport 31556: Figure 15. Published post in WordPress The following image shows the protection job the new namespace dellwordpressrestore. The restored WordPress application is accessed with the nodeport 31640 as shown in the following sample: Rancher Kubernetes Cluster Data Protection using PowerProtect namespace dellwordpress, on the restored namespace dellwordpressrestore, that is accessed with the nodeport 31640: Figure 23. WordPress post available on the restored namespace This confirms the successful

cluster already has the contrail-analytics namespace defined. Contrail Analytics is installed as a NodePort service. You can reach the service by specifying the IP address of any node running Contrail Analytics cluster already has the contrail-analytics namespace defined. Contrail Analytics is installed as a NodePort service. You can reach the service by specifying the IP address of any node running Contrail Analytics

方式，对于需要直接暴露端口的应用如 Database 等这类 L4 的应用，建议使用 HostPort 模 式。填写容器端口并选择传输协议，如果需要固定对应的宿主机端口，则手动配置主机监听 端口。 网络模式： a) Nodeport： 此网络模式为全局模式，即集群中每台节点的 IP+端口都可以访问对应的服务，Pod 跨主机 时通过 iptables 规则来转发数据； b) Hostport： 类似于 docker

Controller控制器，社区有非常多不同的Ingress Controller实现，比较常用的有Ingress Nginx Controller。 注：除了通过Ingress方式进行服务对外发布以外，Service还提供了NodePort、LoadBalance两种服务类型，针对不同的 应用场景可以选择最适合的方案。 © Copyright 2020 Rancher Labs. All Rights Reserved. Confidential