<commit_before># High Level Roadmap

Kismatic is focused on simplifying the management of privately hosted Kubernetes by making best practices simpler to implement.

1. Storage
   * Stateful workloads are a fact of life and running them on Kubernetes, with its PersistentVolume awareness, makes sense. We want to make it easy to add durable storage to a cluster via Kismatic. This will also allow us to set aside some amount of durable storage for management tools like Prometheus.  
2. Ingress
   * As it stands, some networking configurations that are possible with Kismatic aren't terribly useful until you also install an Ingress server and controller. It would be valuable to be able to manage this configuration within Kismatic.
3. Kubeadm
   * Requiring a centralized tool to add or change the node layout of the cluster is suboptimal and a barrier to infrastructure elasticity. Kubeadm solves a lot of these issues but it remains too new for us to include in this release.
4. Platform Upgrades
   * Shortly after the release of Kubernetes 1.5, we expect to have a release of Kismatic that will allow upgrades from 1.4 -> 1.5<commit_msg>[skip ci]<commit_after># High Level Roadmap

1. Storage
   * We want to make it easy to add durable storage to a cluster via Kismatic. This will also allow us to set aside some amount of durable storage for management tools like Prometheus and allow our customers to run reliable stateful applications on Kubernetes clustered deployed by KET.
2. Ingress
   * As it stands, some networking configurations that are possible with Kismatic are not possible until an Ingress server and controller is present. It would be valuable to be able to manage this configuration within Kismatic.
3. Kubeadm
   * Requiring a centralized tool to add or change the node layout of the cluster is suboptimal and a barrier to infrastructure elasticity. Kubeadm solves a lot of these issues but it remains too new for us to include in this release. We will continue to support the development of Kubeadm and investigate how to best integrate it with KET over the coming releases.
4. Platform Upgrades
   * Shortly after the release of Kubernetes 1.5, we expect to have a release of Kismatic that will allow upgrades from 1.4 -> 1.5.
{'fraction_non_alphanumeric': 0.02616407982261641, 'fraction_numerical': 0.008869179600886918, 'mean_word_length': 4.210161662817552, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1908426', 'n_tokens_mistral': 550, 'n_tokens_neox': 504, 'n_words': 362}