Skip to content

Application Developer Overview

We know software developers are busy people that want to get up and running as soon as possible!

Use the navigational bar to the side to jump to the section that interests you the most.

Getting started quickly

Welkin is a Kubernetes distribution that consists of the best (community-driven) open source components in the cloud native space, configured for security and platform stability. It does not contain any proprietary technology, and no vendor-specific tooling, such as command-line tools or abstractions that only work in this distribution. To the greatest extent possible, all technology contained within the distribution is community-driven open source, as in, not under a single vendor's control or governance. The distribution is itself open source, and is also designed and developed in a transparent manner (see our Architectural Decision Records).

Your administrator has already set up the platform for you. You will therefore have received:

  • URLs for the Service Endpoints: OpenSearch Dashboards, Grafana, and Harbor;
  • a kubeconfig file for configuring kubectl or Lens access to the Workload Cluster; and
  • (optionally and rarely) a static username and password. Note that normally, you should log in via a username and a password of your organization's Identity Provider, such as LDAP, Azure Active Directory, or Google Identity.

Install Prerequisite Software

Required software:

  • oidc-login, which helps you log into your Kubernetes cluster via OpenID Connect integration with your Identity Provider of choice

Your cluster management software of choice, of which you can choose either or both:

Optional, but very useful, tools for developers and DevOps engineers:

  • docker, if you want to build (Docker) container images locally
  • Helm, if you want to manage your application with the Helm package manager
You can verify that configuration is correct by issuing the following simple commands

Make sure you have configured your tools properly:

export KUBECONFIG=path/of/kubeconfig.yaml  # leave empty if you use the default of ~/.kube/config
export DOMAIN=  # the domain you received from the administrator

To verify if the required tools are installed and work as expected, type:

docker version
kubectl version  --client
helm version
# You should see the version number of installed tools and no errors.

To verify the received KUBECONFIG, type:

# Notice that you will be asked to complete browser-based single sign-on
kubectl get nodes
# You should see the Nodes of your Kubernetes cluster

To verify the received URLs, type:

curl --head https://dex.$DOMAIN/healthz
curl --head https://harbor.$DOMAIN/healthz
curl --head https://grafana.$DOMAIN/healthz
curl --head https://opensearch.$DOMAIN/api/status
curl --insecure --head https://app.$DOMAIN/healthz  # Ingress Controller
# All commands above should return 'HTTP/2 200'

Endpoint access

Those URLs that your Welkin administrator gave you all have a $DOMAIN, which will typically include your company name and perhaps the environment name.

Your web portals are available at:

  • harbor.$DOMAIN -- the Harbor container image registry, which will be the home to all your container images
  • opensearch.$DOMAIN -- the OpenSearch Dashboards portal, where you will view your application and audit logs
  • grafana.$DOMAIN -- the Grafana portal, where you will view your monitoring metrics for both the platform, as such, and your application-specific metrics

Additional endpoints are also available, depending on if your platform has these additional managed services (AMS) or not:

  • jaeger.$DOMAIN -- the Jaeger distributed tracing observability tool
  • argocd.$DOMAIN -- the Argo CD continuous deployment GitOps tool

Finding more information

If you are not familiar with Kubernetes since before, following our three-step process is a good idea, which includes a demo application for you to deploy and understand the entire process of containerizing an application and how to deploy it.

  1. The first step is about making necessary preparations such as installing prerequisite software on your laptop.
  2. The second step is about deploying your software.
  3. The third step is about how you continuously operate the software.

It may be a good idea to follow along in all of these, even if you have worked with similar systems before.

If you are familiar with similar systems, a common next step for Application Developers that are already used to Kubernetes is to read up on the safeguards that Welkin ships with. You may also wish to use the "Go Deeper" link in the site's navigational bar to find more information about specific topics, such as: