Deploying Infrastructure Stacks manually (via compose)

[garceri]

We are trying a modified version of the Rancher-EBS stack but when deploy it from the UI or via compose the stack ends up as a normal "User" stack instead of getting under Infrastructure as when deployed from the catalog, is there a tag/label that we can use to mark a stack as Infrastructure from the compose files ?

[joshwget]

rancher stack create has a --system flag. I don't think anything currently exists in the UI for this use case unless you add your own catalog.

[garceri]

@joshwget Doesn't seem to work:

$ /home/user/rancher stack create TESTEBS -s -e
1st813
$ /home/user/rancher stack -s |grep TESTEBS
ID        NAME                    STATE       CATALOG                                       SERVICES   SYSTEM    DETAIL
1st813    TESTEBS                 healthy                                                   0          @false     

[pasikarkkainen]

I've noticed the same problem. "system" parameter for rancher cli doesn't work. The resulting new stack isn't marked as system/infra service.

[danielmkraus]

I was struggling with this issue and realize the rancher-cli restrict creation / update of system stacks with environment api keys. Tried to create a stack with system flag (-s) with account api key and rancher cli creates new stack as a infrastructure stack.

[loganhz]

Please let us know in a comment if you can still reproduce the issue, and we'll reopen it