[TOPIC] - Advanced deployment
Have some feedback about the advanced deployment features? Discuss it here.
Hi. u will add later when release CronJob, IngressRouter etc? I liked your project in kubernetes, I used the portainer before, but now I migrated everything to kubernetes, if you add all the features it will look beautiful, would be nice to also have a graphic of the entire structure as kiali does to give it a charm and fragments of the network, as well this is already too much for a beta, good job 👏 👏
Hi @BlackMix,
Of course we'll think about support for other Kubernetes resources (with our own twist though, see how we can continue with our simplified approach).
Thanks for the feedback !
namespace support would be good. I am able to setup and use namespaces in the advanced deployment, but dont see them in the app ui, tough resource pools are displayed. (or i just missed the namespace?)
@WhiteBahamut Resource pool is a wrapper around namespaces (it uses a namespace behind the scenes).
I will try to recreate it properly. But here in short: I had created a resource poll and then did an "Expert Mode" deployment via yaml. had used the namespace property in my yaml, same name as the resource pool and got an error for "missing namespace". Once I created the namespace within my yaml all was fine
In advanced deployment you don't need to specify namespaces in your manifest YAML, just select the resource pool in which you want to deploy the manifest.
Worth noting that advanced deployment do not support deploying in different namespaces at the same time.
Here my easy repo (original yaml was much larger):

Error msg:

So it might just occour for me while I play around and just paste some yaml into it ;-) But it would also be good if the "Resource Pool" option let me select something like "Create new from yaml...".
@WhiteBahamut
So basically the advanced deployment view allows you to deploy a manifest inside a resource pool (namespace).
What you're trying to do here with your manifest is: "I want to deploy this manifest inside the test resource pool (= test namespace)" and in your manifest you also say "deploy this in the not-resource-pool-ns namespace.
There is a conflict. Behind the scene this view is going to do `kubectl apply -n test ..."