Skip to content

Commit df3523c

Browse files
committed
added steps to expose service a vmware based cks cluster
1 parent 5640e12 commit df3523c

File tree

5 files changed

+33
-0
lines changed

5 files changed

+33
-0
lines changed
80.6 KB
Loading
58.6 KB
Loading
29.1 KB
Loading
51.8 KB
Loading

source/plugins/cloudstack-kubernetes-provider.rst

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -148,6 +148,39 @@ on the cluster nodes.
148148

149149
|ckp-ip-lb.png|
150150

151+
.. note::
152+
- In case of Cloudstack + Vmware Intergaration, if you want to expose the application via Public Ipaddress, you have to expose it as a Node-port service and manually add the rules in cloudstack.
153+
154+
Example
155+
156+
.. parsed-literal::
157+
158+
1. Expose the application service as a Node port service.
159+
160+
kubectl expose deploy/nginx-deployment --port=80 --type=Nodeport
161+
162+
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
163+
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 5d1h
164+
nginx-deployment2 NodePort 10.103.111.85 <none> 80:32014/TCP 4s
165+
166+
2. Navigate to network and acquire a public IP.
167+
168+
|cks-acquire-publicip.png|
169+
170+
3. Add a firewall rule on port 80 on the public IP address
171+
172+
|cks-addfirewall.png|
173+
174+
4. Add a loadbalcner rule mentioning the private node port and add the corresponding kubenetes worker node.
175+
176+
|cks-addloadbalancer.png|
177+
178+
|cks-addnode.png|
179+
151180
.. |ckp-ip.png| image:: /_static/images/ckp-ip.png
152181
.. |ckp-ip-fw.png| image:: /_static/images/ckp-ip-fw.png
153182
.. |ckp-ip-lb.png| image:: /_static/images/ckp-ip-lb.png
183+
.. |cks-acquire-publicip.png| image:: /_static/images/cks-acquire-publicip.png
184+
.. |cks-addfirewall.png| image:: /_static/images/cks-addfirewall.png
185+
.. |cks-addloadbalancer.png| image:: /_static/images/cks-addloadbalancer.png
186+
.. |cks-addnode.png| image:: /_static/images/cks-addnode.png

0 commit comments

Comments
 (0)