<style> body { background: url( 'https://raw.githubusercontent.com/SovereignCloudStack/website/main/_assets/revealjs/presentation-content.png' ); background-size:cover; background-position: center; } @media print { .backgrounds { background:url('https://raw.githubusercontent.com/SovereignCloudStack/website/main/_assets/revealjs/presentation-content.png'); /* if you used "cover" on screen, * you will probably want "contains" on print */ background-size:contain; background-position: center; } </style> <!-- .slide: data-background="https://raw.githubusercontent.com/SovereignCloudStack/website/main/_assets/revealjs/presentation-main.png" data-background-size="contain" data-background-color="rgb(0,0,0)" --> ## Workload identities ...may be part of SCS someday --- ## Introduction ---  <small>Taking triangle metaphor of technology "layers". Customers generally can consume each of these blocks "as a Service".</small> ---  Humans generally can use the cloud IdP to consume cloud services. --- ## Problem statement --- <small>Most likely, consumers will want to use multiple of these blocks: Users of e. g. Kubernetes may want to consume the container registry and database+pubsub for deployed applications.</small>  --- ## (Potential) solution <small>Kubernetes OIDC Issuer discovery with support of used IdP</small> ---  --- # Thank you!