In some cases, a resource cannot be deleted in Kubernetes (K8S), and it will remain stuck in terminating state.

The steps to solve this problem are:

kubefwd

kubefwd is a command line utility built to port forward multiple services within one or more namespaces on one or more Kubernetes clusters. kubefwd uses the same port exposed by the service and forwards it from a loopback IP address on your local workstation. kubefwd temporally adds domain entries to your /etc/hosts file with the service names it forwards.

kubefwd helps to enable a seamless and efficient way to develop applications and services on a local workstation. Locally develop applications that intend to interact with other services in a Kubernetes cluster. kubefwd allows applications with connection strings like http://elasticsearch:9200/ or tcp://db:3306 to communicate into the remote cluster. kubefwd can be used to reduce or eliminate the need for local environment specific connection configurations.

Rancher

Rancher is a complete container management platform for Kubernetes, giving you the tools to successfully run Kubernetes anywhere.

Rancher can provision Kubernetes from a hosted provider, provision compute nodes and then install Kubernetes onto them, or import existing Kubernetes clusters running anywhere.

One Rancher server installation can manage thousands of Kubernetes clusters and thousands of nodes from the same user interface.

Rancher adds significant value on top of Kubernetes, first by centralizing authentication and role-based access control (RBAC) for all of the clusters, giving global admins the ability to control cluster access from one location.

It then enables detailed monitoring and alerting for clusters and their resources, ships logs to external providers, and integrates directly with Helm via the Application Catalog. If you have an external CI/CD system, you can plug it into Rancher, but if you don’t, Rancher even includes a pipeline engine to help you automatically deploy and upgrade workloads.

This article is about how to use Helm to deploy Rancher on Kubernetes (K8S).

Rancher Labs Longhorn

Longhorn is a lightweight, reliable and easy-to-use Cloud native distributed block storage system for Kubernetes.

kubernetes-dashboard

kubernetes-dashboard is a general purpose, web-based UI for Kubernetes clusters. It allows users to manage applications running in the cluster and troubleshoot them, as well as manage the cluster itself.

This article is about how to use Helm to deploy kubernetes-dashboard on Kubernetes (K8S).

helm-ingress-nginx-example

ingress-nginx is an Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer.

You can modify it and use ingress-nginx. There is some examplesabout installing it with Helm in the article.

hexo-theme-next

NexT is a high quality elegant theme for Hexo. It is crafted from scratch, with love.

Make sure that you have installed Hexo and created a site(such as hexo-site) with it successfully, because the following documents require you to operate in the site root directory.

Prerequisites

• Hexo - https://hexo.io/

  Hexo is a fast, simple & powerful blog framework. It use plugins to provide features powerful APIs for limitless extensibility. Various plugins are available to support most template engines (EJS, Pug, Nunjucks, and many others). Easily integrate with existing NPM packages (Babel, PostCSS, Less/Sass, etc).

  To learn more about all the features of Docker, see Hexo - https://hexo.io/.

Installation

Open your Terminal, change to Hexo site root directory and install NexT theme:

1
2
3
4
5

$ cd hexo-site

$ npm install hexo-theme-next

$ hexo clean

Configuration

Config Next Theme

At present, NexT encourages users to use the Alternate Theme Config. It’s a feature of Hexo and the documentation is here: Configuration | Hexo - https://hexo.io/docs/configuration.html#Using-an-Alternate-Config.

1
2

# Installed through npm
$ cp node_modules/hexo-theme-next/_config.yml _config.next.yml

The traditional approach is to store some options in site config file and other options in theme config file. But it is not smooth to update NexT theme from pulling or downloading new releases.

1
2

# Installed through Git
$ cp theme/next/_config.yml _config.next.yml

Configuration | NexT - https://theme-next.js.org/docs/getting-started/configuration.html

Enabling NexT

Like all Hexo themes, after you download it, open site config file, find theme section, and change its value to next (or another theme directory name).

1
2
3

# hexo/_config.yml

theme: next

