Explore all topics

Networking

Explore all libraries in Networking

Explore Kits

Explore all topics

Networking

Explore all libraries in Networking

This is related to Networking

Explore Related Topics

Popular New Releases in Networking

frp

v0.41.0

shadowsocks-windows

4.4.1.0

requests

v2.27.1

react-router

v2ray-core

v4.31.0

frp

v0.41.0

shadowsocks-windows

4.4.1.0

requests

v2.27.1

react-router

v2ray-core

v4.31.0

Popular Libraries in Networking

frp

by fatedier go

55464 Apache-2.0

A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.

shadowsocks-windows

by shadowsocks csharp

53806 GPL-3.0

A C# port of shadowsocks

requests

by psf python

47177 Apache-2.0

A simple, yet elegant, HTTP library.

react-router

by remix-run typescript

46674 MIT

Declarative routing for React

react-router

by ReactTraining javascript

43698 MIT

Declarative routing for React

okhttp

by square kotlin

41993 Apache-2.0

Square’s meticulous HTTP client for the JVM, Android, and GraalVM.

v2ray-core

by v2ray go

39387 MIT

A platform for building proxies to bypass network restrictions.

caddy

by caddyserver go

39075 Apache-2.0

Fast, multi-platform web server with automatic HTTPS

Alamofire

by Alamofire swift

37489 MIT

Elegant HTTP Networking in Swift

frp

by fatedier go

55464 Apache-2.0

A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.

shadowsocks-windows

by shadowsocks csharp

53806 GPL-3.0

A C# port of shadowsocks

requests

by psf python

47177 Apache-2.0

A simple, yet elegant, HTTP library.

react-router

by remix-run typescript

46674 MIT

Declarative routing for React

react-router

by ReactTraining javascript

43698 MIT

Declarative routing for React

okhttp

by square kotlin

41993 Apache-2.0

Square’s meticulous HTTP client for the JVM, Android, and GraalVM.

v2ray-core

by v2ray go

39387 MIT

A platform for building proxies to bypass network restrictions.

caddy

by caddyserver go

39075 Apache-2.0

Fast, multi-platform web server with automatic HTTPS

Alamofire

by Alamofire swift

37489 MIT

Elegant HTTP Networking in Swift

Explore all libraries in Networking

Trending New libraries in Networking

Xray-core

by XTLS go

8099 MPL-2.0

Xray, Penetrates Everything. Also the best v2ray-core, with XTLS support. Fully compatible configuration.

Open-IM-Server

by OpenIMSDK go

7570 Apache-2.0

OpenIM: Instant messaging open source project based on go built by IM technology experts. Backend in Go.（由IM技术专家打造的基于 Go 实现的即时通讯（IM）项目，从服务端到客户端SDK开源即时通讯（IM）整体解决方案，可以轻松替代第三方IM云服务，打造具备聊天、社交功能的app。）

workflow

by sogou c++

7431 Apache-2.0

Parallel Computing and Asynchronous Networking Engine ⭐️⭐️⭐️

tailscale

by tailscale go

7241 NOASSERTION

The easiest, most secure way to use WireGuard and 2FA.

itlwm

by OpenIntelWireless c

5394 NOASSERTION

Intel Wi-Fi Drivers for macOS

reverse-proxy

by microsoft csharp

5209 MIT

A toolkit for developing high-performance HTTP reverse proxy applications.

axum

by tokio-rs rust

4413 MIT

Ergonomic and modular web framework built with Tokio, Tower, and Hyper

trojan-go

by p4gefau1t go

4281 GPL-3.0

Go实现的Trojan代理，支持多路复用/路由功能/CDN中转/Shadowsocks混淆插件，多平台，无依赖。A Trojan proxy written in Go. An unidentifiable mechanism that helps you bypass GFW. https://p4gefau1t.github.io/trojan-go/

server

by screego go

4189 GPL-3.0

screen sharing for developers https://screego.net/

Xray-core

by XTLS go

8099 MPL-2.0

Xray, Penetrates Everything. Also the best v2ray-core, with XTLS support. Fully compatible configuration.

Open-IM-Server

by OpenIMSDK go

7570 Apache-2.0

workflow

by sogou c++

7431 Apache-2.0

Parallel Computing and Asynchronous Networking Engine ⭐️⭐️⭐️

tailscale

by tailscale go

7241 NOASSERTION

The easiest, most secure way to use WireGuard and 2FA.

itlwm

by OpenIntelWireless c

5394 NOASSERTION

Intel Wi-Fi Drivers for macOS

reverse-proxy

by microsoft csharp

5209 MIT

A toolkit for developing high-performance HTTP reverse proxy applications.

axum

by tokio-rs rust

4413 MIT

Ergonomic and modular web framework built with Tokio, Tower, and Hyper

trojan-go

by p4gefau1t go

4281 GPL-3.0

server

by screego go

4189 GPL-3.0

screen sharing for developers https://screego.net/

Top Authors in Networking

mafintosh

64 Libraries

5208

libp2p

46 Libraries

7050

google

45 Libraries

25552

microsoft

33 Libraries

18854

apache

32 Libraries

8941

hrbrmstr

29 Libraries

194

sindresorhus

28 Libraries

22582

substack

27 Libraries

3270

PacktPublishing

24 Libraries

384

NordicSemiconductor

23 Libraries

2136

mafintosh

64 Libraries

5208

libp2p

46 Libraries

7050

google

45 Libraries

25552

microsoft

33 Libraries

18854

apache

32 Libraries

8941

hrbrmstr

29 Libraries

194

sindresorhus

28 Libraries

22582

substack

27 Libraries

3270

PacktPublishing

24 Libraries

384

NordicSemiconductor

23 Libraries

2136

Trending Kits in Networking

25 Best Java Encryption Libraries for 2023

Enable security functions like password encryption, digital signatures, secure random number generation, message authentication, Two Factor Authentication (2FA), and more with Java encryption libraries.

Encryption, decryption, and key generation are the three most crucial aspects of Java cryptography. Key-based data security can be enabled in two ways, using symmetric or asymmetric encryption algorithms, considering how secure the code needs to be. Moreover, developers can easily enable security functions directly into the code with the set of APIs available in the Java Cryptography Architecture (JCA). The JCA is the core of java encryption and decryption, hashing, secure random, and various other java cryptographic functions.

Check out the below list to find more trending Java encryption libraries for your applications:

Developers generally use java crypto libraries like Google Tink that help both encrypt and decrypt the data through simple and secure APIs.

Bouncy Castle is a popular Java cryptographic library that is used by developers to perform basic operations, such as encryption and digital signature.

Frequently used with Bouncy Castle, the Jasypt library helps enable basic encryption functions even if you don’t have deep cryptography know-how.

App Store Payment Alternatives

Judge Yvonne Gonzalez Rogers ordered that iOS apps must be allowed to support non Apple payment options in the Epic v. Apple case. In this case, Apple also scored a partial victory as the judge stopped short of calling it a monopoly. The judge also ordered Epic Games to pay Apple 30% of its revenue through the direct payment system. Epic is fighting a similar lawsuit against Google. Countries like South Korea have passed laws requiring Apple and Google to offer alternative payment systems to their users in the country. While the jury is still out on the Epic v. Apple case, it brings out two aspects. Is what is often referred to by developers as the "Apple Tax" of 30% indeed justified? For this reason, Epic launched the Epic Games Store to demonstrate that they could operate at a lower revenue cut of 12%. The second aspect is platform and payments interoperability. When platform interoperability becomes mandated or a global best practice, developers should be ready to bring in payment gateways of their choice. The kandi kit for App Store Payment Alternatives showcases the popular open source payment gateways such as Omnipay, Active Merchant, and CI Merchant and libraries available to connect with leading payment platforms such as Stripe, Braintree, and Razorpay.

Omnipay

Core libraries and samples from Omnipay, a framework agnostic, multi-gateway payment processing library for PHP.

Active Merchant

Libraries on Active Merchant, a simple payment abstraction library extracted from Shopify.

CI Merchant

Though no longer actively supported use the library to build and support your own gateway. If you are not looking to build but to use, then leverage other frameworks.

Braintree

Libraries for Braintree integration.

Razorpay

Libraries for Razorpay integration.

Stripe

Libraries for Stripe integration.

Web scraping automation with Python

Build smart application to collect and scrap data from a variety of online sources using these open-source data scrapping libraries.

In today’s world, we are surrounded loads of data of different types and from diverse sources. And every business organisation wants to make the best use of this data. The ability to gather and utilise this data is a must-have skill for every data scientist.

Web scraping is the process of extracting structured and unstructured data from the web with the help of programs and exporting into a useful format. You can efficiently use the Python language to build application to harvest online data through these specific Python libraries.

The following list covers the top and trending libraries for web data scrapping. By clicking on each you can check out the overview, code examples, best applications and cases for each of them, and a lot more. Scroll through:

Working with HTTP to request a web page

Complete web scraping framework

Parsing HTML, XML

23 best C# Networking

Network programming is a complex and difficult task, so it's not surprising that many developers are looking for C# Networking libraries to help them with this task. While working with network protocols such as TCP/IP, UDP or HTTP, there are a lot of details that are hard to get right. Luckily, there are some excellent open-source C# libraries available that can make your life easier when you're working with these protocols. DotNetty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. Protobuf-net is a .NET library that allows serialization and deserialization of structured data into Protocol Buffers format. The project includes both a library (for serializing objects) as well as a command line tool (for generating code from schema definition files). They all provide support for multiple platforms, easy to use and have good documentation. Build enhanced networking configurations, protocols and performance optimizations in C# using these 23 libraries:

28 best JavaScript Button libraries

Buttons are essentially the drivers of online interaction as we use them to login into our emails, add products to our shopping carts, download photos and basically confirm any and all actions. But more than that, every button click is a successful conclusion of every front-end web developer’s hard work. That’s why it is crucial to spend time creating functional buttons that both look beautiful and provide visual cues to the user. JavaScript offers a ton of great button libraries for you to choose your essential UI components from. Here are some of the JavaScript libraries for buttons including Semantic-UI - UI component framework based around useful principles; Buttons - A CSS button library built using Sass and Compass; Ladda - Buttons with built-in loading indicators. The following is a comprehensive list of the best open-source JavaScript Button libraries in 2022

Highly Secured WiFi Router

A router connects your home computers to a local area network (LAN). It then routes packets intended for the Internet (email, web, etc.) through your router to your ISP's (Internet Service Provider) actual connection to the big bad Internet. This project came to life from a personal interest in hardware embedded design and software design in Linux with PHP. The main aim is to build a highly secure Wi-Fi Router out of a Raspberry Pi, easily configurable via a dynamic UI designed in HTML/PHP.

Status Indicators

Security

Authenticator and Router

Analyzer

WI-FI Routing

Opensource Social Platforms

The Trump Media and Technology Group is being investigated by Software Freedom Conservancy for non-compliance with copyleft licensing. The issue stems from President Donald Trump’s new social network, Truth Social appearing to be forked from Mastodon. While Mastodon is open source and available to use, it is licensed under Affero General Public License (or AGPLv3) that requires The Trump Media and Technology Group to share its source code with all who used the site. If they fail to do this within 30 days, their rights and permissions in the software are automatically and permanently terminated, making their platform inoperable. So if you are just a developer or a former POTUS, copyleft provisions apply to all. If you want to use open source, use kandi.openweaver.com. All libraries are matched to SPDX license definitions and highlighted clearly for appropriate use. Privacy, regulation, bias, and many other issues are weighing down popular social networks. Users are seeking self-hosted social platforms that can be governed by themselves. But do use them with the appropriate licenses. The kandi kit on Opensource Social Platforms lists popular opensource libraries that you can use to host private social channels.

WiFi And Bluetooth Tracking

