Hi.
I had added an item for this:
https://bugs.launchpad.net/magnum/+bug/1752433
after the last reply and a bit of searching around.
It's not urgent but we already got a couple cases in our deployment.
Cheers,
Ricardo
On Thu, Mar 1, 2018 at 3:44 PM, Spyros Trigazis wrote:
> Hello,
>
> After d
Hello,
After discussion with the keystone team at the above session, keystone
will not provide a way to transfer trusts nor application credentials,
since it doesn't address the above problem (the member that leaves the team
can auth with keystone if he has the trust/app-creds).
In magnum we need
Hi Lance.
On Mon, Feb 26, 2018 at 4:45 PM, Lance Bragstad wrote:
>
>
> On 02/26/2018 10:17 AM, Ricardo Rocha wrote:
>> Hi.
>>
>> We have an issue on the way Magnum uses keystone trusts.
>>
>> Magnum clusters are created in a given project using HEAT, and require
>> a trust token to communicate ba
On 02/26/2018 10:17 AM, Ricardo Rocha wrote:
> Hi.
>
> We have an issue on the way Magnum uses keystone trusts.
>
> Magnum clusters are created in a given project using HEAT, and require
> a trust token to communicate back with OpenStack services - there is
> also integration with Kubernetes via
Hi.
We have an issue on the way Magnum uses keystone trusts.
Magnum clusters are created in a given project using HEAT, and require
a trust token to communicate back with OpenStack services - there is
also integration with Kubernetes via a cloud provider.
This trust belongs to a given user, not
