You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@stratos.apache.org by Chamila De Alwis <ch...@wso2.com> on 2014/10/25 14:57:08 UTC

Passing Subscription Key to the Container in Kubernetes Setup

Hi,

When subscribing to a cartridge, the VM flow is to create a subscription
key and pass it as a payload parameter through the IaaS metadata service,
as CARTRIDGE_KEY. This will be used as the secret key in password
decryption for repository password in artifact management.

How is the subscription key made accessible to a container in the
Kubernetes + Docker setup? Do we currently have a code path where the
generated payload data are passed to the container from the Stratos
Manager?

Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com

Re: Passing Subscription Key to the Container in Kubernetes Setup

Posted by Nirmal Fernando <ni...@gmail.com>.

It's the same way as VM Chamila.

On Sat, Oct 25, 2014 at 2:57 PM, Chamila De Alwis <ch...@wso2.com> wrote:

> Hi,
>
> When subscribing to a cartridge, the VM flow is to create a subscription
> key and pass it as a payload parameter through the IaaS metadata service,
> as CARTRIDGE_KEY. This will be used as the secret key in password
> decryption for repository password in artifact management.
>
> How is the subscription key made accessible to a container in the
> Kubernetes + Docker setup? Do we currently have a code path where the
> generated payload data are passed to the container from the Stratos
> Manager?
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>


-- 
Best Regards,
Nirmal

Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.

Blog: http://nirmalfdo.blogspot.com/