analogue for the `k8s-api` assumes
Bug #1990279 reported by
Robert Gildein
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I think there could bu alternative for `k8s-api` assumption.
It is possible to deploy a machine charm on k8s even if it doesn't
work and therefore I think it would be beneficial to have
an alternative to `k8s-api`.
A good example is rabbitmq-server, which you cloud deploy on
microk8s, but it does not work. It's not obvious from logs [1] why
it doesn't work, which leads to confusion.
Changed in juju: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
tags: | added: canonical-is |
tags: | added: canonical-data-platform-eng |
To post a comment you must log in.
Hello,
I faced the exact same issue with influxdb. I deployed it on a controller in Kubernetes, and no error, no warning. The charm was failing at the install event.
That's very confusing and I didn't expect to be allowed to deploy a machine charm on a K8S controller