I think what we have here is a misunderstanding between --config and
--model-defaults
Configuration that is passed in with --config applies JUST to the
controller model.
If you are wanting particular configuration to apply to new models as
well, then you need to specify --model-defaults.
Any config that is passed in to model-defaults will also apply to the
controller model.
Tim
On 8/10/19 1:23 PM, Harry Pidcock wrote:
> Can we get some more information about this please.
>
> What do you expect to happen with the proxy env vars. Should they be
> applied to just the controller or do you want them injected into every
> container on every pod managed by Juju?
>
> Also in relation to the k8s cluster, is it just microk8s or is it also
> intended to work on CDK/GKE/AKS/EKS etc.
>
> Where would the proxy server be running? Inside the cluster or outside?
> If inside is it running as a service?
>
> Is the cluster using Istio or a CNI like Calico or Flannel?
>
> ** Changed in: juju
> Status: Triaged => Incomplete
>
I think what we have here is a misunderstanding between --config and
--model-defaults
Configuration that is passed in with --config applies JUST to the
controller model.
If you are wanting particular configuration to apply to new models as
well, then you need to specify --model-defaults.
Any config that is passed in to model-defaults will also apply to the
controller model.
Tim
On 8/10/19 1:23 PM, Harry Pidcock wrote:
> Can we get some more information about this please.
>
> What do you expect to happen with the proxy env vars. Should they be
> applied to just the controller or do you want them injected into every
> container on every pod managed by Juju?
>
> Also in relation to the k8s cluster, is it just microk8s or is it also
> intended to work on CDK/GKE/AKS/EKS etc.
>
> Where would the proxy server be running? Inside the cluster or outside?
> If inside is it running as a service?
>
> Is the cluster using Istio or a CNI like Calico or Flannel?
>
> ** Changed in: juju
> Status: Triaged => Incomplete
>