update blog links (kubevela#1021)

Signed-off-by: Arhell <[email protected]> Signed-off-by: Arhell <[email protected]>
jxs1211 · Oct 28, 2022 · fd9c214 · fd9c214
1 parent 8fbf3a1
commit fd9c214
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 7 deletions.
diff --git a/blog/2022-04-01-offline-deployment-practice.md b/blog/2022-04-01-offline-deployment-practice.md
@@ -2,7 +2,7 @@
 title: China Merchants Bank's Practice on Offline Installation with KubeVela 
 author: Xiangbo Ma
 author_title: (Cloud platform development team)
-author_url: http://www.cmbchina.com/
+author_url: https://www.cmbchina.com/
 author_image_url: /img/china-merchants-bank.jpg
 tags: [ KubeVela , "use-case"]
 description: ""

diff --git a/blog/2022-06-21-release-1.4.md b/blog/2022-06-21-release-1.4.md
@@ -10,7 +10,7 @@ image: https://raw.githubusercontent.com/oam-dev/KubeVela.io/main/docs/resources
 hide_table_of_contents: false
 ---
 
-[KubeVela](http://kubevela.net/) is a modern software delivery control panel. The goal is to make application deployment and O&M simpler, more agile, and more reliable in today's hybrid multi-cloud environment. Since the release of [Version 1.1](https://kubevela.net/blog/2021/10/08/blog-1.1), the KubeVela architecture has naturally solved the delivery problems of enterprises in the hybrid multi-cloud environments and has provided sufficient scalability based on the OAM model, which makes it win the favor of many enterprise developers. This also accelerates the iteration of KubeVela. 
+[KubeVela](https://kubevela.net/) is a modern software delivery control panel. The goal is to make application deployment and O&M simpler, more agile, and more reliable in today's hybrid multi-cloud environment. Since the release of [Version 1.1](https://kubevela.net/blog/2021/10/08/blog-1.1), the KubeVela architecture has naturally solved the delivery problems of enterprises in the hybrid multi-cloud environments and has provided sufficient scalability based on the OAM model, which makes it win the favor of many enterprise developers. This also accelerates the iteration of KubeVela. 
 
 In [Version 1.2](https://kubevela.net/blog/2022/01/27/blog-1.2), we released an out-of-the-box visual console, which allows the end user to publish and manage diverse workloads through the interface. The release of [Version 1.3](https://kubevela.net/blog/2022/04/06/multi-cluster-management) improved the expansion system with the OAM model as the core and provides rich plug-in functions. It also provides users with a large number of enterprise-level functions, including LDAP permission authentication, and provides more convenience for enterprise integration. You can obtain more than 30 addons in the [addons registry](https://github.com/kubevela/catalog) of the KubeVela community. There are well-known CNCF projects (such as argocd, istio, and traefik), database middleware (such as Flink and MySQL), and hundreds of cloud vendor resources. 
 

diff --git a/blog/2022-08-17-helm-rollout.md b/blog/2022-08-17-helm-rollout.md
@@ -37,7 +37,7 @@ The image above is a typical canary rollout scenario, *so how do we complete the
 
 The two solutions are complex with considerable modification costs, especially **when your Helm chart is a third-party component that cannot be modified or cannot maintain a Helm chart.** Even if the two are modified, there are still stability risks compared to the original simple workload model. The reason is that **Helm is only a package management tool, and it is incompatible with the canary rollout or workloads management.**
 
-When we have in-depth communication with large number of users in the community, we find that most users' applications are not complicated, among which the most are classic types (such as Deployment and StatefulSet). Therefore, through the powerful addon mechanism of [KubeVela](http://kubevela.net/) and the [OpenKruise](https://openkruise.io/) community, we have made a canary rollout KubeVela Addon for these qualified types. **This addon helps you easily complete the canary rollout of the Helm chart without any migration and modification.** Also, if your Helm chart is more complicated, you can customize an addon for your scenario to get the same experience.
+When we have in-depth communication with large number of users in the community, we find that most users' applications are not complicated, among which the most are classic types (such as Deployment and StatefulSet). Therefore, through the powerful addon mechanism of [KubeVela](https://kubevela.net/) and the [OpenKruise](https://openkruise.io/) community, we have made a canary rollout KubeVela Addon for these qualified types. **This addon helps you easily complete the canary rollout of the Helm chart without any migration and modification.** Also, if your Helm chart is more complicated, you can customize an addon for your scenario to get the same experience.
 Let's take you through a practical example (using Deployment Workload as an example) to get a glimpse of the complete process.
 
 ## Use KubeVela for Canary Rollout

diff --git a/blog/2022-09-17-release.1.5.md b/blog/2022-09-17-release.1.5.md
@@ -40,7 +40,7 @@ Starting from version 1.5, addon developers could have a better experience. Addo
 
 - Addon metadata definition files like metadata.yaml and readme.md describe the basic information and environment requirements of the addon.  
 
-Please refer to [the document](http://kubevela.net/docs/platform-engineers/addon/intro) for details.
+Please refer to [the document](https://kubevela.net/docs/platform-engineers/addon/intro) for details.
 
 Here is an example of integrating the delivery capability of the Helm Chart package. Currently, projects in the community like FluxCD or ArgoCD provide the atomic capability of deploying Chart packages. Their implementations are different, and each has its advantages. For KubeVela users, these two projects can be introduced through addons. As shown in Figure 2, we need to define a standard API for the end user to expose the necessary parameters to the end user according to the specific situation of the enterprise. 
 
@@ -82,7 +82,7 @@ Figure 5 shows the monitoring dashboard of the Kubernetes API Server service con
 
 In the next release, the community will gradually integrate the unified description and delivery of application observability into the application delivery process. It covers Metric, Logger, and Tracing data acquisition, intermediate processing and transmission, storage and analysis, alerts and visualizations, and applications to the complete process of the application release workflow. 
 
-Reference: http://kubevela.net/docs/platform-engineers/operations/observability
+Reference: https://kubevela.net/docs/platform-engineers/operations/observability
 
 
 ### Integrate CloudShell for CLI and UI Collaborated Application Delivery
@@ -112,7 +112,7 @@ The KubeVela community incubated the Rollout project in the early days, similar
 
 3. **Good Compatibility:** No matter what workload the user uses for packaging (Helm or custom Operator), Rollout can work in bypass form after discovering the current underlying load resources.
 
-Reference: http://kubevela.net/docs/end-user/traits/rollout
+Reference: https://kubevela.net/docs/end-user/traits/rollout
 
 
 ### VelaUX Adds Multi-Environment Differentiated Visualized Configuration
@@ -131,7 +131,7 @@ In version 1.5, the following convenient features are added before and after dep
 
 - **Version Detail Query and Difference Comparison:** You can view the application configuration rendering results of each version on the Version Management page. You can also compare the version configuration with the current running configuration or the latest local configuration. It is convenient for users to track the configuration change process. 
 
-Reference: http://kubevela.net/docs/tutorials/multi-env
+Reference: https://kubevela.net/docs/tutorials/multi-env
 
 
 ## Improve Application Engine Capabilities