Now you have installed NexT theme and enabled it. The following steps will help you verify whether NexT is enabled correctly.

Run

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

$ hexo s
INFO  Validating config
INFO  ==================================
  ███╗   ██╗███████╗██╗  ██╗████████╗
  ████╗  ██║██╔════╝╚██╗██╔╝╚══██╔══╝
  ██╔██╗ ██║█████╗   ╚███╔╝    ██║
  ██║╚██╗██║██╔══╝   ██╔██╗    ██║
  ██║ ╚████║███████╗██╔╝ ██╗   ██║
  ╚═╝  ╚═══╝╚══════╝╚═╝  ╚═╝   ╚═╝
========================================
NexT version 8.2.1
Documentation: https://theme-next.js.org
========================================
INFO  Start processing
INFO  Hexo is running at http://localhost:4000 . Press Ctrl+C to stop.

Now you can open http://localhost:4000 in your browser, and check whether the site works correctly.

References

[1] NexT - Theme for Hexo - https://theme-next.js.org/

[2] Getting Started | NexT - https://theme-next.js.org/docs/getting-started/

[3] Configuration | Hexo - https://hexo.io/docs/configuration.html#Using-an-Alternate-Config

[4] Hexo - https://hexo.io/

helm-dnspod-webhook-cert-manager-example

dnspod-webhook-cert-manager is a cert-manager plugin to manage SSL certificates on Kubernetes.

Along with Nginx Ingress, you can configure HTTPS access to the website. With Let’s Encrypt provide free SSL certificates, all the free packs of cert-manager + Nginx Ingress + Let’s Encrypt are automatic generated. But cert-manager does not support dnspod by default.

You can modify it and use dnspod-webhook-cert-manager. There is some examplesabout installing it with Helm in the article.

GitLab Runner

GitLab Runner is an application that works with GitLab CI/CD to run jobs in a pipeline.

GitLab Runner has the following features.

• Run multiple jobs concurrently.

• Use multiple tokens with multiple servers (even per-project).

• Limit the number of concurrent jobs per-token.

• Jobs can be run:

  • Locally.

  • Using Docker containers.

  • Using Docker containers and executing job over SSH.

  • Using Docker containers with autoscaling on different clouds and virtualization hypervisors.

  • Connecting to a remote SSH server.

• Is written in Go and distributed as single binary without any other requirements.

• Supports Bash and Windows PowerShell.

• Works on GNU/Linux, macOS, and Windows (pretty much anywhere you can run Docker).

• Allows customization of the job running environment.

• Automatic configuration reload without restart.

• Easy to use setup with support for Docker, Docker-SSH, Parallels, or SSH running environments.

• Enables caching of Docker containers.

• Easy installation as a service for GNU/Linux, macOS, and Windows.

• Embedded Prometheus metrics HTTP server.

• Referee workers to monitor and pass Prometheus metrics and other job-specific data to GitLab.

This article is about how to use Helm to deploy GitLab Runner on Kubernetes (K8S).

GitLab

GitLab is an open source end-to-end software development platform with built-in version control, issue tracking, code review, CI/CD, and more. Self-host GitLab on your own servers, in a container, or on a cloud provider.

GitLab is a fully integrated software development platform that enables your team to be transparent, fast, effective, and cohesive from discussion on a new idea to production, all on the same platform.

GitLab is a Git-based platform that integrates a great number of essential tools for software development and deployment, and project management:

• Hosting code in repositories with version control.

• Tracking proposals for new implementations, bug reports, and feedback with a fully featured Issue Tracker.

• Organizing and prioritizing with Issue Boards.

• Reviewing code in Merge Requests with live-preview changes per branch with Review Apps.

• Building, testing, and deploying with built-in Continuous Integration.

• Deploying personal and professional static websites with GitLab Pages.

• Integrating with Docker by using GitLab Container Registry.

• Tracking the development lifecycle by using GitLab Value Stream Analytics.

• Provide support with Service Desk.

• Export issues as CSV.

This article is about how to use Helm to deploy GitLab on Kubernetes (K8S).