<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" 
  xmlns:content="http://purl.org/rss/1.0/modules/content/" 
  xmlns:dc="http://purl.org/dc/elements/1.1/" 
  xmlns:atom="http://www.w3.org/2005/Atom" 
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" 
  xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>scc on Failing with Kubernetes</title>
    <link>http://jorgemoral.es/tags/scc/</link>
    <description>Recent content in scc on Failing with Kubernetes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>©{year}, All Rights Reserved</copyright>
    <lastBuildDate>Fri, 15 Apr 2016 00:00:00 +0000</lastBuildDate>
    
        <atom:link href="http://jorgemoral.es/tags/scc/index.xml" rel="self" type="application/rss+xml" />
    
    
    

      
      <item>
        <title>Understanding Service Accounts and SCCs</title>
        <link>http://jorgemoral.es/posts/2016-04-15-understanding-sas_and-sccs/</link>
        <pubDate>Fri, 15 Apr 2016 00:00:00 +0000</pubDate>
        
        <atom:modified>Fri, 15 Apr 2016 00:00:00 +0000</atom:modified>
        <guid>http://jorgemoral.es/posts/2016-04-15-understanding-sas_and-sccs/</guid>
        <description>We launched OpenShift 3.0 back in June 2015 and I have had the pleasure of speaking with users all over Europe and the EMEA region to help them get up and running with deploying applications on the platform. One of the features that developers and administrator often ask questions about are Service Accounts and Security Context Constraints. In this blog post, I will provide a simple introduction into both concepts, how they work and their usage.</description>
        
        <dc:creator>jorgemoralespou</dc:creator>
        
        
        
        
          
            
              <category>openshift</category>
            
          
            
              <category>origin</category>
            
          
            
              <category>scc</category>
            
          
        
        
        
      </item>
      

    
  </channel>
</rss>