Bluetooth and Wi-Fi are the essential communication medium in the internet world. Bluetooth and Wi-Fi are used to provide wireless communication. Bluetooth allows us to share data, files, voice, music, video, and a lot of information between paired devices. Bluetooth and Wi-Fi provide tracking facility also. If we lose the gadgets and want to track that gadget or track a particular person, we can track them with the help of Bluetooth and Wi-Fi. Bluetooth and Wi-Fi tracking play a vital role in tracking the lost gadgets or a person. Following libraries can help you to perform Bluetooth and Wi-Fi tracking

15 best Ruby Server Side Scripting

Build enhanced server side scripting for various usecases in Ruby for your application.Get ratings, code snippets & documentation for each library.

Ping Pong Video Game

One of the most phenomenal online games ruling the young generation is Ping-pong, which is supposed to be the world's best brain game. Ping-pong is a Racquet sport, an indoor game, is highly organized as a competitive sport in most countries, especially in Europe and Asia. Ping-pong is also known as table tennis, similar in principle to lawn tennis. Playing ping-pong improves hand-eye coordination, burns calories, keeps our brain sharp. Python is preferable for building Ping-pong game; the reason behind that is python is free and open-source, with vast library support. Let's build your own Ping-pong game with the help of the bellow libraries. Following are the steps to be followed for building the 3D Tron Clone Game, 1. Development Environment For Creating Game 2. Control Ball And Create Panel 3. Track Result And Skill 4. Multiplayer Support 5. Background Music 6. Java Library For Creating Paddle, Ball, and Scoring System 7. C++ And java Libraries For Develop Ping Pong 8. Python Libraries For Develop Ping Pong 9. Typescript, JavaScript, PHP Libraries For Develop Ping Pong 10. Go Library For Develop Ping Pong

Development Environment For Creating Game

These reusable libraries are game development platform libraries. These libraries provide the 2D,3D game support.

Control Ball And Create Panel

The reusable libraries are used to 3D scene editor, animation, screenshot, background music, control a ball, create a panel, track the ball, and create the one-player mode.

Track Result And Skill

These libraries are used to track your game result and give an accurate skill rating.

Multiplayer Support

These libraries are used for multiplayer in game.

Background Music

These libraries provide the background music, sound effects, animation for the game.

java Library for Creating Paddle , Ball And Scoring System

This library is used to build the game window and initialize the game loop, creating the paddle with keyword, bouncing the ball back when it collides with the paddle, and also provide the scoring system for game.

C++ And java Libraries for Develop Ping Pong

The first two libraries are used for tuning and Ping-pong, usually fixed user-generated positions. Also able to combine positions.

Python Libraries For Develop Ping Pong

These libraries are used to move the ball from the two possible ways here up and down. And also, using these libraries create the ping pong game using python libraries.

Go Library For Develop Ping Pong

These library is used to create the game using go language.

Typescript , JavaScript , PHP Libraries For Develop Ping Pong

They have different libraries based on the language all these libraries also used to create the ping pong game.

Python Encryption and Security Libraries

Python encryption libraries are useful for enabling surety function in your applications such as encryption, key generation, message authentication, key agreement, etc.

Encryption is a challenging task in web and application development. And a reliable open-source Python encryption library can make the job easier. Basically, there are two types of encryption algorithms, viz., Symmetric and Asymmetric.

For instance, if you need to store or secure a password, it can be useful to implement a strong cryptographic hashing algorithm. On the other hand, for encrypting something like credit card details, you can employ the Advanced Encryption Standard. AES is a symmetric-key algorithm, which is most preferred by the US federal organizations.

There are various Python libraries that can help both encrypt and decrypt the data. Check out the below list to find more top Python encryption libraries for your applications:

10 Best PHP FTP

One of the most common tasks in web development is transferring files and folders to and from a server. PHP provides a number of FTP libraries that make this task easy. PHP supports FTP (File Transfer Protocol) with the help of an FTP library. OpenMediaVault is a free Linux distribution designed to run Network Attached Storage (NAS) systems. It's based on Debian and is freely available under a GPLv2 license. One of the best things about OpenMediaVault is its user interface which makes it easy to set up and manage your networked storage devices. TinUFileManager is an easy-to-use file manager for your PHP web applications. It supports multiple languages like Spanish, Catalan, Portuguese, French, German, and more! This library also comes with an authentication system which makes it easy to manage users/groups and their permissions through a simple interface. The PHP FTP Client library provides an easy way to connect to any FTP server from within your PHP scripts without having to worry about writing complex code or dealing with any low-level sockets yourself! Developers tend to use some of the following open source PHP FTP libraries are given below

48 best Java Cryptocurrency

Java Cryptocurrency libraries mostly work with the Bitcoin protocol to maintain a wallet and send or receive cryptocurrency transactions without storing a local copy of the Bitcoin core. One such library is bitcoinj. These open-source libraries have many advanced features implemented in Java and can be used by any JVM-compatible programming language, like Python. With these libraries, you can create components for building Bitcoin, Ethereum, Altcoin, Litecoin, and other such popular crypotocurrencies. You can also create and maintain the bitcoin wallet, integrate with popular crypto-exchanges, enable automated trading, and so on. You can use these to incorporate blockchain into a Java project, create wallets, and manage transactions between nodes, often without having to write your own integration code.

Below is our list of the 48 best Java cryptocurrency libraries that are open-source in 2021. XChange is a Java library of streamlined APIs for interaction with more than 60 Bitcoin and Altcoin exchanges. It has an MIT license and modular components with minimal dependency on third-party applications. Another library, bitcoin-wallet, is a wallet app for your Android device that works as a standalone Bitcoin payment platform with no centralized backend requirement. With this, you can integrate Bitcoin payments into your Android app. On the other hand, Best is an Apache 2.0 licensed enterprise-grade Ethereum client that is Java-based and MainNet compatible. Depending on your requirements, you can choose any of these open-source libraries for your project.

Wireless Camera Forest Survey

The hunting of animals has led to a decrease in their populations. Continuous hunting has a led a lot of animal species to go into extinction. Governments and scientists around the world have taken this into attention and started introducing a few laws by conducting a few surveys. Conducting surveys is a complicated task, especially without the help of technology. Some of these libraries can help you create customized forest survey applications.

25 Best Java Encryption Libraries for 2023

Check out the below list to find more trending Java encryption libraries for your applications:

Developers generally use java crypto libraries like Google Tink that help both encrypt and decrypt the data through simple and secure APIs.

Bouncy Castle is a popular Java cryptographic library that is used by developers to perform basic operations, such as encryption and digital signature.

Frequently used with Bouncy Castle, the Jasypt library helps enable basic encryption functions even if you don’t have deep cryptography know-how.

App Store Payment Alternatives

Omnipay

Core libraries and samples from Omnipay, a framework agnostic, multi-gateway payment processing library for PHP.

Active Merchant

Libraries on Active Merchant, a simple payment abstraction library extracted from Shopify.

CI Merchant

Though no longer actively supported use the library to build and support your own gateway. If you are not looking to build but to use, then leverage other frameworks.

Braintree

Libraries for Braintree integration.

Razorpay

Libraries for Razorpay integration.

Stripe

Libraries for Stripe integration.

Web scraping automation with Python

Build smart application to collect and scrap data from a variety of online sources using these open-source data scrapping libraries.

Working with HTTP to request a web page

Complete web scraping framework

Parsing HTML, XML

23 best C# Networking

28 best JavaScript Button libraries

Highly Secured WiFi Router

Status Indicators

Security

Authenticator and Router

Analyzer

WI-FI Routing

Opensource Social Platforms

WiFi And Bluetooth Tracking

15 best Ruby Server Side Scripting

Build enhanced server side scripting for various usecases in Ruby for your application.Get ratings, code snippets & documentation for each library.

Ping Pong Video Game

Development Environment For Creating Game

These reusable libraries are game development platform libraries. These libraries provide the 2D,3D game support.

Control Ball And Create Panel

The reusable libraries are used to 3D scene editor, animation, screenshot, background music, control a ball, create a panel, track the ball, and create the one-player mode.

Track Result And Skill

These libraries are used to track your game result and give an accurate skill rating.

Multiplayer Support

These libraries are used for multiplayer in game.

Background Music

These libraries provide the background music, sound effects, animation for the game.

java Library for Creating Paddle , Ball And Scoring System

C++ And java Libraries for Develop Ping Pong

The first two libraries are used for tuning and Ping-pong, usually fixed user-generated positions. Also able to combine positions.

Python Libraries For Develop Ping Pong

These libraries are used to move the ball from the two possible ways here up and down. And also, using these libraries create the ping pong game using python libraries.

Go Library For Develop Ping Pong

These library is used to create the game using go language.

Typescript , JavaScript , PHP Libraries For Develop Ping Pong

They have different libraries based on the language all these libraries also used to create the ping pong game.

Python Encryption and Security Libraries

Python encryption libraries are useful for enabling surety function in your applications such as encryption, key generation, message authentication, key agreement, etc.

There are various Python libraries that can help both encrypt and decrypt the data. Check out the below list to find more top Python encryption libraries for your applications:

10 Best PHP FTP

48 best Java Cryptocurrency

Wireless Camera Forest Survey

More kits in Networking

Trending Discussions on Networking

Microk8s dashboard using nginx-ingress via http not working (Error: `no matches for kind "Ingress" in version "extensions/v1beta1"`)

Laravel Homestead - page stopped working ERR_ADDRESS_UNREACHABLE

Accessing PostgreSQL (on wsl2) from DBeaver (on Windows) fails: "Connection refused: connect"

Why URL re-writing is not working when I do not use slash at the end?

Standard compliant host to network endianess conversion

How to configure proxy in emulators in new versions of Android Studio?

Unable to log egress traffic HTTP requests with the istio-proxy

Dynamodb local web shell does not load

Cancelling an async/await Network Request

How to configure GKE Autopilot w/Envoy & gRPC-Web

QUESTION

Microk8s dashboard using nginx-ingress via http not working (Error: `no matches for kind "Ingress" in version "extensions/v1beta1"`)

Asked 2022-Apr-01 at 07:26

I have microk8s v1.22.2 running on Ubuntu 20.04.3 LTS.

Output from /etc/hosts:

1127.0.0.1 localhost
2127.0.1.1 main
3

Excerpt from microk8s status:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9

I checked for the running dashboard (kubectl get all --all-namespaces):

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39

I want to expose the microk8s dashboard within my local network to access it through http://main/dashboard/

To do so, I did the following nano ingress.yaml:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56

Enabling the ingress-config through kubectl apply -f ingress.yaml gave the following error:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
57

Help would be much appreciated, thanks!

Update: @harsh-manvar pointed out a mismatch in the config version. I have rewritten ingress.yaml to a very stripped down version:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
57apiVersion: networking.k8s.io/v1
58kind: Ingress
59metadata:
60  name: dashboard
61  namespace: kube-system
62spec:
63  rules:
64  - http:
65      paths:
66      - path: /dashboard
67        pathType: Prefix
68        backend:
69          service:
70            name: kubernetes-dashboard
71            port:
72              number: 443
73

Applying this works. Also, the ingress rule gets created.

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
57apiVersion: networking.k8s.io/v1
58kind: Ingress
59metadata:
60  name: dashboard
61  namespace: kube-system
62spec:
63  rules:
64  - http:
65      paths:
66      - path: /dashboard
67        pathType: Prefix
68        backend:
69          service:
70            name: kubernetes-dashboard
71            port:
72              number: 443
73NAMESPACE     NAME        CLASS    HOSTS   ADDRESS     PORTS   AGE
74kube-system   dashboard   public   *       127.0.0.1   80      11m
75

However, when I access the dashboard through http://<ip-of-kubernetes-master>/dashboard, I get a 400 error.

Log from the ingress controller:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
57apiVersion: networking.k8s.io/v1
58kind: Ingress
59metadata:
60  name: dashboard
61  namespace: kube-system
62spec:
63  rules:
64  - http:
65      paths:
66      - path: /dashboard
67        pathType: Prefix
68        backend:
69          service:
70            name: kubernetes-dashboard
71            port:
72              number: 443
73NAMESPACE     NAME        CLASS    HOSTS   ADDRESS     PORTS   AGE
74kube-system   dashboard   public   *       127.0.0.1   80      11m
75192.168.0.123 - - [10/Oct/2021:21:38:47 +0000] &quot;GET /dashboard HTTP/1.1&quot; 400 54 &quot;-&quot; &quot;Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36&quot; 466 0.002 [kube-system-kubernetes-dashboard-443] [] 10.1.76.3:8443 48 0.000 400 ca0946230759edfbaaf9d94f3d5c959a
76

Does the dashboard also need to be exposed using the microk8s proxy? I thought the ingress controller would take care of this, or did I misunderstand this?

ANSWER

Answered 2021-Oct-10 at 18:29

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
57apiVersion: networking.k8s.io/v1
58kind: Ingress
59metadata:
60  name: dashboard
61  namespace: kube-system
62spec:
63  rules:
64  - http:
65      paths:
66      - path: /dashboard
67        pathType: Prefix
68        backend:
69          service:
70            name: kubernetes-dashboard
71            port:
72              number: 443
73NAMESPACE     NAME        CLASS    HOSTS   ADDRESS     PORTS   AGE
74kube-system   dashboard   public   *       127.0.0.1   80      11m
75192.168.0.123 - - [10/Oct/2021:21:38:47 +0000] &quot;GET /dashboard HTTP/1.1&quot; 400 54 &quot;-&quot; &quot;Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36&quot; 466 0.002 [kube-system-kubernetes-dashboard-443] [] 10.1.76.3:8443 48 0.000 400 ca0946230759edfbaaf9d94f3d5c959a
76error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
77

it' due to the mismatch in the ingress API version.

You are running the v1.22.2 while API version in YAML is old.

Good example : https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/

you are using the older ingress API version in your YAML which is extensions/v1beta1.

You need to change this based on ingress version and K8s version you are running.

This is for version 1.19 in K8s and will work in 1.22 also

Example :

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
57apiVersion: networking.k8s.io/v1
58kind: Ingress
59metadata:
60  name: dashboard
61  namespace: kube-system
62spec:
63  rules:
64  - http:
65      paths:
66      - path: /dashboard
67        pathType: Prefix
68        backend:
69          service:
70            name: kubernetes-dashboard
71            port:
72              number: 443
73NAMESPACE     NAME        CLASS    HOSTS   ADDRESS     PORTS   AGE
74kube-system   dashboard   public   *       127.0.0.1   80      11m
75192.168.0.123 - - [10/Oct/2021:21:38:47 +0000] &quot;GET /dashboard HTTP/1.1&quot; 400 54 &quot;-&quot; &quot;Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36&quot; 466 0.002 [kube-system-kubernetes-dashboard-443] [] 10.1.76.3:8443 48 0.000 400 ca0946230759edfbaaf9d94f3d5c959a
76error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
77apiVersion: networking.k8s.io/v1
78kind: Ingress
79metadata:
80  name: minimal-ingress
81  annotations:
82    nginx.ingress.kubernetes.io/rewrite-target: /
83spec:
84  rules:
85  - http:
86      paths:
87      - path: /testpath
88        pathType: Prefix
89        backend:
90          service:
91            name: test
92            port:
93              number: 80
94

Reference : https://kubernetes.io/docs/concepts/services-networking/ingress/

Source https://stackoverflow.com/questions/69517855

QUESTION

Laravel Homestead - page stopped working ERR_ADDRESS_UNREACHABLE

Asked 2022-Mar-25 at 09:10

Took my laptop out of house for a couple of days, didn't even get to turn it on during that time. Came back, ready to keep fiddling with my project but the page stopped working all of a sudden. I started getting ERR_ADDRESS_UNREACHABLE in the browser.

I've uninstalled homestead box, vagrant, virtualbox, with restart after each, re installed everything, same issue.

I can not ping the 192.168.10.10 address but I can SSH into the box no problem.

Running MacOS Big Sur, VirtualBox 6.1, Vagrant 2.2.18 and whatever the latest homestead version is. Really about quit programming altogether, this is super frustrating. I'd really appreciate any help. Thank you

Homestead.yaml

1---
2ip: &quot;192.168.10.10&quot;
3memory: 2048
4cpus: 2
5provider: virtualbox
6
7authorize: ~/.ssh/id_rsa.pub
8
9keys:
10    - ~/.ssh/id_rsa
11
12folders:
13    - map: ~/Documents/Code
14      to: /home/vagrant/code
15
16sites:
17    - map: homestead.test
18      to: /home/vagrant/code/PHP/test/public
19
20databases:
21    - homestead
22
23features:
24    - mysql: true
25    - mariadb: false
26    - postgresql: false
27    - ohmyzsh: false
28    - webdriver: false
29
30services:
31    - enabled:
32          - &quot;mysql&quot;
33

Vagrantfile

1---
2ip: &quot;192.168.10.10&quot;
3memory: 2048
4cpus: 2
5provider: virtualbox
6
7authorize: ~/.ssh/id_rsa.pub
8
9keys:
10    - ~/.ssh/id_rsa
11
12folders:
13    - map: ~/Documents/Code
14      to: /home/vagrant/code
15
16sites:
17    - map: homestead.test
18      to: /home/vagrant/code/PHP/test/public
19
20databases:
21    - homestead
22
23features:
24    - mysql: true
25    - mariadb: false
26    - postgresql: false
27    - ohmyzsh: false
28    - webdriver: false
29
30services:
31    - enabled:
32          - &quot;mysql&quot;
33# -*- mode: ruby -*-
34# vi: set ft=ruby :
35
36require 'json'
37require 'yaml'
38
39VAGRANTFILE_API_VERSION ||= &quot;2&quot;
40confDir = $confDir ||= File.expand_path(File.dirname(__FILE__))
41
42homesteadYamlPath = confDir + &quot;/Homestead.yaml&quot;
43homesteadJsonPath = confDir + &quot;/Homestead.json&quot;
44afterScriptPath = confDir + &quot;/after.sh&quot;
45customizationScriptPath = confDir + &quot;/user-customizations.sh&quot;
46aliasesPath = confDir + &quot;/aliases&quot;
47
48require File.expand_path(File.dirname(__FILE__) + '/scripts/homestead.rb')
49
50Vagrant.require_version '&gt;= 2.2.4'
51
52
53Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
54    if File.exist? aliasesPath then
55        config.vm.provision &quot;file&quot;, source: aliasesPath, destination: &quot;/tmp/bash_aliases&quot;
56        config.vm.provision &quot;handle_aliases&quot;, type: &quot;shell&quot; do |s|
57            s.inline = &quot;awk '{ sub(\&quot;\r$\&quot;, \&quot;\&quot;); print }' /tmp/bash_aliases &gt; /home/vagrant/.bash_aliases &amp;&amp; chown vagrant:vagrant /home/vagrant/.bash_aliases&quot;
58        end
59    end
60
61    if File.exist? homesteadYamlPath then
62        settings = YAML::load(File.read(homesteadYamlPath))
63    elsif File.exist? homesteadJsonPath then
64        settings = JSON::parse(File.read(homesteadJsonPath))
65    else
66        abort &quot;Homestead settings file not found in #{confDir}&quot;
67    end
68
69    Homestead.configure(config, settings)
70
71    if File.exist? afterScriptPath then
72        config.vm.provision &quot;Run after.sh&quot;, type: &quot;shell&quot;, path: afterScriptPath, privileged: false, keep_color: true
73    end
74
75    if File.exist? customizationScriptPath then
76        config.vm.provision &quot;Run customize script&quot;, type: &quot;shell&quot;, path: customizationScriptPath, privileged: false, keep_color: true
77    end
78
79    if Vagrant.has_plugin?('vagrant-hostsupdater')
80        config.hostsupdater.remove_on_suspend = false
81        config.hostsupdater.aliases = settings['sites'].map { |site| site['map'] }
82    elsif Vagrant.has_plugin?('vagrant-hostmanager')
83        config.hostmanager.enabled = true
84        config.hostmanager.manage_host = true
85        config.hostmanager.aliases = settings['sites'].map { |site| site['map'] }
86    elsif Vagrant.has_plugin?('vagrant-goodhosts')
87        config.goodhosts.aliases = settings['sites'].map { |site| site['map'] }
88    end
89
90    if Vagrant.has_plugin?('vagrant-notify-forwarder')
91        config.notify_forwarder.enable = true
92    end
93end
94

I did try to setup networking as described here and here but nothing worked.

ANSWER

Answered 2021-Oct-29 at 20:41

I think this is the fix, but I couldn't get it running until now:

Anything in the 192.68.56.0/21 range will work out-of-the-box without any custom configuration per VirtualBox's documentation.

https://github.com/laravel/homestead/issues/1717

Found some more related information here:

https://discuss.hashicorp.com/t/vagrant-2-2-18-osx-11-6-cannot-create-private-network/30984/16

update 29.10.2021:
I downgraded virtualbox to 6.1.26 and it's working again.

Source https://stackoverflow.com/questions/69731953

QUESTION

Why URL re-writing is not working when I do not use slash at the end?

Asked 2022-Mar-13 at 20:40

I have a simple ingress configuration file-

1apiVersion: networking.k8s.io/v1
2kind: Ingress
3metadata:
4  annotations:
5    nginx.ingress.kubernetes.io/rewrite-target: /link2/link3/
6  name: tut-ingress
7  namespace: default
8spec:
9  rules:
10    - host: tutorial.com
11      http:
12        paths:
13          - path: /link1/
14            pathType: Prefix
15            backend:
16              service:
17                name: nginx-ingress-tut-service
18                port:
19                  number: 8080
20

in which requests coming to /link1 or /link1/ are rewritten to /link2/link3/. When I access it using http://tutorial.com/link1/ I am shown the correct result but when I access it using http://tutorial.com/link1, I get a 404 not found. The nginx-ingress-tut-service has the following endpoints-

/
/link1
/link2/link3

I am a beginner in the web domain, any help will be appreciated.

When I change it to-

1apiVersion: networking.k8s.io/v1
2kind: Ingress
3metadata:
4  annotations:
5    nginx.ingress.kubernetes.io/rewrite-target: /link2/link3/
6  name: tut-ingress
7  namespace: default
8spec:
9  rules:
10    - host: tutorial.com
11      http:
12        paths:
13          - path: /link1/
14            pathType: Prefix
15            backend:
16              service:
17                name: nginx-ingress-tut-service
18                port:
19                  number: 8080
20- path: /link1
21

it starts working fine, but can anybody tell why is it not working with /link1/.

Helpful resources - https://kubernetes.io/docs/concepts/services-networking/ingress/#examples

https://kubernetes.github.io/ingress-nginx/examples/rewrite/

Edit- Please also explain what happens when you write a full HTTP link in nginx.ingress.kubernetes.io/rewrite-target

ANSWER

Answered 2022-Mar-13 at 20:40

The answer is posted in the comment:

Well, /link1/ is not a prefix of /link1 because a prefix must be the same length or longer than the target string

If you have

1apiVersion: networking.k8s.io/v1
2kind: Ingress
3metadata:
4  annotations:
5    nginx.ingress.kubernetes.io/rewrite-target: /link2/link3/
6  name: tut-ingress
7  namespace: default
8spec:
9  rules:
10    - host: tutorial.com
11      http:
12        paths:
13          - path: /link1/
14            pathType: Prefix
15            backend:
16              service:
17                name: nginx-ingress-tut-service
18                port:
19                  number: 8080
20- path: /link1
21- path: /link1/
22

the string to match will have to have a / character at the end of the path. Everything works correctly. In this situation if you try to access by the link http://tutorial.com/link1 you will get 404 error, because ingress was expecting http://tutorial.com/link1/.

For more you can see examples of rewrite rule and documentation about path types:

