Skip to content

Latest commit

 

History

History
80 lines (52 loc) · 2.7 KB

DEPRECATION-NOTE.md

File metadata and controls

80 lines (52 loc) · 2.7 KB
Raw

Deprecation Note

This page is related to our components deprecation plan. Components listed below are marked as deprecated with plan of removal in Epiphany version 2.0.

The list of components removed:

  • Hashicorp Vault

The role related to Hashicorp Vault has never been developed beyond MVP/PoC stage and cannot be used for production usage. It also causes troubles with upgrade to new Kubernetes versions.

Removed: Epiphany 2.0 Issue: 2834

  • Istio

We are considering replacement of Istio component with different solution. Additionally, Istio causes problems during upgrade of Kubernetes.

Removed: Epiphany 2.0 Issue: 2836

  • Apache Ignite

Apache Ignite is prone to 1.x log4j issue.

Removed: Epiphany 2.0 Issue: 2837

  • Logstash

The functionality that the Logstash is serving in Epiphany - exporting csv can right now be achieved using the Open Distro for Elasticsearch plugin. The Logstash in this version is prone to log4j issue and this is also the reason it should be removed.

Removed: Epiphany 2.0 Issue: 2833

Next steps

Logstash

If you plan Epiphany upgrade from v1.x to v2.x and Logstash is installed in your cluster, but you don't use it, it is recommended to:

  • remove logstash group, if present, from inventory file
  • remove Logstash from machines (recommended way is to use apt/yum according to your OS)

Ignite

There are a few installation approaches that influence the removal of Ignite.

Standalone installation on VMs

To remove Ignite application in this case, it's necessary to destroy related infrastructure part with following configuration. The epicli apply command with --skip-config flag may be used to run only Terraform part and skip Ansible role provisioning. To be sure about compatibility of applied changes, use the same epicli version.

---
kind: epiphany-cluster
...
specification:
  components:
    ignite:
      count: 0
...

Installation on VMs by usage of custom feature mapping

When custom feature-mapping was used, following actions are required for removal:

  • remove /opt/ignite symlink
  • remove folders in format /opt/ignite_<version>
  • if there are no applications dependent on openjdk packages, such as Kafka/Zookeeper, remove them:
    • openjdk-8-jre-headless for Ubuntu
    • java-1.8.0-openjdk-headless for RHEL

Installation as a K8s application

It was possible to install Ignite only in a separate namespace, ignite by default. If the application is not used anymore, remove its namespace with all content.