Shipa v1.2 Release

Release Date: Jan 2021

We are pleased to present Shipa 1.2 release.

New Features & Enhancements

This release adds improvements related to the following components and concepts.

  •     Ingress Controller
  •     Network Policies
  •     Security
  •     Developer Experience
  •     Web Console
  •     Application Management
  •     Clusters

Ingress Controller Support

Allow users to use Istio ingress controller
Shipa users can now leverage their existing Istio ingress controller for their applications deployed on Shipa.
Shipa simplifies using Service Mesh by abstracting the complexities away, empowering users to define services communication policies. Shipa users can get the most out of Istio through functionalities such as Canary rollouts, metrics, CNAME, and HTTPS.


Network Policies Map
Shipa Network Policy Map is a visual translation of standard Kubernetes network policies representing the superficial abstraction level that Shipa offers when restricting or allowing traffic flow between applications. Shipa users can set rules for the application and have an automated visualization of all application policies displayed on Shilpa’s UI.


Integration with Vault
Shipa users now can inject secrets from their Harshicorp Vault into their Kubernetes applications deployed using Shipa.

Developer Experience

Allow users to pull images from private registries
Shipa now provides the ability to deploy applications with docker images stored in private registries. This feature uses an image URL, docker username, and password/access token to gain access.

Web Console

Application Vulnerabilities Dashboard
Better visibility of application security on the dashboard, now users can see a summary of vulnerabilities that were "granted" vs. the total found.

Application Deployment from the Dashboard
Shipa users can deploy their applications directly from the dashboard page, creating a convenient and fast deployment option.

Application Management

Move applications from one framework to another.
Frameworks are the central point for application deployment control on Shipa, acting as templates that group different configuration sets that will automatically be applied to any application deployed on that framework.
The capability of moving applications from one framework to another empowers the user to test and use their application in different scenarios.


Simplifying cluster configuration
By requesting ingress configuration based on the framework.

Improve Cluster Page View
Add metadata on the cluster page to reflect API changes.

Resolved Issues

This section list limitation that is resolved with this release.

Ingress Controller

  • Shipa-862 Updating cluster to add Istio pool results in a silent error
  • Shipa-792 Adding a second pool to a cluster with Istio does not create the namespace in the cluster - After updating the cluster to add the second pool, it gives the message completed successfully. Still, it fails when it creates an application pointing to that second pool in the cluster.
  • Shipa-791 Deploying apps on a cluster with Istio fails - On the CLI fails displays an error message; when deploying from the dashboard, the deployment fails without showing notifications.
  • Shipa-790 Connecting a cluster with Istio required the user to enter a namespace - When adding a cluster with Istio without specifying any pool name, it reports an error.
  • Shipa-709 CNAME does not work on Istio - CNAME does not work for applications deployed using Istio as a router option.
  • Shipa-710 Istio-proxy installed on Traefik applications - Applications deployed using Traefik router are getting Istio-proxy installed on its pod.
  • Shipa-724 Application with vault annotations and Istio fails to deploy - When deploying applications using Istio as a router option, deployment results in failure. The Vault container can’t access the Vault services.
  • Shipa-789 Removing multiple router choices from when creating applications - When creating applications using the dashboard, developers can choose which router to use (Istio or Traefik). Instead, the application should automatically pick up the router defined previously by the Platform Engineer.


  • Shipa-711 Vault secret injection does not work for docker image applications - Deploying an application using a docker image doesn’t inject secrets on the deployed pod.


  • Shipa-778 Issue on “deny-all” rule on network policy - After removing a network rule that denies access, ingress, and egress, the access to the application is still blocked, not bring it back to the default rule “allow-all.”
  • Shipa-727 Application deployment running on a specific port fails - Not able to access applications deployed on a particular port set by the users.