Each path in an Ingress is required to have a corresponding path type. Paths that do not include an explicit pathType will fail validation. There are three supported path types:

ImplementationSpecific: With this path type, matching is up to the IngressClass. Implementations can treat this as a separate pathType or treat it identically to Prefix or Exact path types.

Exact: Matches the URL path exactly and with case sensitivity.

Prefix: Matches based on a URL path prefix split by /. Matching is case sensitive and done on a path element by element basis. A path element refers to the list of labels in the path split by the / separator. A request is a match for path p if every p is an element-wise prefix of p of the request path.

EDIT: Based on documentation this should work, but it looks like there is a fresh problem with nginx ingress. The problem is still unresolved. You can use workaround posted in this topic or try to change your you similar to this:

1apiVersion: networking.k8s.io/v1
2kind: Ingress
3metadata:
4  annotations:
5    nginx.ingress.kubernetes.io/rewrite-target: /link2/link3/
6  name: tut-ingress
7  namespace: default
8spec:
9  rules:
10    - host: tutorial.com
11      http:
12        paths:
13          - path: /link1/
14            pathType: Prefix
15            backend:
16              service:
17                name: nginx-ingress-tut-service
18                port:
19                  number: 8080
20- path: /link1
21- path: /link1/
22- path: /link1(/|$)
23

Source https://stackoverflow.com/questions/71424259

QUESTION

Standard compliant host to network endianess conversion

Asked 2022-Mar-03 at 15:19

I am amazed at how many topics on StackOverflow deal with finding out the endianess of the system and converting endianess. I am even more amazed that there are hundreds of different answers to these two questions. All proposed solutions that I have seen so far are based on undefined behaviour, non-standard compiler extensions or OS-specific header files. In my opinion, this question is only a duplicate if an existing answer gives a standard-compliant, efficient (e.g., use x86-bswap), compile time-enabled solution.

Surely there must be a standard-compliant solution available that I am unable to find in the huge mess of old "hacky" ones. It is also somewhat strange that the standard library does not include such a function. Perhaps the attitude towards such issues is changing, since C++20 introduced a way to detect endianess into the standard (via std::endian), and C++23 will probably include std::byteswap, which flips endianess.

In any case, my questions are these:

Starting at what C++ standard is there a portable standard-compliant way of performing host to network byte order conversion?
I argue below that it's possible in C++20. Is my code correct and can it be improved?
Should such a pure-c++ solution be preferred to OS specific functions such as, e.g., POSIX-htonl? (I think yes)

I think I can give a C++23 solution that is OS-independent, efficient (no system call, uses x86-bswap) and portable to little-endian and big-endian systems (but not portable to mixed-endian systems):

1// requires C++23. see https://gcc.godbolt.org/z/6or1sEvKn
2#include &lt;type_traits&gt;
3#include &lt;utility&gt;
4#include &lt;bit&gt;
5
6constexpr inline auto host_to_net(std::integral auto i) {
7    static_assert(std::endian::native == std::endian::big || std::endian::native == std::endian::little);
8    if constexpr (std::endian::native == std::endian::big) {
9        return i;
10    } else {
11        return std::byteswap(i);
12    }
13}
14

Since std::endian is available in C++20, one can give a C++20 solution for host_to_net by implementing byteswap manually. A solution is described here, quote:

1// requires C++23. see https://gcc.godbolt.org/z/6or1sEvKn
2#include &lt;type_traits&gt;
3#include &lt;utility&gt;
4#include &lt;bit&gt;
5
6constexpr inline auto host_to_net(std::integral auto i) {
7    static_assert(std::endian::native == std::endian::big || std::endian::native == std::endian::little);
8    if constexpr (std::endian::native == std::endian::big) {
9        return i;
10    } else {
11        return std::byteswap(i);
12    }
13}
14// requires C++17
15#include &lt;climits&gt;
16#include &lt;cstdint&gt;
17#include &lt;type_traits&gt;
18
19template&lt;class T, std::size_t... N&gt;
20constexpr T bswap_impl(T i, std::index_sequence&lt;N...&gt;) {
21  return ((((i &gt;&gt; (N * CHAR_BIT)) &amp; (T)(unsigned char)(-1)) &lt;&lt;
22           ((sizeof(T) - 1 - N) * CHAR_BIT)) | ...);
23}; //                                        ^~~~~ fold expression
24template&lt;class T, class U = typename std::make_unsigned&lt;T&gt;::type&gt;
25constexpr U bswap(T i) {
26  return bswap_impl&lt;U&gt;(i, std::make_index_sequence&lt;sizeof(T)&gt;{});
27}
28

The linked answer also provides a C++11 byteswap, but that one seems to be less efficient (not compiled to x86-bswap). I think there should be an efficient C++11 way of doing this, too (using either less template-nonsense or even more) but I don't care about older C++ and didn't really try.

Assuming I am correct, the remaining question is: can one can determine system endianess before C++20 at compile time in a standard-compliant and compiler-agnostic way? None of the answers here seem to do achieve this. They use reinterpret_cast (not compile time), OS-headers, union aliasing (which I believe is UB in C++), etc. Also, for some reason, they try to do it "at runtime" although a compiled executable will always run under the same endianess.)

One could do it outside of constexpr context and hope it's optimized away. On the other hand, one could use system-defined preprocessor definitions and account for all platforms, as seems to be the approach taken by Boost. Or maybe (although I would guess the other way is better?) use macros and pick platform-specific htnl-style functions from networking libraries(done, e.g., here (GitHub))?

ANSWER

Answered 2022-Feb-06 at 05:48

compile time-enabled solution.

Consider whether this is useful requirement in the first place. The program isn't going to be communicating with another system at compile time. What is the case where you would need to use the serialised integer in a compile time constant context?

Starting at what C++ standard is there a portable standard-compliant way of performing host to network byte order conversion?

It's possible to write such function in standard C++ since C++98. That said, later standards bring tasty template goodies that make this nicer.

There isn't such function in the standard library as of the latest standard.

Should such a pure-c++ solution be preferred to OS specific functions such as, e.g., POSIX-htonl? (I think yes)

Advantage of POSIX is that it's less important to write tests to make sure that it works correctly.

Advantage of pure C++ function is that you don't need platform specific alternatives to those that don't conform to POSIX.

Also, the POSIX htonX are only for 16 bit and 32 bit integers. You could instead use htobeXX functions instead that are in some *BSD and in Linux (glibc).

Here is what I have been using since C+17. Some notes beforehand:

Since endianness conversion is always¹ for purposes of serialisation, I write the result directly into a buffer. When converting to host endianness, I read from a buffer.
I don't use CHAR_BIT because network doesn't know my byte size anyway. Network byte is an octet, and if your CPU is different, then these functions won't work. Correct handling of non-octet byte is possible but unnecessary work unless you need to support network communication on such system. Adding an assert might be a good idea.
I prefer to call it big endian rather than "network" endian. There's a chance that a reader isn't aware of the convention that de-facto endianness of network is big.
Instead of checking "if native endianness is X, do Y else do Z", I prefer to write a function that works with all native endianness. This can be done with bit shifts.
Yeah, it's constexpr. Not because it needs to be, but just because it can be. I haven't been able to produce an example where dropping constexpr would produce worse code.

1// requires C++23. see https://gcc.godbolt.org/z/6or1sEvKn
2#include &lt;type_traits&gt;
3#include &lt;utility&gt;
4#include &lt;bit&gt;
5
6constexpr inline auto host_to_net(std::integral auto i) {
7    static_assert(std::endian::native == std::endian::big || std::endian::native == std::endian::little);
8    if constexpr (std::endian::native == std::endian::big) {
9        return i;
10    } else {
11        return std::byteswap(i);
12    }
13}
14// requires C++17
15#include &lt;climits&gt;
16#include &lt;cstdint&gt;
17#include &lt;type_traits&gt;
18
19template&lt;class T, std::size_t... N&gt;
20constexpr T bswap_impl(T i, std::index_sequence&lt;N...&gt;) {
21  return ((((i &gt;&gt; (N * CHAR_BIT)) &amp; (T)(unsigned char)(-1)) &lt;&lt;
22           ((sizeof(T) - 1 - N) * CHAR_BIT)) | ...);
23}; //                                        ^~~~~ fold expression
24template&lt;class T, class U = typename std::make_unsigned&lt;T&gt;::type&gt;
25constexpr U bswap(T i) {
26  return bswap_impl&lt;U&gt;(i, std::make_index_sequence&lt;sizeof(T)&gt;{});
27}
28// helper to promote an integer type
29template &lt;class T&gt;
30using promote_t = std::decay_t&lt;decltype(+std::declval&lt;T&gt;())&gt;;
31
32template &lt;class T, std::size_t... I&gt;
33constexpr void
34host_to_big_impl(
35    unsigned char* buf,
36    T t,
37    [[maybe_unused]] std::index_sequence&lt;I...&gt;) noexcept
38{
39    using U = std::make_unsigned_t&lt;promote_t&lt;T&gt;&gt;;
40    constexpr U lastI = sizeof(T) - 1u;
41    constexpr U bits = 8u;
42    U u = t;
43    ( (buf[I] = u &gt;&gt; ((lastI - I) * bits)), ... );
44}
45
46
47template &lt;class T, std::size_t... I&gt;
48constexpr void
49host_to_big(unsigned char* buf, T t) noexcept
50{
51    using Indices = std::make_index_sequence&lt;sizeof(T)&gt;;
52    return host_to_big_impl&lt;T&gt;(buf, t, Indices{});
53}
54

