<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>websocket on Cisco Techblog</title><link>https://techblog.cisco.com/tags/websocket/</link><description>Recent posts on the Banzai Cloud Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 12 Jul 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://techblog.cisco.com/tags/websocket/index.xml" rel="self" type="application/rss+xml"/><item><title>Proxy WebSocket through Kubernetes API server</title><link>https://techblog.cisco.com/blog/proxy-websocket-kubernetes-api-server/?utm_source=blog&amp;utm_medium=rss&amp;utm_campaign=blog_rss</link><pubDate>Sun, 12 Jul 2020 00:00:00 +0000</pubDate><guid>https://techblog.cisco.com/blog/proxy-websocket-kubernetes-api-server/?utm_source=blog&amp;utm_medium=rss&amp;utm_campaign=blog_rss</guid><description>It may not be a well-known fact, but a Kubernetes API server can proxy HTTP connections between a client and any service running on a cluster. A simple kubectl command exists that allows it:
$ kubectl proxy Starting to serve on 127.0.0.1:8001 We use this for demo purposes or when we don&amp;rsquo;t want to expose APIs publicly, but need to access them from our computers. Moreover, this proxy can transport WebSocket connections.</description></item></channel></rss>