is juju deploy <Model> --config juju-external-hostname= changed?

1

Hi every one is the --config juju-external-hostname changed?

$ juju deploy <app> --config juju-external-hostname=app.test
ERROR unknown option "juju-external-hostname"
ERROR Charm cannot be deployed because:
  - charm must be deployed on a Kubernetes cloud
ERROR failed to deploy charm "<app>

please help

I have juju and k8s running inside MAAS

2

do you mean, it succeeds without the --config ... flag?

That feels unlikely. The error makes me think you’re trying to deploy a k8s charm on a machine model.

3

yes correct! is that wrong?

I have added k8s client to juju with juju add-k8s app (then choosing option 1 for client) then bootstrapped it then juju add-model app then juju deploy <app> --config juju-external-hostname=app.test where there an error

4

what charm is that?

5

kubecon I think

6

oh, hello-kubecon charm. It seems to work for me. Can you show me the outputs of juju controllers and juju models and juju status?

7

ok,

juju controllers
Use --refresh option with this command to see the latest information.

Controller           Model          User   Access     Cloud/Region        Models  Nodes    HA  Version
maas-cloud-default*  hello-kubecon  admin  superuser  maas-cloud/default       2     10  none  3.6.2

juju status

$ juju status
Model          Controller          Cloud/Region        Version  SLA          Timestamp
hello-kubecon  maas-cloud-default  maas-cloud/default  3.6.2    unsupported  15:10:10Z

Model "admin/hello-kubecon" is empty.

 juju models

Controller: maas-cloud-default

Model           Cloud/Region        Type  Status     Machines  Cores  Units  Access  Last connection
controller      maas-cloud/default  maas  available        10     31  18     admin   just now
hello-kubecon*  maas-cloud/default  maas  available         0      -  -      admin   3 hours ago
8

so you are currently connected to the maas cloud, which is a machine cloud. You should bootstrap a k8s cloud (e.g. run microk8s and then bootstrap a controller there) instead.

You can’t deploy a k8s charm such as hello-kubecon to a maas cloud.

follow for example: https://juju.is/docs/sdk/dev-setup#heading--set-up-your-development-environment-automatically

9

I already have k8s-core on the controller, I will share the status on the controller, using ubuntu pastebin below. I’m trying a a HA cluster with 3 VMs and K8s-core

Control juju status

10

ok you have a kubernetes, but you should see a controller of type k8s in the output of juju controllers and as far as I can tell, you don’t

what’s missing then is you should bootstrap a controller on that k8s cloud

11

struggling on this one

ERROR could not upload k8s cloud to a controller: cloud "my-k8s" already exists (already exists)

when I try juju add-k8s my-k8s it seems the relations that are created are 1 controller with 2 models

12

you already have a k8s cloud somewhere, the bit you’re missing is bootstrap a juju controller on it. I’d say dive into the docs. Probably you’ll need to get the kubeconfig file from the cloud and pass it to juju bootstrap, or something like that.

14

Hi @ppasotti thanks for help buddy. my ceph was not downloading the pluggins, its all good now I have a full k8s settled

15

ah! great to hear :slight_smile: good luck!