X-Git-Url: https://osm.etsi.org/gitweb/?a=blobdiff_plain;f=Release8%2Fk8s_proxy_charms.md;fp=Release8%2Fk8s_proxy_charms.md;h=eb1b9b8778f9566f2247d15e862430aed4e52a7f;hb=01fc71a4914868f178ed461f5f5e2a7387ee04fb;hp=0000000000000000000000000000000000000000;hpb=2c75c75c0ea263661cd4c570799a1ae4a608b87c;p=osm%2FFeatures.git

diff --git a/Release8/k8s_proxy_charms.md b/Release8/k8s_proxy_charms.md
new file mode 100644
index 0000000..eb1b9b8
--- /dev/null
+++ b/Release8/k8s_proxy_charms.md
@@ -0,0 +1,33 @@
+# Proxy Charms on K8s #
+
+## Proposer ##
+Tytus Kurek (Canonical)
+David Garcia (Canonical)
+Dominik Fleischmann (Canonical)
+
+## Type ##
+**Feature**
+
+## Target MDG/TF ##
+IM, LCM, N2VC
+
+## Description ##
+Currrently proxy charms are deployed on LXD. This allows us to have these workloads
+running without consuming a lot of resources.Nevertheless with OSM starting to be
+used for production level deployments new methods of deploying these workloads shall
+be considered.
+
+By deploying proxy charms on Kuberentes the deployments will be faster and will ensure
+all the orchestration features already available in a K8s cluster. This will be achieved
+by adding an additional field in the descriptors stating that this proxy charm will be
+deployed on Kubernetes (k8s-proxy-charm). The charm will then be deployed in a Kubernetes
+that must have been added previously with `k8scluster-add` and will operate the same way
+as a proxy charm in LXD.
+
+In the charm implementation the only thing that should change is the charm series in the
+metadata.yaml which will be changed to `series: kubernetes`.
+
+## Definition of done #
+Once this feature is implemented the user will be able to deploy proxy charms on
+kubernetes by changing the above mentioned charm series and setting the k8s-proxy-charm
+field in their descriptors.