{"id":2587,"date":"2019-03-13T08:43:31","date_gmt":"2019-03-13T12:43:31","guid":{"rendered":"http:\/\/www.soul-repairs.com\/blog\/?p=2587"},"modified":"2019-03-12T11:44:18","modified_gmt":"2019-03-12T15:44:18","slug":"openshift-2019-roadmap-whats-cool","status":"publish","type":"post","link":"https:\/\/soul-repairs.com\/blog\/2019\/03\/13\/openshift-2019-roadmap-whats-cool\/","title":{"rendered":"OpenShift 2019 Roadmap &#8211; What&#8217;s Cool?"},"content":{"rendered":"<h2 class=\"qowt-stl-Heading1\" style=\"text-align: left;\"><span id=\"E185\">OpenShift 3.11 release<\/span><\/h2>\n<p>In late 2018, Red Hat released OpenShift 3.11. Major features <span id=\"E188\">we <\/span>cared about were:<\/p>\n<ul>\n<li id=\"E190\" class=\"qowt-li-1_0 qowt-list qowt-stl-ListParagraph\"><span id=\"E191\">CRI-O \u2013 a replacement container service (over <a href=\"https:\/\/www.docker.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">Docker<\/a>, although it <em>can<\/em> still run Docker containers) that isn&#8217;t controlled by a single company<\/span>\u00a0(<a href=\"https:\/\/www.projectatomic.io\/blog\/2017\/06\/6-reasons-why-cri-o-is-the-best-runtime-for-kubernetes\/\" target=\"_blank\" rel=\"noopener noreferrer\">6 Reasons why CRI-O is the best runtime for Kubernetes<\/a><span id=\"E198\">) <\/span><\/li>\n<li id=\"E199\" class=\"qowt-li-1_0 qowt-list qowt-stl-ListParagraph\"><span id=\"E200\">Improved infrastructure alerting and monitoring<\/span><\/li>\n<li id=\"E201\" class=\"qowt-li-1_0 qowt-list qowt-stl-ListParagraph\">New web console for admins\n<p><figure id=\"attachment_2589\" aria-describedby=\"caption-attachment-2589\" style=\"width: 640px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_3.11_node_overview.png\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-2589 size-large\" src=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_3.11_node_overview-1024x300.png\" alt=\"\" width=\"640\" height=\"188\" srcset=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_3.11_node_overview-1024x300.png 1024w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_3.11_node_overview-300x88.png 300w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_3.11_node_overview-768x225.png 768w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_3.11_node_overview-604x177.png 604w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_3.11_node_overview.png 1629w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/a><figcaption id=\"caption-attachment-2589\" class=\"wp-caption-text\">New Node Monitoring UI<\/figcaption><\/figure><\/li>\n<\/ul>\n<p id=\"E203\"><span id=\"E204\">There are some great words <a href=\"https:\/\/blog.openshift.com\/wp-content\/uploads\/OpenShift-Commons-Whats-New-in-OpenShift-Container-Platform-3.11.pdf\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a> about what else was part of 3.11.<\/span><\/p>\n<p><!--more--><\/p>\n<p id=\"E226\"><span id=\"E227\">For what it&#8217;s worth, upgrades don&#8217;t <strong>have<\/strong> to be super painful. At our last company, we updated very smoothly from 3.6 to 3.10 via a parallel upgrade and resource copy (via some super sweet automation, <img loading=\"lazy\" decoding=\"async\" class=\"emoji alignnone wp-image-2547 size-thumbnail\" src=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/success-150x150.png\" alt=\"\" width=\"150\" height=\"150\" \/>,\u00a0<em>nerd alert&#8230;<\/em>) and then did an immediate upgrade in place to 3.11.<\/span><\/p>\n<h2>What Are We Excited about in OpenShift 4.0?<\/h2>\n<figure id=\"attachment_2590\" aria-describedby=\"caption-attachment-2590\" style=\"width: 450px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_roadmap-2019.png\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-2590\" src=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_roadmap-2019-300x166.png\" alt=\"\" width=\"450\" height=\"249\" srcset=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_roadmap-2019-300x166.png 300w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_roadmap-2019-768x426.png 768w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_roadmap-2019-487x270.png 487w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/openshift_roadmap-2019.png 956w\" sizes=\"auto, (max-width: 450px) 100vw, 450px\" \/><\/a><figcaption id=\"caption-attachment-2590\" class=\"wp-caption-text\">The Roadmap! A lot of what we know comes from the predictions made in talks, most notably the 3.11 Commons briefing.<\/figcaption><\/figure>\n<h3>Highlights<\/h3>\n<p><span id=\"E254\">Red Hat is switching over to CoreOS as the host OS, and that will enable a lot of nice features like over the air updates and infrastructure alerting. <a href=\"https:\/\/blog.openshift.com\/openshift-4-a-noops-platform\/\" target=\"_blank\" rel=\"noopener noreferrer\">Operations will find this to be a lot easier.<\/a><\/span><span id=\"E256\">\u00a0<\/span><\/p>\n<p id=\"E260\"><span id=\"E261\">Major updates are coming for the internal registry. Red Hat is planning on <a href=\"https:\/\/coreos.com\/blog\/coreos-tech-to-combine-with-red-hat-openshift\" target=\"_blank\" rel=\"noopener noreferrer\">swapping out the existing internal registry<\/a> technology for Quay<\/span><span id=\"E265\">,<\/span><span id=\"E267\"> the registry technology they acquired from Tectonic\/CoreOS <\/span><span id=\"E269\">(<\/span><span id=\"E271\">actually<\/span><span id=\"E273\"> many of the new features in the 4.x series of releases look to be rolling in features from the Tectonic\/CoreOS purchase).<\/span><\/p>\n<p id=\"E274\"><span id=\"E275\">Quay\u2019s major features include geo replication and <a href=\"https:\/\/coreos.com\/blog\/vulnerability-analysis-for-containers.html?utm_source=blog&amp;utm_medium=referral\" target=\"_blank\" rel=\"noopener noreferrer\">integrated container security<\/a> <\/span><span id=\"E277\">scanning<\/span><span id=\"E279\"> with <a href=\"https:\/\/github.com\/coreos\/clair\" target=\"_blank\" rel=\"noopener noreferrer\">Clair<\/a><\/span><span id=\"E282\">. Red Hat plans to produce one version of Quay (to include with OpenShift) that matches the features in the existing OpenShift registry. They&#8217;ll also produce <em>another<\/em> version of Quay that has all of the bells and whistles that Quay provides now.<\/span><\/p>\n<h2>More Exciting Stuff in 4.1!<\/h2>\n<h3>Istio! <img loading=\"lazy\" decoding=\"async\" class=\"emoji alignnone wp-image-2591 size-thumbnail\" src=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-150x150.png\" alt=\"HI Istio!\" width=\"150\" height=\"150\" srcset=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-150x150.png 150w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-300x300.png 300w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-270x270.png 270w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio.png 400w\" sizes=\"auto, (max-width: 150px) 100vw, 150px\" \/><\/h3>\n<figure id=\"attachment_2592\" aria-describedby=\"caption-attachment-2592\" style=\"width: 250px\" class=\"wp-caption alignright\"><a href=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-visualization.png\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-2592\" src=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-visualization-300x220.png\" alt=\"\" width=\"250\" height=\"183\" srcset=\"https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-visualization-300x220.png 300w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-visualization-768x563.png 768w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-visualization-1024x750.png 1024w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-visualization-369x270.png 369w, https:\/\/soul-repairs.com\/blog\/wp-content\/uploads\/2019\/02\/istio-visualization.png 1436w\" sizes=\"auto, (max-width: 250px) 100vw, 250px\" \/><\/a><figcaption id=\"caption-attachment-2592\" class=\"wp-caption-text\">Istio service virtualization<\/figcaption><\/figure>\n<p>Understanding Istio is a <a href=\"https:\/\/developers.redhat.com\/topics\/service-mesh\/\" target=\"_blank\" rel=\"noopener noreferrer\">whole series of blog posts<\/a> (or even a <a href=\"https:\/\/blog.christianposta.com\/our-book-has-been-released-introducing-istio-service-mesh-for-microservices\/\" target=\"_blank\" rel=\"noopener noreferrer\">book<\/a>) on its own, but the short version is that it\u2019s an excellent service mesh &#8211; which can both <em>monitor<\/em> and <em>control<\/em> all network traffic in a cluster.<\/p>\n<p>It\u2019s been in Tech Preview for a few releases, and it\u2019s planned to go live in version 4.1.<\/p>\n<h3>Serverless: Knative?<\/h3>\n<p>The OpenShift Roadmap mentions &#8220;Serverless&#8221; in Tech Preview.<\/p>\n<p>According to the <a href=\"https:\/\/www.cncf.io\/blog\/2018\/02\/14\/cncf-takes-first-step-towards-serverless-computing\/\" target=\"_blank\" rel=\"noopener noreferrer\">CNCF<\/a>,<\/p>\n<blockquote><p>Serverless computing refers to the concept of building and running applications that do not require server management. It describes a finer-grained deployment model where applications, bundled as one or more functions, are uploaded to a platform and then executed, scaled, and billed in response to the exact demand needed at the moment.\u201d<\/p><\/blockquote>\n<p>TLDR: if containers are a simpler way to deploy and run applications than VMs,\u00a0<strong><em>serverless\u00a0<\/em>applications are an even simpler way to run applications than containers.<\/strong> You don&#8217;t have to worry about middleware at all, you just write some code and deploy it.<\/p>\n<p>There are several serverless options out there, and <a href=\"https:\/\/www.redhat.com\/en\/blog\/serverless-next-phase-cloud-native-application-development\" target=\"_blank\" rel=\"noopener noreferrer\">the original OpenShift discussions were around OpenWhisk<\/a>, but the OpenShift blog has several posts. Here are a couple good ones explaining more about it:<\/p>\n<ul>\n<li><a href=\"https:\/\/blog.openshift.com\/knative-serving-your-serverless-services\/\" target=\"_blank\" rel=\"noopener noreferrer\">3-part series on Knative<\/a><\/li>\n<li><a href=\"https:\/\/blog.openshift.com\/state-of-serverless-in-kubernetes-knative-and-openshift-cloud-functions\/\" target=\"_blank\" rel=\"noopener noreferrer\">The State of Serverless<\/a><\/li>\n<\/ul>\n<p>Our best guess is that <a href=\"https:\/\/cloud.google.com\/knative\/\" target=\"_blank\" rel=\"noopener noreferrer\">Knative<\/a> will be the flavor of serverless technology that goes into Tech Preview in 4.1. This is good, because it&#8217;s the most open and widely supported serverless technology.<\/p>\n<h3 id=\"E339\" class=\"qowt-stl-Heading3\"><span id=\"E340\">Eclipse <\/span><span id=\"E342\">Che<\/span><span id=\"E344\">: Cloud-based IDE<\/span><\/h3>\n<p><a href=\"https:\/\/www.eclipse.org\/che\/\" target=\"_blank\" rel=\"noopener noreferrer\">Eclipse Che<\/a> is a browser-based IDE. We&#8217;re interested in it because it means that a developer can do all of their usual programmer tasks with zero desktop application install. Just click a link, wait for Che to load, and be off and running. Compared to setting up a desktop-based Eclipse IDE and getting servers running locally, this could be another <strong>huge<\/strong> improvement in developer efficiency with OpenShift and containers.<\/p>\n<p>Originally Che was planned for OpenShift 4.x, but it was recently branded as <a href=\"https:\/\/developers.redhat.com\/products\/codeready-workspaces\/overview\/\" target=\"_blank\" rel=\"noopener noreferrer\"><em>Code Ready Workspaces<\/em><\/a> and released &#8211; we aren&#8217;t entirely sure why it&#8217;s on the Roadmap still, but hey, good news! You don&#8217;t have to wait for 4.x to use it.<\/p>\n<h2 id=\"E346\" class=\"qowt-stl-Heading2\"><span id=\"E347\">The Future<\/span><\/h2>\n<p id=\"E348\"><span id=\"E350\">OpenShift\u2019s<\/span><span id=\"E352\"> future has a lot of cool stuff in it &#8211; and we don\u2019t even know the road map beyond <\/span><span id=\"E354\">mid 2019. Chances are good that a lot <em>more<\/em> cool stuff <\/span><span id=\"E356\">will be announced at <a href=\"http:\/\/www.redhat.com\/Red_Hat\/Summit_19\u200e\" target=\"_blank\" rel=\"noopener noreferrer\">Summit<\/a>, in May.<\/span><\/p>\n<p id=\"E357\"><span id=\"E358\">Also, if <del>creepy-stalking<\/del> <a href=\"https:\/\/soul-repairs.com\/blog\/2019\/01\/10\/the-five-most-important-ingredients-in-doing-technical-stuff\/\" target=\"_blank\" rel=\"noopener noreferrer\">being good at finding stuff on the internet<\/a> is your jam, you can also keep an eye on the <a href=\"https:\/\/trello.com\/atomicopenshift\" target=\"_blank\" rel=\"noopener noreferrer\">OpenShift Trello boards<\/a>.\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>OpenShift 3.11 release In late 2018, Red Hat released OpenShift 3.11. Major features we cared about were: CRI-O \u2013 a replacement container service (over Docker, although it can still run Docker containers) that isn&#8217;t controlled by a single company\u00a0(6 Reasons why CRI-O is the best runtime for Kubernetes) Improved infrastructure alerting and monitoring New web &hellip; <\/p>\n<p class=\"read-more\"><a class=\"btn btn-default\" href=\"https:\/\/soul-repairs.com\/blog\/2019\/03\/13\/openshift-2019-roadmap-whats-cool\/\"> Read More<span class=\"screen-reader-text\">  Read More<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[4],"tags":[112,88,82,91,92,44,113],"wf_post_folders":[],"coauthors":[11,26],"class_list":["post-2587","post","type-post","status-publish","format-standard","hentry","category-technology","tag-che","tag-cri-o","tag-docker","tag-istio","tag-knative","tag-openshift","tag-red-hat"],"_links":{"self":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts\/2587","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/comments?post=2587"}],"version-history":[{"count":28,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts\/2587\/revisions"}],"predecessor-version":[{"id":2673,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts\/2587\/revisions\/2673"}],"wp:attachment":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/media?parent=2587"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/categories?post=2587"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/tags?post=2587"},{"taxonomy":"wf_post_folders","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/wf_post_folders?post=2587"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/coauthors?post=2587"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}