Web Console

  • Shipa-845 Blank UI displayed on “Node Distribution Chart Page.” - When moving across different views and coming back to the Dashboard page, the Node Distribution chart does not show any data or chart.
    Shipa-796 Application map returns an error during load.

  • Shipa-775 Shipa credentials list error - When there is no credential present, the shipa credentials list reports an error.

  • Shipa-769 Environment variable value is visible on the dashboard - When creating a private env variable to an application using the dashboard, the variable value is exposed on the dashboard instead of being masked.

  • Shipa-758 App Lifecycle data fetching fails after React Query upgrade - After upgrading React Query to v2.0.0, the data fetching process that happens on the lifecycle table does not work.

  • Shipa-738 Instance data returns empty on object map - The object map breaks when an application does not have an instance bound to it.

  • Shipa-715 Dashboard application map fails to load - The Dashboard application map fails to load due to API/network-policy.

  • Shipa-704 Volume plan details do not show volumes - Volumes are not displayed on the “volume plan details” UI page.

  • Application Build & Deployment Pipeline

  • Shipa-652 Buildkit can’t get manifest when building a Golang image - Not deploying Golang application using Buildkit.

  • Shipa-655 Application bigger than 1MB in size fails during deployment - Limitations on 1MB size during deployment was happening due to the’ devtools’ proxy used to run Shipa locally.

  • Shipa-651 Node distributions chart shows “undefined” when using minikube - Using Shipa on Minikube, the dashboard page displays an error in the node distribution chart and categorizes the available node as “undefined” instead of ‘others.’

  • Shipa-693 SHIPA_TARGET env variable overrides current target - On Shipa CLI, the target command uses “SHIPA-TARGET” as the current target, overriding the correct target set by the user.

  • Shipa-702 Artifactory applications fail during deployment - When using a private image, the deployment from artifactory does not work.

  • Shipa-718 ENV in Docker file doesn’t work

  • Shipa-725 Deployment from source

  • Shipa-726 Enable to deploy an application with a static HTML file

  • Shipa-780 Fix CLI version in docker image - With each tagged version of shipa CLI, the docker image should print the intended version instead of the “dev” default version.

  • Shipa-797 Unite Test - App Create/Update test files failing on Travis - Test is falling in the CI, RTL is finding several elements with the same ID or TEXT.


  • Shipa-873 Shipa fails to deploy on EKS.
  • Shipa-703 Bugs after uninstalling Helm chart - After uninstalling Helm and installing again, bugs with permission issues were found.


  • Shipa-588 Application Deployment failures on REST API - When deploying REST API applications, there is a consistent failure in the API and inaccurate response code.
  • Shipa-759 App deploys events are not getting listed on the Shipa event list - Events that don’t contain an organization name set were not getting reported through events API, not listed in the front-end or event list.

Traffic Management

  • Shipa-677 CNAME validation issue - The address generated with Shipa CNAME for HTTPS was not valid, required validation.
  • Shipa-690 Remove CNAME does not work - CNAME has not been removed after requested, and application info was still showing the CNAME.

Nodes & Cluster

  • Shipa-716 Creating application fails - When attaching a cluster, the app creating does not work, resulting in failure
  • Shipa-733 Unauthorized error when accessing an application deployed to an attached cluster - Applications deployed to an attached cluster is accessible through its URL. However, it can’t be accessible using Shipa CLI or the Dashboard UI; attempting to access it results in an unauthorized error.
  • Shipa-739 Application deployment fails after adding a pool to the “shipa-corp” cluster - When creating a new pool and adding to the “shipa-core” cluster, app deployment starts to fail.
  • Shipa-767 Lack of synchronization between Shipa application status and Kubernetes - While Shipa was exhibiting application status as “running,” on Kubernetes, the same application was not working.
  • Shipa-614 Issue when adding multiple pools to a single cluster - Shipa did not create different namespaces for each pool, compromising the application creation on those pools.


  • Shipa-610 Application name should not be globally scoped - Application name has to be defined at the organization or pool level.
  • Shipa-611 Application deployment failing at organization level - Not able to deploy applications using public docker image for a new organization with permission (AllowAllOrg).
  • Shipa-732 No ID value to “default organization.”- When creating a new organization in Shipa, this organization has an ID value associated with it. However, a default organization has no ID value.
  • Shipa-770 Unable to retrieve application metrics - Package exporter fails to retrieve application metrics when organizations contain hyphenation in their name.


  • Shipa-793 Behavior issue during service install - The service install process starts but right after disappears without showing any error message.
  • Shipa-598 Issue using Azure PostgreSQL - Not creating an instance using the Azure managed PostgreSQL services on Shipa.

Known Behavior

This section lists known limitations with this release.

Shipa-907 Broken connection during cluster update - Cluster update command restarts Traefik, leading to a broken connection.

Shipa-927 Application deployment from source code using the API does not work properly -
The behavior results in a silenced error; deployment from source code does not work from the Dashboard.

Shipa-834 Removing a pool using Shipa, does not remove the namespace in the cluster

Shipa-860 User in new "org" with the right set permission, are not able to deploy apps on default cluster

Shipa-916 Shipa CLI's not returning an error if more that one team or pool specified during "app create"