serboctor
commented
5 years ago The container template doesn't accept the zt client, it accepts the token. But the authorization isn't working anyway in the container template. The zrobot template also has token in its schema, but I dont see it being used so probably authorization doesn't work there too.
Templates that accept zt client in their schemas:
- coredns
- dm_vm
- etcd
- etcd_cluster
- gateway
- s3
- s3_redundant
- traefik
- vm
- web_gateway
- zerodb
Story : https://github.com/threefoldtech/home/issues/66
Now that we are on the way to the deployment of the 3bot on the grid, we need to clean up all the primitives template so they are really strip down to their bare minimum.
In the vm, container and probably other templates, they accept a zerotier client in their schema. This is used to authorize the service to the zerotier network. This needs to be removed. The only thing accepted is to define a zerotier nic (type zerotier and network id). That's it. The template should not try to authorize to the network. This is the role of the 3bot to authorize the capacity in the network once it's up and running.
@serboctor can you list all the template that are build like that, so we know what needs to be worked on for milestone 9.6.0 please :-)