_{¹ In all use cases I've encountered. Conversions from integer to integer can be implemented by delegating these if you have such case, although they cannot be constexpr due to need for reinterpret_cast.}

Source https://stackoverflow.com/questions/71003780

QUESTION

How to configure proxy in emulators in new versions of Android Studio?

Asked 2022-Feb-23 at 14:14

Problem Description

I need to configure the proxy manually in my emulator through Android Studio. From the official Android documentation, it is suggested that this change can be made in the "settings" tab of the emulator's extended controls. The problem is that it seems to me that this documentation is outdated, as this setting is no longer displayed in the "settings" tab of the Android Studio emulators' extended controls.

Documentation

My Android Studio

My version of Android Studio

1Android Studio Bumblebee | 2021.1.1
2Build #AI-211.7628.21.2111.8092744, built on January 19, 2022
3Runtime version: 11.0.11+9-b60-7590822 amd64
4VM: OpenJDK 64-Bit Server VM by Oracle Corporation
5Windows 10 10.0
6GC: G1 Young Generation, G1 Old Generation
7Memory: 1280M
8Cores: 8
9Registry: external.system.auto.import.disabled=true
10Non-Bundled Plugins: com.wakatime.intellij.plugin (13.1.10), wu.seal.tool.jsontokotlin (3.7.2), org.jetbrains.kotlin (211-1.6.10-release-923-AS7442.40), com.developerphil.adbidea (1.6.4), org.jetbrains.compose.desktop.ide (1.0.0), ru.adelf.idea.dotenv (2021.2), org.intellij.plugins.markdown (211.7142.37)
11

ANSWER

Answered 2022-Feb-17 at 19:12

After a while trying to find solutions to this problem, I saw that an emulator running outside android studio provides these options. To run a standalone Android Studio emulator see the official documentation or simply enter the command:

1Android Studio Bumblebee | 2021.1.1
2Build #AI-211.7628.21.2111.8092744, built on January 19, 2022
3Runtime version: 11.0.11+9-b60-7590822 amd64
4VM: OpenJDK 64-Bit Server VM by Oracle Corporation
5Windows 10 10.0
6GC: G1 Young Generation, G1 Old Generation
7Memory: 1280M
8Cores: 8
9Registry: external.system.auto.import.disabled=true
10Non-Bundled Plugins: com.wakatime.intellij.plugin (13.1.10), wu.seal.tool.jsontokotlin (3.7.2), org.jetbrains.kotlin (211-1.6.10-release-923-AS7442.40), com.developerphil.adbidea (1.6.4), org.jetbrains.compose.desktop.ide (1.0.0), ru.adelf.idea.dotenv (2021.2), org.intellij.plugins.markdown (211.7142.37)
11emulator -avd &lt;avd_name&gt;
12

In my case I'm using an avd named PIXEL 4 API 30, so the command will be emulator -avd PIXEL_4_API_30. If you are on Windows you may have problems running this command so I suggest you see this.

Edit

The solution proposed by @Inliner also solves this problem.

Source https://stackoverflow.com/questions/70972106

QUESTION

Unable to log egress traffic HTTP requests with the istio-proxy

Asked 2022-Feb-11 at 10:45

I am following this guide.

Ingress requests are getting logged. Egress traffic control is working as expected, except I am unable to log egress HTTP requests. What is missing?

1apiVersion: networking.istio.io/v1beta1
2kind: Sidecar
3metadata:
4  name: myapp
5spec:
6  workloadSelector:
7    labels:
8      app: myapp
9
10  outboundTrafficPolicy:
11    mode: REGISTRY_ONLY
12
13  egress:
14    - hosts:
15        - default/*.example.com
16

1apiVersion: networking.istio.io/v1beta1
2kind: Sidecar
3metadata:
4  name: myapp
5spec:
6  workloadSelector:
7    labels:
8      app: myapp
9
10  outboundTrafficPolicy:
11    mode: REGISTRY_ONLY
12
13  egress:
14    - hosts:
15        - default/*.example.com
16apiVersion: networking.istio.io/v1alpha3
17kind: ServiceEntry
18metadata:
19  name: example
20
21spec:
22  location: MESH_EXTERNAL
23  resolution: NONE
24  hosts:
25    - '*.example.com'
26
27  ports:
28    - name: https
29      protocol: TLS
30      number: 443
31

1apiVersion: networking.istio.io/v1beta1
2kind: Sidecar
3metadata:
4  name: myapp
5spec:
6  workloadSelector:
7    labels:
8      app: myapp
9
10  outboundTrafficPolicy:
11    mode: REGISTRY_ONLY
12
13  egress:
14    - hosts:
15        - default/*.example.com
16apiVersion: networking.istio.io/v1alpha3
17kind: ServiceEntry
18metadata:
19  name: example
20
21spec:
22  location: MESH_EXTERNAL
23  resolution: NONE
24  hosts:
25    - '*.example.com'
26
27  ports:
28    - name: https
29      protocol: TLS
30      number: 443
31apiVersion: telemetry.istio.io/v1alpha1
32kind: Telemetry
33metadata:
34  name: mesh-default
35  namespace: istio-system
36spec:
37  accessLogging:
38    - providers:
39        - name: envoy
40
41

Kubernetes 1.22.2 Istio 1.11.4

ANSWER

Answered 2022-Feb-07 at 17:14

AFAIK istio collects only ingress HTTP logs by default.

In the istio documentation there is an old article (from 2018) describing how to enable egress traffic HTTP logs.

Please keep in mind that some of the information may be outdated, however I believe this is the part that you are missing.

Source https://stackoverflow.com/questions/71018977

QUESTION

Dynamodb local web shell does not load

Asked 2022-Jan-15 at 14:55

I am running DynamoDB locally using the instructions here. To remove potential docker networking issues I am using the "Download Locally" version of the instructions. Before running dynamo locally I run aws configure to set some fake values for AWS access, secret, and region, and here is the output:

1$ aws configure
2AWS Access Key ID [****************fake]:
3AWS Secret Access Key [****************ake2]:
4Default region name [local]:
5Default output format [json]:
6

here is the output of running dynamo locally:

1$ aws configure
2AWS Access Key ID [****************fake]:
3AWS Secret Access Key [****************ake2]:
4Default region name [local]:
5Default output format [json]:
6$ java -Djava.library.path=./DynamoDBLocal_lib -jar DynamoDBLocal.jar -sharedDb
7Initializing DynamoDB Local with the following configuration:
8Port:   8000
9InMemory:   false
10DbPath: null
11SharedDb:   true
12shouldDelayTransientStatuses:   false
13CorsParams: *
14

I can confirm that the DynamoDB is running locally successfully by listing tables using aws cli

1$ aws configure
2AWS Access Key ID [****************fake]:
3AWS Secret Access Key [****************ake2]:
4Default region name [local]:
5Default output format [json]:
6$ java -Djava.library.path=./DynamoDBLocal_lib -jar DynamoDBLocal.jar -sharedDb
7Initializing DynamoDB Local with the following configuration:
8Port:   8000
9InMemory:   false
10DbPath: null
11SharedDb:   true
12shouldDelayTransientStatuses:   false
13CorsParams: *
14$ aws dynamodb list-tables --endpoint-url http://localhost:8000
15{
16    &quot;TableNames&quot;: []
17}
18

but when I visit http://localhost:8000/shell in my browser, this is the error I get and the page does not load.

I tried running curl on the shell to see if I can get a more useful error message:

1$ aws configure
2AWS Access Key ID [****************fake]:
3AWS Secret Access Key [****************ake2]:
4Default region name [local]:
5Default output format [json]:
6$ java -Djava.library.path=./DynamoDBLocal_lib -jar DynamoDBLocal.jar -sharedDb
7Initializing DynamoDB Local with the following configuration:
8Port:   8000
9InMemory:   false
10DbPath: null
11SharedDb:   true
12shouldDelayTransientStatuses:   false
13CorsParams: *
14$ aws dynamodb list-tables --endpoint-url http://localhost:8000
15{
16    &quot;TableNames&quot;: []
17}
18$ curl http://localhost:8000/shell
19{
20&quot;__type&quot;:&quot;com.amazonaws.dynamodb.v20120810#MissingAuthenticationToken&quot;,
21&quot;Message&quot;:&quot;Request must contain either a valid (registered) AWS access key ID or X.509 certificate.&quot;}%
22

I tried looking up the error above, but I don't have much choice in doing setup when running the shell merely in the browser. Any help is appreciated on how I can run the Dynamodb javascript web shell with this setting.

Software versions:

aws cli: aws-cli/2.4.7 Python/3.9.9 Darwin/20.6.0 source/x86_64 prompt/off

OS: MacOS Big Sur 11.6.2 (20G314)

ANSWER

Answered 2022-Jan-13 at 08:12

As I answered in DynamoDB local http://localhost:8000/shell this appears to be a regression in new versions of DynamoDB Local, where the shell mysteriously stopped working, whereas in versions from a year ago it does work.

Somebody should report it to Amazon. If there is some flag that new versions require you to set to enable the shell, it isn't documented anywhere that I can find.

Source https://stackoverflow.com/questions/70535330

QUESTION

Cancelling an async/await Network Request

Asked 2022-Jan-03 at 22:23

I have a networking layer that currently uses completion handlers to deliver a result on the operation is complete.

As I support a number of iOS versions, I instead extend the network layer within the app to provide support for Combine. I'd like to extend this to now also a support Async/Await but I am struggling to understand how I can achieve this in a way that allows me to cancel requests.

The basic implementation looks like;

1
2protocol HTTPClientTask {
3    func cancel()
4}
5
6protocol HTTPClient {
7    typealias Result = Swift.Result&lt;(data: Data, response: HTTPURLResponse), Error&gt;
8    @discardableResult
9    func dispatch(_ request: URLRequest, completion: @escaping (Result) -&gt; Void) -&gt; HTTPClientTask
10}
11
12final class URLSessionHTTPClient: HTTPClient {
13    
14    private let session: URLSession
15    
16    init(session: URLSession) {
17        self.session = session
18    }
19    
20    func dispatch(_ request: URLRequest, completion: @escaping (HTTPClient.Result) -&gt; Void) -&gt; HTTPClientTask {
21        let task = session.dataTask(with: request) { data, response, error in
22            completion(Result {
23                if let error = error {
24                    throw error
25                } else if let data = data, let response = response as? HTTPURLResponse {
26                    return (data, response)
27                } else {
28                    throw UnexpectedValuesRepresentation()
29                }
30            })
31        }
32        task.resume()
33        return URLSessionTaskWrapper(wrapped: task)
34    }
35}
36
37private extension URLSessionHTTPClient {
38    struct UnexpectedValuesRepresentation: Error {}
39    
40    struct URLSessionTaskWrapper: HTTPClientTask {
41        let wrapped: URLSessionTask
42        
43        func cancel() {
44            wrapped.cancel()
45        }
46    }
47}
48

It very simply provides an abstraction that allows me to inject a URLSession instance.

By returning HTTPClientTask I can call cancel from a client and end the request.

I extend this in a client app using Combine as follows;

1
2protocol HTTPClientTask {
3    func cancel()
4}
5
6protocol HTTPClient {
7    typealias Result = Swift.Result&lt;(data: Data, response: HTTPURLResponse), Error&gt;
8    @discardableResult
9    func dispatch(_ request: URLRequest, completion: @escaping (Result) -&gt; Void) -&gt; HTTPClientTask
10}
11
12final class URLSessionHTTPClient: HTTPClient {
13    
14    private let session: URLSession
15    
16    init(session: URLSession) {
17        self.session = session
18    }
19    
20    func dispatch(_ request: URLRequest, completion: @escaping (HTTPClient.Result) -&gt; Void) -&gt; HTTPClientTask {
21        let task = session.dataTask(with: request) { data, response, error in
22            completion(Result {
23                if let error = error {
24                    throw error
25                } else if let data = data, let response = response as? HTTPURLResponse {
26                    return (data, response)
27                } else {
28                    throw UnexpectedValuesRepresentation()
29                }
30            })
31        }
32        task.resume()
33        return URLSessionTaskWrapper(wrapped: task)
34    }
35}
36
37private extension URLSessionHTTPClient {
38    struct UnexpectedValuesRepresentation: Error {}
39    
40    struct URLSessionTaskWrapper: HTTPClientTask {
41        let wrapped: URLSessionTask
42        
43        func cancel() {
44            wrapped.cancel()
45        }
46    }
47}
48extension HTTPClient {
49    typealias Publisher = AnyPublisher&lt;(data: Data, response: HTTPURLResponse), Error&gt;
50
51    func dispatchPublisher(for request: URLRequest) -&gt; Publisher {
52        var task: HTTPClientTask?
53
54        return Deferred {
55            Future { completion in
56                task = self.dispatch(request, completion: completion)
57            }
58        }
59        .handleEvents(receiveCancel: { task?.cancel() })
60        .eraseToAnyPublisher()
61    }
62}
63

As you can see I now have an interface that supports canceling tasks.

Using async/await however, I am unsure what this should look like, how I can provide a mechanism for canceling requests.

My current attempt is;

1
2protocol HTTPClientTask {
3    func cancel()
4}
5
6protocol HTTPClient {
7    typealias Result = Swift.Result&lt;(data: Data, response: HTTPURLResponse), Error&gt;
8    @discardableResult
9    func dispatch(_ request: URLRequest, completion: @escaping (Result) -&gt; Void) -&gt; HTTPClientTask
10}
11
12final class URLSessionHTTPClient: HTTPClient {
13    
14    private let session: URLSession
15    
16    init(session: URLSession) {
17        self.session = session
18    }
19    
20    func dispatch(_ request: URLRequest, completion: @escaping (HTTPClient.Result) -&gt; Void) -&gt; HTTPClientTask {
21        let task = session.dataTask(with: request) { data, response, error in
22            completion(Result {
23                if let error = error {
24                    throw error
25                } else if let data = data, let response = response as? HTTPURLResponse {
26                    return (data, response)
27                } else {
28                    throw UnexpectedValuesRepresentation()
29                }
30            })
31        }
32        task.resume()
33        return URLSessionTaskWrapper(wrapped: task)
34    }
35}
36
37private extension URLSessionHTTPClient {
38    struct UnexpectedValuesRepresentation: Error {}
39    
40    struct URLSessionTaskWrapper: HTTPClientTask {
41        let wrapped: URLSessionTask
42        
43        func cancel() {
44            wrapped.cancel()
45        }
46    }
47}
48extension HTTPClient {
49    typealias Publisher = AnyPublisher&lt;(data: Data, response: HTTPURLResponse), Error&gt;
50
51    func dispatchPublisher(for request: URLRequest) -&gt; Publisher {
52        var task: HTTPClientTask?
53
54        return Deferred {
55            Future { completion in
56                task = self.dispatch(request, completion: completion)
57            }
58        }
59        .handleEvents(receiveCancel: { task?.cancel() })
60        .eraseToAnyPublisher()
61    }
62}
63extension HTTPClient {
64    func dispatch(_ request: URLRequest) async -&gt; HTTPClient.Result {
65
66        let task = Task { () -&gt; (data: Data, response: HTTPURLResponse) in
67            return try await withCheckedThrowingContinuation { continuation in
68                self.dispatch(request) { result in
69                    switch result {
70                    case let .success(values): continuation.resume(returning: values)
71                    case let .failure(error): continuation.resume(throwing: error)
72                    }
73                }
74            }
75        }
76
77        do {
78            let output = try await task.value
79            return .success(output)
80        } catch {
81            return .failure(error)
82        }
83    }
84}
85

However this simply provides the async implementation, I am unable to cancel this.

How should this be handled?

ANSWER

Answered 2021-Oct-10 at 13:42

async/await might not be the proper paradigm if you want cancellation. The reason is that the new structured concurrency support in Swift allows you to write code that looks single-threaded/synchronous, but it fact it's multi-threaded.

Take for example a naive synchronous code:

1
2protocol HTTPClientTask {
3    func cancel()
4}
5
6protocol HTTPClient {
7    typealias Result = Swift.Result&lt;(data: Data, response: HTTPURLResponse), Error&gt;
8    @discardableResult
9    func dispatch(_ request: URLRequest, completion: @escaping (Result) -&gt; Void) -&gt; HTTPClientTask
10}
11
12final class URLSessionHTTPClient: HTTPClient {
13    
14    private let session: URLSession
15    
16    init(session: URLSession) {
17        self.session = session
18    }
19    
20    func dispatch(_ request: URLRequest, completion: @escaping (HTTPClient.Result) -&gt; Void) -&gt; HTTPClientTask {
21        let task = session.dataTask(with: request) { data, response, error in
22            completion(Result {
23                if let error = error {
24                    throw error
25                } else if let data = data, let response = response as? HTTPURLResponse {
26                    return (data, response)
27                } else {
28                    throw UnexpectedValuesRepresentation()
29                }
30            })
31        }
32        task.resume()
33        return URLSessionTaskWrapper(wrapped: task)
34    }
35}
36
37private extension URLSessionHTTPClient {
38    struct UnexpectedValuesRepresentation: Error {}
39    
40    struct URLSessionTaskWrapper: HTTPClientTask {
41        let wrapped: URLSessionTask
42        
43        func cancel() {
44            wrapped.cancel()
45        }
46    }
47}
48extension HTTPClient {
49    typealias Publisher = AnyPublisher&lt;(data: Data, response: HTTPURLResponse), Error&gt;
50
51    func dispatchPublisher(for request: URLRequest) -&gt; Publisher {
52        var task: HTTPClientTask?
53
54        return Deferred {
55            Future { completion in
56                task = self.dispatch(request, completion: completion)
57            }
58        }
59        .handleEvents(receiveCancel: { task?.cancel() })
60        .eraseToAnyPublisher()
61    }
62}
63extension HTTPClient {
64    func dispatch(_ request: URLRequest) async -&gt; HTTPClient.Result {
65
66        let task = Task { () -&gt; (data: Data, response: HTTPURLResponse) in
67            return try await withCheckedThrowingContinuation { continuation in
68                self.dispatch(request) { result in
69                    switch result {
70                    case let .success(values): continuation.resume(returning: values)
71                    case let .failure(error): continuation.resume(throwing: error)
72                    }
73                }
74            }
75        }
76
77        do {
78            let output = try await task.value
79            return .success(output)
80        } catch {
81            return .failure(error)
82        }
83    }
84}
85let data = tryData(contentsOf: fileURL)
86

If the file is huge, then it might take a lot of time for the operation to finish, and during this time the operation cannot be cancelled, and the caller thread is blocked.

Now, assuming Data exports an async version of the above initializer, you'd write the async version of the code similar to this:

1
2protocol HTTPClientTask {
3    func cancel()
4}
5
6protocol HTTPClient {
7    typealias Result = Swift.Result&lt;(data: Data, response: HTTPURLResponse), Error&gt;
8    @discardableResult
9    func dispatch(_ request: URLRequest, completion: @escaping (Result) -&gt; Void) -&gt; HTTPClientTask
10}
11
12final class URLSessionHTTPClient: HTTPClient {
13    
14    private let session: URLSession
15    
16    init(session: URLSession) {
17        self.session = session
18    }
19    
20    func dispatch(_ request: URLRequest, completion: @escaping (HTTPClient.Result) -&gt; Void) -&gt; HTTPClientTask {
21        let task = session.dataTask(with: request) { data, response, error in
22            completion(Result {
23                if let error = error {
24                    throw error
25                } else if let data = data, let response = response as? HTTPURLResponse {
26                    return (data, response)
27                } else {
28                    throw UnexpectedValuesRepresentation()
29                }
30            })
31        }
32        task.resume()
33        return URLSessionTaskWrapper(wrapped: task)
34    }
35}
36
37private extension URLSessionHTTPClient {
38    struct UnexpectedValuesRepresentation: Error {}
39    
40    struct URLSessionTaskWrapper: HTTPClientTask {
41        let wrapped: URLSessionTask
42        
43        func cancel() {
44            wrapped.cancel()
45        }
46    }
47}
48extension HTTPClient {
49    typealias Publisher = AnyPublisher&lt;(data: Data, response: HTTPURLResponse), Error&gt;
50
51    func dispatchPublisher(for request: URLRequest) -&gt; Publisher {
52        var task: HTTPClientTask?
53
54        return Deferred {
55            Future { completion in
56                task = self.dispatch(request, completion: completion)
57            }
58        }
59        .handleEvents(receiveCancel: { task?.cancel() })
60        .eraseToAnyPublisher()
61    }
62}
63extension HTTPClient {
64    func dispatch(_ request: URLRequest) async -&gt; HTTPClient.Result {
65
66        let task = Task { () -&gt; (data: Data, response: HTTPURLResponse) in
67            return try await withCheckedThrowingContinuation { continuation in
68                self.dispatch(request) { result in
69                    switch result {
70                    case let .success(values): continuation.resume(returning: values)
71                    case let .failure(error): continuation.resume(throwing: error)
72                    }
73                }
74            }
75        }
76
77        do {
78            let output = try await task.value
79            return .success(output)
80        } catch {
81            return .failure(error)
82        }
83    }
84}
85let data = tryData(contentsOf: fileURL)
86let data = try await Data(contentsOf: fileURL)
87

For the developer, it's the same coding style, once the operation finishes, they'll either have a data variable to use, or they'll be receiving an error.

In both cases, there's no cancellation built in, as the operation is synchronous from the developer's perspective. The major difference is that the await-ed call doesn't block the caller thread, but on the other hand once the control flow returns it might well be that the code continues executing on a different thread.

Now, if you need support for cancellation, then you'll have to store somewhere some identifiable data that can be used to cancel the operation.

If you'll want to store those identifiers from the caller scope, then you'll need to split your operation in two: initialization, and execution.

Something along the lines of

1
2protocol HTTPClientTask {
3    func cancel()
4}
5
6protocol HTTPClient {
7    typealias Result = Swift.Result&lt;(data: Data, response: HTTPURLResponse), Error&gt;
8    @discardableResult
9    func dispatch(_ request: URLRequest, completion: @escaping (Result) -&gt; Void) -&gt; HTTPClientTask
10}
11
12final class URLSessionHTTPClient: HTTPClient {
13    
14    private let session: URLSession
15    
16    init(session: URLSession) {
17        self.session = session
18    }
19    
20    func dispatch(_ request: URLRequest, completion: @escaping (HTTPClient.Result) -&gt; Void) -&gt; HTTPClientTask {
21        let task = session.dataTask(with: request) { data, response, error in
22            completion(Result {
23                if let error = error {
24                    throw error
25                } else if let data = data, let response = response as? HTTPURLResponse {
26                    return (data, response)
27                } else {
28                    throw UnexpectedValuesRepresentation()
29                }
30            })
31        }
32        task.resume()
33        return URLSessionTaskWrapper(wrapped: task)
34    }
35}
36
37private extension URLSessionHTTPClient {
38    struct UnexpectedValuesRepresentation: Error {}
39    
40    struct URLSessionTaskWrapper: HTTPClientTask {
41        let wrapped: URLSessionTask
42        
43        func cancel() {
44            wrapped.cancel()
45        }
46    }
47}
48extension HTTPClient {
49    typealias Publisher = AnyPublisher&lt;(data: Data, response: HTTPURLResponse), Error&gt;
50
51    func dispatchPublisher(for request: URLRequest) -&gt; Publisher {
52        var task: HTTPClientTask?
53
54        return Deferred {
55            Future { completion in
56                task = self.dispatch(request, completion: completion)
57            }
58        }
59        .handleEvents(receiveCancel: { task?.cancel() })
60        .eraseToAnyPublisher()
61    }
62}
63extension HTTPClient {
64    func dispatch(_ request: URLRequest) async -&gt; HTTPClient.Result {
65
66        let task = Task { () -&gt; (data: Data, response: HTTPURLResponse) in
67            return try await withCheckedThrowingContinuation { continuation in
68                self.dispatch(request) { result in
69                    switch result {
70                    case let .success(values): continuation.resume(returning: values)
71                    case let .failure(error): continuation.resume(throwing: error)
72                    }
73                }
74            }
75        }
76
77        do {
78            let output = try await task.value
79            return .success(output)
80        } catch {
81            return .failure(error)
82        }
83    }
84}
85let data = tryData(contentsOf: fileURL)
86let data = try await Data(contentsOf: fileURL)
87extension HTTPClient {
88    // note that this is not async
89    func task(for request: URLRequest) -&gt; HTTPClientTask {
90        // ...
91    }
92}
93
94class HTTPClientTask {
95    func dispatch() async -&gt; HTTPClient.Result {
96        // ...
97    }
98}
99
100let task = httpClient.task(for: urlRequest)
101self.theTask = task
102let result = await task.dispatch()
103
104// somewhere outside the await scope
105self.theTask.cancel()
106

Source https://stackoverflow.com/questions/69506002

QUESTION

How to configure GKE Autopilot w/Envoy & gRPC-Web

Asked 2021-Dec-14 at 20:31

I have an application running on my local machine that uses React -> gRPC-Web -> Envoy -> Go app and everything runs with no problems. I'm trying to deploy this using GKE Autopilot and I just haven't been able to get the configuration right. I'm new to all of GCP/GKE, so I'm looking for help to figure out where I'm going wrong.

I was following this doc initially, even though I only have one gRPC service: https://cloud.google.com/architecture/exposing-grpc-services-on-gke-using-envoy-proxy

From what I've read, GKE Autopilot mode requires using External HTTP(s) load balancing instead of Network Load Balancing as described in the above solution, so I've been trying to get that to work. After a variety of attempts, my current strategy has an Ingress, BackendConfig, Service, and Deployment. The deployment has three containers: my app, an Envoy sidecar to transform the gRPC-Web requests and responses, and a cloud SQL proxy sidecar. I eventually want to be using TLS, but for now, I left that out so it wouldn't complicate things even more.

When I apply all of the configs, the backend service shows one backend in one zone and the health check fails. The health check is set for port 8080 and path /healthz which is what I think I've specified in the deployment config, but I'm suspicious because when I look at the details for the envoy-sidecar container, it shows the Readiness probe as: http-get HTTP://:0/healthz headers=x-envoy-livenessprobe:healthz. Does ":0" just mean it's using the default address and port for the container, or does indicate a config problem?

I've been reading various docs and just haven't been able to piece it all together. Is there an example somewhere that shows how this can be done? I've been searching and haven't found one.

My current configs are:

1apiVersion: networking.k8s.io/v1
2kind: Ingress
3metadata:
4  name: grammar-games-ingress
5  #annotations:
6    # If the class annotation is not specified it defaults to &quot;gce&quot;.
7    # kubernetes.io/ingress.class: &quot;gce&quot;
8    # kubernetes.io/ingress.global-static-ip-name: &lt;IP addr&gt;
9spec:
10  defaultBackend:
11    service:
12      name: grammar-games-core
13      port:
14        number: 80
15---
16apiVersion: cloud.google.com/v1
17kind: BackendConfig
18metadata:
19  name: grammar-games-bec
20  annotations:
21    cloud.google.com/neg: '{&quot;ingress&quot;: true}'
22spec:
23  sessionAffinity:
24    affinityType: &quot;CLIENT_IP&quot;  
25  healthCheck:
26    checkIntervalSec: 15
27    port: 8080
28    type: HTTP
29    requestPath: /healthz
30  timeoutSec: 60
31---
32apiVersion: v1
33kind: Service
34metadata:
35  name: grammar-games-core
36  annotations:
37    cloud.google.com/neg: '{&quot;ingress&quot;: true}'
38    cloud.google.com/app-protocols: '{&quot;http&quot;:&quot;HTTP&quot;}'
39    cloud.google.com/backend-config: '{&quot;default&quot;: &quot;grammar-games-bec&quot;}'
40spec:
41  type: ClusterIP
42  selector:
43    app: grammar-games-core
44  ports:
45  - name: http
46    protocol: TCP
47    port: 80
48    targetPort: 8080
49---
50apiVersion: apps/v1
51kind: Deployment
52metadata:
53  name: grammar-games-core
54spec:
55  # Two replicas for right now, just so I can see how RPC calls get directed.
56  # replicas: 2
57  selector:
58    matchLabels:
59      app: grammar-games-core
60  template:
61    metadata:
62      labels:
63        app: grammar-games-core
64    spec:
65      serviceAccountName: grammar-games-core-k8sa
66      containers:
67      - name: grammar-games-core
68        image: gcr.io/grammar-games/grammar-games-core:1.1.2
69        command:
70          - &quot;/bin/grammar-games-core&quot;
71        ports:
72        - containerPort: 52001
73        env:
74        - name: GAMESDB_USER
75          valueFrom:
76            secretKeyRef:
77              name: gamesdb-config
78              key: username
79        - name: GAMESDB_PASSWORD
80          valueFrom:
81            secretKeyRef:
82              name: gamesdb-config
83              key: password
84        - name: GAMESDB_DB_NAME
85          valueFrom:
86            secretKeyRef:
87              name: gamesdb-config
88              key: db-name 
89        - name: GRPC_SERVER_PORT
90          value: '52001'
91        - name: GAMES_LOG_FILE_PATH
92          value: ''
93        - name: GAMESDB_LOG_LEVEL
94          value: 'debug'
95        resources:
96          requests:
97            # The proxy's memory use scales linearly with the number of active
98            # connections. Fewer open connections will use less memory. Adjust
99            # this value based on your application's requirements.
100            memory: &quot;2Gi&quot;
101            # The proxy's CPU use scales linearly with the amount of IO between
102            # the database and the application. Adjust this value based on your
103            # application's requirements.
104            cpu:    &quot;1&quot;
105        readinessProbe:
106          exec:
107            command: [&quot;/bin/grpc_health_probe&quot;, &quot;-addr=:52001&quot;]
108          initialDelaySeconds: 5
109      - name: cloud-sql-proxy
110        # It is recommended to use the latest version of the Cloud SQL proxy
111        # Make sure to update on a regular schedule!
112        image: gcr.io/cloudsql-docker/gce-proxy:1.24.0
113        command:
114          - &quot;/cloud_sql_proxy&quot;
115
116          # If connecting from a VPC-native GKE cluster, you can use the
117          # following flag to have the proxy connect over private IP
118          # - &quot;-ip_address_types=PRIVATE&quot;
119
120          # Replace DB_PORT with the port the proxy should listen on
121          # Defaults: MySQL: 3306, Postgres: 5432, SQLServer: 1433
122          - &quot;-instances=grammar-games:us-east1:grammar-games-db=tcp:3306&quot;
123        securityContext:
124          # The default Cloud SQL proxy image runs as the
125          # &quot;nonroot&quot; user and group (uid: 65532) by default.
126          runAsNonRoot: true
127        # Resource configuration depends on an application's requirements. You
128        # should adjust the following values based on what your application
129        # needs. For details, see https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
130        resources:
131          requests:
132            # The proxy's memory use scales linearly with the number of active
133            # connections. Fewer open connections will use less memory. Adjust
134            # this value based on your application's requirements.
135            memory: &quot;2Gi&quot;
136            # The proxy's CPU use scales linearly with the amount of IO between
137            # the database and the application. Adjust this value based on your
138            # application's requirements.
139            cpu:    &quot;1&quot;
140      - name: envoy-sidecar
141        image: envoyproxy/envoy:v1.20-latest
142        ports:
143        - name: http
144          containerPort: 8080
145        resources:
146          requests:
147            cpu: 10m
148            ephemeral-storage: 256Mi
149            memory: 256Mi
150        volumeMounts:
151        - name: config
152          mountPath: /etc/envoy
153        readinessProbe:
154          httpGet:
155            port: http
156            httpHeaders:
157            - name: x-envoy-livenessprobe
158              value: healthz
159            path: /healthz
160            scheme: HTTP
161      volumes:
162      - name: config
163        configMap:
164          name: envoy-sidecar-conf      
165---
166apiVersion: v1
167kind: ConfigMap
168metadata:
169  name: envoy-sidecar-conf
170data:
171  envoy.yaml: |
172    static_resources:
173      listeners:
174      - name: listener_0
175        address:
176          socket_address:
177            address: 0.0.0.0
178            port_value: 8080
179        filter_chains:
180        - filters:
181          - name: envoy.filters.network.http_connection_manager
182            typed_config:
183              &quot;@type&quot;: type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
184              access_log:
185              - name: envoy.access_loggers.stdout
186                typed_config:
187                  &quot;@type&quot;: type.googleapis.com/envoy.extensions.access_loggers.stream.v3.StdoutAccessLog
188              codec_type: AUTO
189              stat_prefix: ingress_http
190              route_config:
191                name: local_route
192                virtual_hosts:
193                - name: http
194                  domains:
195                  - &quot;*&quot;
196                  routes:
197                  - match:
198                      prefix: &quot;/grammar_games_protos.GrammarGames/&quot;
199                    route:
200                      cluster: grammar-games-core-grpc
201                  cors:
202                    allow_origin_string_match:
203                    - prefix: &quot;*&quot;
204                    allow_methods: GET, PUT, DELETE, POST, OPTIONS
205                    allow_headers: keep-alive,user-agent,cache-control,content-type,content-transfer-encoding,custom-header-1,x-accept-content-transfer-encoding,x-accept-response-streaming,x-user-agent,x-grpc-web,grpc-timeout
206                    max_age: &quot;1728000&quot;
207                    expose_headers: custom-header-1,grpc-status,grpc-message
208              http_filters:
209              - name: envoy.filters.http.health_check
210                typed_config:
211                  &quot;@type&quot;: type.googleapis.com/envoy.extensions.filters.http.health_check.v3.HealthCheck
212                  pass_through_mode: false
213                  headers:
214                  - name: &quot;:path&quot;
215                    exact_match: &quot;/healthz&quot;
216                  - name: &quot;x-envoy-livenessprobe&quot;
217                    exact_match: &quot;healthz&quot;
218              - name: envoy.filters.http.grpc_web
219              - name: envoy.filters.http.cors
220              - name: envoy.filters.http.router
221                typed_config: {}
222      clusters:
223      - name: grammar-games-core-grpc
224        connect_timeout: 0.5s
225        type: logical_dns
226        lb_policy: ROUND_ROBIN
227        http2_protocol_options: {}
228        load_assignment:
229          cluster_name: grammar-games-core-grpc
230          endpoints:
231          - lb_endpoints:
232            - endpoint:
233                address:
234                  socket_address:
235                    address: 0.0.0.0
236                    port_value: 52001
237        health_checks:
238          timeout: 1s
239          interval: 10s
240          unhealthy_threshold: 2
241          healthy_threshold: 2
242          grpc_health_check: {}
243    admin:
244      access_log_path: /dev/stdout
245      address:
246        socket_address:
247          address: 127.0.0.1
248          port_value: 8090
249
250

ANSWER

Answered 2021-Oct-14 at 22:35

Here is some documentation about Setting up HTTP(S) Load Balancing with Ingress. This tutorial shows how to run a web application behind an external HTTP(S) load balancer by configuring the Ingress resource.

Related to Creating a HTTP Load Balancer on GKE using Ingress, I found two threads where instances created are marked as unhealthy.

In the first one, they mention the necessity to manually enable a firewall rule to allow http load balancer ip range to pass health check.

In the second one, they mention that the Pod’s spec must also include containerPort. Example:

1apiVersion: networking.k8s.io/v1
2kind: Ingress
3metadata:
4  name: grammar-games-ingress
5  #annotations:
6    # If the class annotation is not specified it defaults to &quot;gce&quot;.
7    # kubernetes.io/ingress.class: &quot;gce&quot;
8    # kubernetes.io/ingress.global-static-ip-name: &lt;IP addr&gt;
9spec:
10  defaultBackend:
11    service:
12      name: grammar-games-core
13      port:
14        number: 80
15---
16apiVersion: cloud.google.com/v1
17kind: BackendConfig
18metadata:
19  name: grammar-games-bec
20  annotations:
21    cloud.google.com/neg: '{&quot;ingress&quot;: true}'
22spec:
23  sessionAffinity:
24    affinityType: &quot;CLIENT_IP&quot;  
25  healthCheck:
26    checkIntervalSec: 15
27    port: 8080
28    type: HTTP
29    requestPath: /healthz
30  timeoutSec: 60
31---
32apiVersion: v1
33kind: Service
34metadata:
35  name: grammar-games-core
36  annotations:
37    cloud.google.com/neg: '{&quot;ingress&quot;: true}'
38    cloud.google.com/app-protocols: '{&quot;http&quot;:&quot;HTTP&quot;}'
39    cloud.google.com/backend-config: '{&quot;default&quot;: &quot;grammar-games-bec&quot;}'
40spec:
41  type: ClusterIP
42  selector:
43    app: grammar-games-core
44  ports:
45  - name: http
46    protocol: TCP
47    port: 80
48    targetPort: 8080
49---
50apiVersion: apps/v1
51kind: Deployment
52metadata:
53  name: grammar-games-core
54spec:
55  # Two replicas for right now, just so I can see how RPC calls get directed.
56  # replicas: 2
57  selector:
58    matchLabels:
59      app: grammar-games-core
60  template:
61    metadata:
62      labels:
63        app: grammar-games-core
64    spec:
65      serviceAccountName: grammar-games-core-k8sa
66      containers:
67      - name: grammar-games-core
68        image: gcr.io/grammar-games/grammar-games-core:1.1.2
69        command:
70          - &quot;/bin/grammar-games-core&quot;
71        ports:
72        - containerPort: 52001
73        env:
74        - name: GAMESDB_USER
75          valueFrom:
76            secretKeyRef:
77              name: gamesdb-config
78              key: username
79        - name: GAMESDB_PASSWORD
80          valueFrom:
81            secretKeyRef:
82              name: gamesdb-config
83              key: password
84        - name: GAMESDB_DB_NAME
85          valueFrom:
86            secretKeyRef:
87              name: gamesdb-config
88              key: db-name 
89        - name: GRPC_SERVER_PORT
90          value: '52001'
91        - name: GAMES_LOG_FILE_PATH
92          value: ''
93        - name: GAMESDB_LOG_LEVEL
94          value: 'debug'
95        resources:
96          requests:
97            # The proxy's memory use scales linearly with the number of active
98            # connections. Fewer open connections will use less memory. Adjust
99            # this value based on your application's requirements.
100            memory: &quot;2Gi&quot;
101            # The proxy's CPU use scales linearly with the amount of IO between
102            # the database and the application. Adjust this value based on your
103            # application's requirements.
104            cpu:    &quot;1&quot;
105        readinessProbe:
106          exec:
107            command: [&quot;/bin/grpc_health_probe&quot;, &quot;-addr=:52001&quot;]
108          initialDelaySeconds: 5
109      - name: cloud-sql-proxy
110        # It is recommended to use the latest version of the Cloud SQL proxy
111        # Make sure to update on a regular schedule!
112        image: gcr.io/cloudsql-docker/gce-proxy:1.24.0
113        command:
114          - &quot;/cloud_sql_proxy&quot;
115
116          # If connecting from a VPC-native GKE cluster, you can use the
117          # following flag to have the proxy connect over private IP
118          # - &quot;-ip_address_types=PRIVATE&quot;
119
120          # Replace DB_PORT with the port the proxy should listen on
121          # Defaults: MySQL: 3306, Postgres: 5432, SQLServer: 1433
122          - &quot;-instances=grammar-games:us-east1:grammar-games-db=tcp:3306&quot;
123        securityContext:
124          # The default Cloud SQL proxy image runs as the
125          # &quot;nonroot&quot; user and group (uid: 65532) by default.
126          runAsNonRoot: true
127        # Resource configuration depends on an application's requirements. You
128        # should adjust the following values based on what your application
129        # needs. For details, see https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
130        resources:
131          requests:
132            # The proxy's memory use scales linearly with the number of active
133            # connections. Fewer open connections will use less memory. Adjust
134            # this value based on your application's requirements.
135            memory: &quot;2Gi&quot;
136            # The proxy's CPU use scales linearly with the amount of IO between
137            # the database and the application. Adjust this value based on your
138            # application's requirements.
139            cpu:    &quot;1&quot;
140      - name: envoy-sidecar
141        image: envoyproxy/envoy:v1.20-latest
142        ports:
143        - name: http
144          containerPort: 8080
145        resources:
146          requests:
147            cpu: 10m
148            ephemeral-storage: 256Mi
149            memory: 256Mi
150        volumeMounts:
151        - name: config
152          mountPath: /etc/envoy
153        readinessProbe:
154          httpGet:
155            port: http
156            httpHeaders:
157            - name: x-envoy-livenessprobe
158              value: healthz
159            path: /healthz
160            scheme: HTTP
161      volumes:
162      - name: config
163        configMap:
164          name: envoy-sidecar-conf      
165---
166apiVersion: v1
167kind: ConfigMap
168metadata:
169  name: envoy-sidecar-conf
170data:
171  envoy.yaml: |
172    static_resources:
173      listeners:
174      - name: listener_0
175        address:
176          socket_address:
177            address: 0.0.0.0
178            port_value: 8080
179        filter_chains:
180        - filters:
181          - name: envoy.filters.network.http_connection_manager
182            typed_config:
183              &quot;@type&quot;: type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
184              access_log:
185              - name: envoy.access_loggers.stdout
186                typed_config:
187                  &quot;@type&quot;: type.googleapis.com/envoy.extensions.access_loggers.stream.v3.StdoutAccessLog
188              codec_type: AUTO
189              stat_prefix: ingress_http
190              route_config:
191                name: local_route
192                virtual_hosts:
193                - name: http
194                  domains:
195                  - &quot;*&quot;
196                  routes:
197                  - match:
198                      prefix: &quot;/grammar_games_protos.GrammarGames/&quot;
199                    route:
200                      cluster: grammar-games-core-grpc
201                  cors:
202                    allow_origin_string_match:
203                    - prefix: &quot;*&quot;
204                    allow_methods: GET, PUT, DELETE, POST, OPTIONS
205                    allow_headers: keep-alive,user-agent,cache-control,content-type,content-transfer-encoding,custom-header-1,x-accept-content-transfer-encoding,x-accept-response-streaming,x-user-agent,x-grpc-web,grpc-timeout
206                    max_age: &quot;1728000&quot;
207                    expose_headers: custom-header-1,grpc-status,grpc-message
208              http_filters:
209              - name: envoy.filters.http.health_check
210                typed_config:
211                  &quot;@type&quot;: type.googleapis.com/envoy.extensions.filters.http.health_check.v3.HealthCheck
212                  pass_through_mode: false
213                  headers:
214                  - name: &quot;:path&quot;
215                    exact_match: &quot;/healthz&quot;
216                  - name: &quot;x-envoy-livenessprobe&quot;
217                    exact_match: &quot;healthz&quot;
218              - name: envoy.filters.http.grpc_web
219              - name: envoy.filters.http.cors
220              - name: envoy.filters.http.router
221                typed_config: {}
222      clusters:
223      - name: grammar-games-core-grpc
224        connect_timeout: 0.5s
225        type: logical_dns
226        lb_policy: ROUND_ROBIN
227        http2_protocol_options: {}
228        load_assignment:
229          cluster_name: grammar-games-core-grpc
230          endpoints:
231          - lb_endpoints:
232            - endpoint:
233                address:
234                  socket_address:
235                    address: 0.0.0.0
236                    port_value: 52001
237        health_checks:
238          timeout: 1s
239          interval: 10s
240          unhealthy_threshold: 2
241          healthy_threshold: 2
242          grpc_health_check: {}
243    admin:
244      access_log_path: /dev/stdout
245      address:
246        socket_address:
247          address: 127.0.0.1
248          port_value: 8090
249
250spec:
251  containers:
252  - name: nginx
253    image: nginx:1.7.9
254    ports:
255    - containerPort: 80
256

Adding to that, here is some more documentation about:

Source https://stackoverflow.com/questions/69560536

Community Discussions contain sources that include Stack Exchange Network

Microk8s dashboard using nginx-ingress via http not working (Error: `no matches for kind "Ingress" in version "extensions/v1beta1"`)

Laravel Homestead - page stopped working ERR_ADDRESS_UNREACHABLE

Accessing PostgreSQL (on wsl2) from DBeaver (on Windows) fails: "Connection refused: connect"

Why URL re-writing is not working when I do not use slash at the end?

Standard compliant host to network endianess conversion

How to configure proxy in emulators in new versions of Android Studio?

Unable to log egress traffic HTTP requests with the istio-proxy

Dynamodb local web shell does not load

Cancelling an async/await Network Request

How to configure GKE Autopilot w/Envoy & gRPC-Web

QUESTION

Microk8s dashboard using nginx-ingress via http not working (Error: `no matches for kind "Ingress" in version "extensions/v1beta1"`)

Asked 2022-Apr-01 at 07:26

I have microk8s v1.22.2 running on Ubuntu 20.04.3 LTS.

Output from /etc/hosts:

1127.0.0.1 localhost
2127.0.1.1 main
3

Excerpt from microk8s status:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9

I checked for the running dashboard (kubectl get all --all-namespaces):

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39

I want to expose the microk8s dashboard within my local network to access it through http://main/dashboard/

To do so, I did the following nano ingress.yaml:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56

Enabling the ingress-config through kubectl apply -f ingress.yaml gave the following error:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
57

Help would be much appreciated, thanks!

Update: @harsh-manvar pointed out a mismatch in the config version. I have rewritten ingress.yaml to a very stripped down version:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
57apiVersion: networking.k8s.io/v1
58kind: Ingress
59metadata:
60  name: dashboard
61  namespace: kube-system
62spec:
63  rules:
64  - http:
65      paths:
66      - path: /dashboard
67        pathType: Prefix
68        backend:
69          service:
70            name: kubernetes-dashboard
71            port:
72              number: 443
73

Applying this works. Also, the ingress rule gets created.

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.103   &lt;none&gt;        443/TCP    22m
21kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.197   &lt;none&gt;        8000/TCP   22m
22
23NAMESPACE     NAME                                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
24kube-system   daemonset.apps/calico-node                         1         1         1       1            1           kubernetes.io/os=linux   23m
25ingress       daemonset.apps/nginx-ingress-microk8s-controller   1         1         1       1            1           &lt;none&gt;                   22m
26
27NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
28kube-system   deployment.apps/calico-kube-controllers     1/1     1            1           23m
29kube-system   deployment.apps/metrics-server              1/1     1            1           22m
30kube-system   deployment.apps/kubernetes-dashboard        1/1     1            1           22m
31kube-system   deployment.apps/dashboard-metrics-scraper   1/1     1            1           22m
32
33NAMESPACE     NAME                                                   DESIRED   CURRENT   READY   AGE
34kube-system   replicaset.apps/calico-kube-controllers-69d7f794d9     0         0         0       23m
35kube-system   replicaset.apps/calico-kube-controllers-f744bf684      1         1         1       23m
36kube-system   replicaset.apps/metrics-server-85df567dd8              1         1         1       22m
37kube-system   replicaset.apps/kubernetes-dashboard-59699458b         1         1         1       21m
38kube-system   replicaset.apps/dashboard-metrics-scraper-58d4977855   1         1         1       21m
39apiVersion: extensions/v1beta1
40kind: Ingress
41metadata:
42  annotations:
43    kubernetes.io/ingress.class: public
44    nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTPS&quot;
45  name: dashboard
46  namespace: kube-system
47spec:
48  rules:
49  - host: main
50    http:
51      paths:
52      - backend:
53          serviceName: kubernetes-dashboard
54          servicePort: 443
55        path: /
56error: unable to recognize &quot;ingress.yaml&quot;: no matches for kind &quot;Ingress&quot; in version &quot;extensions/v1beta1&quot;
57apiVersion: networking.k8s.io/v1
58kind: Ingress
59metadata:
60  name: dashboard
61  namespace: kube-system
62spec:
63  rules:
64  - http:
65      paths:
66      - path: /dashboard
67        pathType: Prefix
68        backend:
69          service:
70            name: kubernetes-dashboard
71            port:
72              number: 443
73NAMESPACE     NAME        CLASS    HOSTS   ADDRESS     PORTS   AGE
74kube-system   dashboard   public   *       127.0.0.1   80      11m
75

However, when I access the dashboard through http://<ip-of-kubernetes-master>/dashboard, I get a 400 error.

Log from the ingress controller:

1127.0.0.1 localhost
2127.0.1.1 main
3addons:
4  enabled:
5    dashboard            # The Kubernetes dashboard
6    ha-cluster           # Configure high availability on the current node
7    ingress              # Ingress controller for external access
8    metrics-server       # K8s Metrics Server for API access to service metrics
9NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
10kube-system   pod/calico-node-2jltr                            1/1     Running   0          23m
11kube-system   pod/calico-kube-controllers-f744bf684-d77hv      1/1     Running   0          23m
12kube-system   pod/metrics-server-85df567dd8-jd6gj              1/1     Running   0          22m
13kube-system   pod/kubernetes-dashboard-59699458b-pb5jb         1/1     Running   0          21m
14kube-system   pod/dashboard-metrics-scraper-58d4977855-94nsp   1/1     Running   0          21m
15ingress       pod/nginx-ingress-microk8s-controller-qf5pm      1/1     Running   0          21m
16
17NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
18default       service/kubernetes                  ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP    23m
19kube-system   service/metrics-server              ClusterIP   10.152.183.81    &lt;none&gt;        443/TCP    22m
20kub