diff --git a/admin/kpanda/network/create-services.html b/admin/kpanda/network/create-services.html index 9af0f9362f..e433afca07 100644 --- a/admin/kpanda/network/create-services.html +++ b/admin/kpanda/network/create-services.html @@ -559,7 +559,7 @@
Helm
and Kubectl
, please make sure they are already installed.Helm
and Kubectl
, make sure they are already installed.Several components need to be installed:
@@ -504,7 +504,7 @@Access control pre-defines an administrator role for each sub-module, without user maintenance, you can directly authorize the predefined system roles of the platform to users to realize the modular management of the platform. For fine-grained permissions, refer to Permission Management.
Enterprise-grade access control
@@ -295,7 +295,7 @@LDAP
-LDAP refers to Lightweight Directory Access Protocol (Lightweight Directory Access Protocol), which is often used for single sign-on, that is, users can log in with one account password in multiple services. Global management supports LDAP for identity authentication, so the enterprise IdP that establishes identity authentication with AI platform through the LDAP protocol must support the LDAP protocol. For a detailed description of LDAP, please refer to: Welcome to LDAP.
+LDAP refers to Lightweight Directory Access Protocol (Lightweight Directory Access Protocol), which is often used for single sign-on, that is, users can log in with one account password in multiple services. Global management supports LDAP for identity authentication, so the enterprise IdP that establishes identity authentication with AI platform through the LDAP protocol must support the LDAP protocol. For a detailed description of LDAP, refer to: Welcome to LDAP.
OIDC
-OIDC, short for OpenID Connect, is an identity authentication standard protocol based on the OAuth 2.0 protocol. Global management supports the OIDC protocol for identity authentication, so the enterprise IdP that establishes identity authentication with AI platform through the OIDC protocol must support the OIDC protocol. For a detailed description of OIDC, please refer to: Welcome to OpenID Connect.
+OIDC, short for OpenID Connect, is an identity authentication standard protocol based on the OAuth 2.0 protocol. Global management supports the OIDC protocol for identity authentication, so the enterprise IdP that establishes identity authentication with AI platform through the OIDC protocol must support the OIDC protocol. For a detailed description of OIDC, refer to: Welcome to OpenID Connect.
OAuth 2.0
@@ -301,7 +301,7 @@If the user forgets the password when logging in, please refer to Reset Password.
+If the user forgets the password when logging in, refer to Reset Password.
Warning
@@ -405,7 +405,7 @@The audit logs related to Kubernetes in the auditing module are provided by the Insight module. To reduce the storage pressure of the audit logs, Global Management by default does not collect Kubernetes-related logs. -If you need to record them, please refer to Enabling K8s Audit Logs. +If you need to record them, refer to Enabling K8s Audit Logs. Once enabled, the cleanup function is consistent with the Global Management cleanup function, but they do not affect each other.
If they are not enabled, please refer to the documentation on enabling/disabling Kubernetes audit logs.
+If they are not enabled, refer to the documentation on enabling/disabling Kubernetes audit logs.
If they are not enabled, please refer to the documentation on enabling/disabling Kubernetes audit logs.
+If they are not enabled, refer to the documentation on enabling/disabling Kubernetes audit logs.
If they are not enabled, please refer to the documentation on enabling/disabling K8s audit logs.
+If they are not enabled, refer to the documentation on enabling/disabling K8s audit logs.
The collection of K8s audit logs is disabled by default. To enable it, follow these steps:
If there is a high customization requirement for the Ghippo login IdP, such as supporting WeCom, WeChat, or other social organization login requirements, -please refer to this document for implementation.
+refer to this document for implementation.Ghippo v0.15.0 and above.
Enable Isolation Mode between Folder/WS
-Please refer to Enable Isolation Mode between Folder/WS.
+Refer to Enable Isolation Mode between Folder/WS.
Plan Enterprise Architecture according to the Actual Situation
@@ -288,7 +288,7 @@The Guomi gateway used in this article supports SM2 and RSA TLS certificates. The advantage of dual certificates is that when the browser does not support SM2 TLS certificates, it automatically switches to RSA TLS certificates.
-For more detailed configurations, please refer to the Tongsuo official documentation.
+For more detailed configurations, refer to the Tongsuo official documentation.
We enter the Tengine container:
# Go to the nginx configuration file directory
cd /usr/local/nginx/conf
@@ -463,7 +463,7 @@ Verification
-November 6, 2024
+November 27, 2024
@@ -471,6 +471,9 @@ Verification
GitHub
-The user login screen is as shown in the figure below. For the specific login screen, please refer to the actual product.
+The user login screen is as shown in the figure below. For the specific login screen, refer to the actual product.
For the operation scope of the roles of Workspace Admin, Workspace Editor, and Workspace Viewer in each module, please refer to the permission description:
+For the operation scope of the roles of Workspace Admin, Workspace Editor, and Workspace Viewer in each module, refer to the permission description:
@@ -428,7 +428,7 @@In the left navigation bar, click Alert Center -> Notification Settings -> WeCom . Click Add Group Robot and add one or more group robots.
-For the URL of the WeCom group robot, please refer to the official document of WeCom: How to use group robots.
+For the URL of the WeCom group robot, refer to the official document of WeCom: How to use group robots.
After the configuration is complete, the notification list will automatically return. Click ┇ on the right side @@ -328,7 +328,7 @@
For the URL of the DingTalk group robot, refer to the official document of DingTalk: Custom Robot Access.
After the configuration is complete, the notification list will automatically return. Click ┇ on the right @@ -357,7 +357,7 @@
For the Webhook URL and more configuration methods, refer to the webhook document.
After the configuration is complete, the notification list will automatically return. Click ┇ on the right side @@ -389,7 +389,7 @@
To apply for Alibaba Cloud SMS service, refer to Alibaba Cloud SMS Service.
Field descriptions:
Refer to Alibaba Cloud Variable Specification.
Note
@@ -290,7 +290,7 @@To apply for Tencent Cloud SMS service, refer to Tencent Cloud SMS.
Field descriptions:
Please make sure that the Helm App Insight in your global management cluster is in Running state.
+Make sure that the Helm App Insight in your global management cluster is in Running state.
The specific operation steps are as follows:
timestamp:[2022-01-01 TO 2022-01-31]
.Clicking on the button next to a log will slide out a panel on the right side where you can view the @@ -326,7 +326,7 @@
To install insight-agent, please refer to: Installing insight-agent online or Offline upgrade of insight-agent.
+To install insight-agent, refer to: Installing insight-agent online or Offline upgrade of insight-agent.
Since the storage capacity of the metric storage component vmstorage in the global service cluster @@ -308,7 +308,7 @@
For more details, please refer to the Kubernetes official documentation.
+For more details, refer to the Kubernetes official documentation.
To meet different user needs for scheduling Insight components, Insight provides fine-grained labels for different components' scheduling policies. Below is a description of the labels and their associated components:
@@ -618,7 +618,7 @@Fill in the name, select the namespace and version, and fill in the addresses of logging, metric, audit, and trace reporting data in the yaml file. The system has filled in the address of the component for data reporting by default, please check it before clicking OK to install.
-If you need to modify the data reporting address, please refer to Get Data Reporting Address.
+If you need to modify the data reporting address, refer to Get Data Reporting Address.
Note
-For more configmaps, please refer to the bottom introduction or Prometheus official documentation.
+For more configmaps, refer to the bottom introduction or Prometheus official documentation.
Then prepare the jar package file, you can find the latest jar package download address on the Github page of jmx_exporter and refer to the following Dockerfile:
FROM openjdk:11.0.15-jre
@@ -383,7 +383,7 @@ Method 2: mount via init co
-November 6, 2024
+November 27, 2024
@@ -391,6 +391,9 @@ Method 2: mount via init co
GitHub
-November 15, 2024
+November 27, 2024
diff --git a/en/admin/insight/quickstart/otel/golang/golang.html b/en/admin/insight/quickstart/otel/golang/golang.html
index 4c0ea86d8d..567f09f718 100644
--- a/en/admin/insight/quickstart/otel/golang/golang.html
+++ b/en/admin/insight/quickstart/otel/golang/golang.html
@@ -410,7 +410,7 @@ Enhance Go applications with OTel
OpenTelemetry, also known simply as OTel, is an open-source observability framework that helps generate and collect telemetry data: traces, metrics, and logs in Go apps.
Enhance Go apps with the OpenTelemetry SDK¶
Install related dependencies¶
-Dependencies related to the OpenTelemetry exporter and SDK must be installed first. If you are using another request router, please refer to request routing.
+
Dependencies related to the OpenTelemetry exporter and SDK must be installed first. If you are using another request router, refer to request routing.
After switching/going into the application source folder run the following command:
go get go.opentelemetry.io/otel@v1.8.0 \
go.opentelemetry.io/otel/trace@v1.8.0 \
@@ -537,7 +537,7 @@ Run the applicationAchieving non-intrusive enhancement of applications through Operators to add annotations to deployment yaml:
+
Refer to the introduction of Only injecting environment variable annotations in Achieving non-intrusive enhancement of applications through Operators to add annotations to deployment yaml:
instrumentation.opentelemetry.io/inject-sdk: "insight-system/insight-opentelemetry-autoinstrumentation"
If you cannot use annotations, you can manually add the following environment variables to the deployment yaml:
@@ -679,7 +679,7 @@ Log errors and exceptionsspan.SetStatus(codes.Error, "internal error")
References¶
-For the Demo presentation, please refer to:
+For the Demo presentation, refer to:
- otel-grpc-examples
- opentelemetry-demo/productcatalogservice
@@ -690,7 +690,7 @@ References
-November 15, 2024
+November 27, 2024
diff --git a/en/admin/insight/quickstart/otel/golang/meter.html b/en/admin/insight/quickstart/otel/golang/meter.html
index c6d23beae3..498c88db4d 100644
--- a/en/admin/insight/quickstart/otel/golang/meter.html
+++ b/en/admin/insight/quickstart/otel/golang/meter.html
@@ -404,7 +404,7 @@ For Java ApplicationsOTEL_METRICS_EXPORTER=prometheus
You can then check your metrics at http://localhost:8888/metrics
.
Next, combine it with a Prometheus ServiceMonitor
to complete the metrics integration. If you want to expose custom metrics, please refer to opentelemetry-java-docs/prometheus.
Next, combine it with a Prometheus ServiceMonitor
to complete the metrics integration. If you want to expose custom metrics, refer to opentelemetry-java-docs/prometheus.
The process is mainly divided into two steps: