-
### Context
Each charm in Kubeflow has a ROCK (or a set of ROCKs) it is using. The process of upgrading ROCKs usually means going to the component's upstream repository Dockerfile, comparing current …
-
### Context
Each charm in Kubeflow has a ROCK (or a set of ROCKs) it is using. The process of upgrading ROCKs usually means going to the component's upstream repository Dockerfile, comparing current …
-
### Bug Description
Following the [tutorial](https://juju.is/docs/sdk/write-your-first-kubernetes-charm-for-a-flask-app) to set up and charm `simple-flask`, after running the `juju deploy ./charm/s…
-
### What needs to get done
`charmcraft upload-resource` should be able to upload an OCI image directly from a file rather than requiring a digest and extracting it from a registry.
### Why it needs …
-
### Context
Each charm in Kubeflow has a ROCK (or a set of ROCKs) it is using. The process of upgrading ROCKs usually means going to the component's upstream repository Dockerfile, comparing current …
-
# Description
When using `pebble enter` (which is the case for all rocks), Pebble will keep logging to STDOUT, regardless of the provided subcommand.
Not only that, but it appears that there's …
-
### Context
Each charm in Kubeflow has a ROCK (or a set of ROCKs) it is using. The process of upgrading ROCKs usually means going to the component's upstream repository Dockerfile, comparing current …
-
### Context
Each charm in Kubeflow has a ROCK (or a set of ROCKs) it is using. The process of upgrading ROCKs usually means going to the component's upstream repository Dockerfile, comparing current …
-
### Context
Each charm in Kubeflow has a ROCK (or a set of ROCKs) it is using. The process of upgrading ROCKs usually means going to the component's upstream repository Dockerfile, comparing current …
-
#### Summary
Make sure to follow the steps below and ensure all actions are completed and signed-off by one team member.
#### Information
- **K8s version**: 1.xx
- **Owner**: @addyess …