Skip to content

Commit

Permalink
Merge pull request #541 from 1Shubham7/blog-v1.14
Browse files Browse the repository at this point in the history
New Blog for Release KubeEdge v1.14
  • Loading branch information
kubeedge-bot authored May 17, 2024
2 parents e02c79e + 2d13695 commit 138f88c
Showing 1 changed file with 80 additions and 0 deletions.
80 changes: 80 additions & 0 deletions blog/release-v1.14/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
---
authors:
- KubeEdge SIG Release
categories:
- General
- Announcements
date: 2023-05-15
draft: false
lastmod: 2023-05-15
summary: KubeEdge v1.14 is live!
tags:
- KubeEdge
- kubeedge
- edge computing
- kubernetes edge computing
- K8s edge orchestration
- edge computing platform
- cloud native
- iot
- iiot
- release v1.14
- v1.14
title: KubeEdge v1.14 is live!
---

On July 1, 2023, KubeEdge released v1.14. The new version introduces several enhanced features, significantly improving security, reliability, and user experience.

## v1.14 What's New

- [Support Authentication and Authorization for Kube-API Endpoint for Applications On Edge Nodes](#support-authentication-and-authorization-for-kube-api-endpoint-for-applications-on-edge-nodes)

- [Support Cluster Scope Resource Reliable Delivery to Edge Node](#support-cluster-scope-resource-reliable-delivery-to-edge-node)

- [Upgrade Kubernetes Dependency to v1.24.14](#upgrade-kubernetes-dependency-to-v12414)

- [Support Kubectl Attach to Container Running on Edge Node](#support-kubectl-attach-to-container-running-on-edge-node)

- [Alpha version of KubeEdge Dashboard](#alpha-version-of-kubeedge-dashboard)

## Release Highlights

### Support Authentication and Authorization for Kube-API Endpoint for Applications On Edge Nodes

The Kube-API endpoint for edge applications is implemented through MetaServer in edegcore. However, in previous versions, the authentication and authorization of Kube-API endpoint are performed in the cloud, which prevents authentication and authorization especially in offline scenarios on the edge node.

In this release, the authentication and authorization functionalities are implemented within the MetaServer at edge, which allows for limiting the access permissions of edge applications when accessing Kube-API endpoint at edge.

Refer to the link for more details. ([#4802](https://github.com/kubeedge/kubeedge/pull/4802))

### Support Cluster Scope Resource Reliable Delivery to Edge Node

The cluster scope resource can guarantee deliver to the edge side reliably since this release, especially include using list-watch global resources, the cluster scope resource can be delivered to the edge side reliably, and the edge applications can work normally.

Refer to the link for more details. ([#4758](https://github.com/kubeedge/kubeedge/pull/4758))

### Upgrade Kubernetes Dependency to v1.24.14

Upgrade the vendered kubernetes version to v1.24.14, users are now able to use the feature of new version on the cloud and on the edge side.

:::note
The dockershim has been removed, which means users can't use docker runtime directly in this release.
:::

Refer to the link for more details. ([#4789](https://github.com/kubeedge/kubeedge/pull/4789))

### Support Kubectl Attach to Container Running on Edge Node

KubeEdge already support `kubectl logs/exe` command, `kubectl attach` is supported in this release. `kubectl attach` command can attach to a running container at edge node. Users can execute these commands in the cloud and no need to operate on the edge nodes.

Refer to the link for more details. ([#4734](https://github.com/kubeedge/kubeedge/pull/4734))

### Alpha version of KubeEdge Dashboard

KubeEdge dashboard provides a graphical user interface (GUI) for managing and monitoring your KubeEdge clusters. It allows users to manage edge applications running in the cluster and troubleshoot them.

Refer to the link for more details. (https://github.com/kubeedge/dashboard)

## Important Steps before Upgrading

- On KubeEdge v1.14, EdgeCore has removed the dockeshim support, so users can only use `remote` type runtime, and uses `containerd` runtime by default. If you want to use `docker` runtime, you must first set `edged.containerRuntime=remote` and corresponding docker configuration like `RemoteRuntimeEndpoint` and `RemoteImageEndpoint` in EdgeCore, then install the cri-dockerd tools as docs below: https://github.com/kubeedge/kubeedge/issues/4843

0 comments on commit 138f88c

Please sign in to comment.