Juju add-k8s results in "empty controller name not valid"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Anastasia |
Bug Description
I ran these commands to deploy CDK onto AWS:
juju bootstrap aws/us-east-1 cdkkf
juju deploy cs:bundle/
juju wait -wv
juju kubectl apply -f storage/aws-ebs.yml
juju scp -m cdkkf:default kubernetes-
KUBECONFIG=
That resulted in this error:
ERROR empty controller name not valid
The overlays and snap juju version I'm using:
# overlays/cdk.yml
applications:
kubernetes-
options:
channel: 1.15/stable
kubernetes-
constraints: cores=4 mem=4G root-disk=100G
options:
channel: 1.15/stable
# overlays/
description: Charmed Kubernetes overlay to add native AWS support.
applications:
aws-integrator:
annotations:
gui-x: "600"
gui-y: "300"
charm: cs:~containers/
num_units: 1
trust: true
relations:
- ['aws-integrator', 'kubernetes-
- ['aws-integrator', 'kubernetes-
# overlays/
applications:
kubernetes-
to: ["0"]
machines:
0:
constraints: root-disk=100G instance-
# storage/aws-ebs.yml
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: k8s-ebs
annotations:
storageclas
parameters:
type: gp2
provisioner: kubernetes.
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstCon
# snap info juju
...
installed: 2.7-beta1+
Changed in juju: | |
status: | In Progress → Fix Committed |
milestone: | none → 2.7-beta1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Ah, looks like a refactoring oversight. I'll propose a fix shortly \o/