-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken links in the document files #2611
Conversation
Signed-off-by: vankichi <[email protected]>
WalkthroughWalkthroughThis pull request introduces several changes across multiple files, primarily focusing on enhancing the Kubernetes configuration for the Vald mirror gateway. Key updates include the addition of a new configuration option to enable the gateway mirror feature, updates to documentation hyperlinks for improved navigation, and the introduction of various Kubernetes resources such as ClusterRole, ClusterRoleBinding, ConfigMap, Deployment, HPA, PDB, PriorityClass, ServiceAccount, and Service. These changes collectively aim to improve the management and functionality of the Vald mirror gateway within a Kubernetes environment. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Kubernetes
participant ValdGateway
User->>Kubernetes: Deploy Vald Mirror Gateway
Kubernetes->>ValdGateway: Create ClusterRole
Kubernetes->>ValdGateway: Create ClusterRoleBinding
Kubernetes->>ValdGateway: Create ConfigMap
Kubernetes->>ValdGateway: Create Deployment
Kubernetes->>ValdGateway: Create HPA
Kubernetes->>ValdGateway: Create PodDisruptionBudget
Kubernetes->>ValdGateway: Create PriorityClass
Kubernetes->>ValdGateway: Create ServiceAccount
Kubernetes->>ValdGateway: Create Service
ValdGateway-->>User: Gateway is ready
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Deploying vald with Cloudflare Pages
|
[CHATOPS:HELP] ChatOps commands.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Outside diff range and nitpick comments (1)
docs/performance/continuous-benchmark.md (1)
64-65
: LanguageTool nitpicks (optional)LanguageTool highlighted two minor nitpicks:
- Line 64: Use "cannot" instead of "can not"
- Line 65: Use "cannot" instead of "can not"
Using "cannot" would be more grammatically correct in this context. However, these are very minor documentation nitpicks. Feel free to ignore them or incorporate them at your discretion.
If you'd like, I can submit a small PR to make these fixes. Let me know if that would be helpful!
Tools
LanguageTool
[style] ~64-~64: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...ig for running benchmark job
Tune if can not getting the expected performance with d...(CAN_NOT_PREMIUM)
[style] ~65-~65: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...config for benchmark job pod
Tune if can not getting the expected performance with d...(CAN_NOT_PREMIUM)
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (22)
- Makefile.d/k8s.mk (1 hunks)
- docs/api/insert.md (3 hunks)
- docs/api/object.md (3 hunks)
- docs/api/remove.md (4 hunks)
- docs/api/search.md (12 hunks)
- docs/api/update.md (3 hunks)
- docs/api/upsert.md (3 hunks)
- docs/contributing/coding-style.md (1 hunks)
- docs/performance/continuous-benchmark.md (1 hunks)
- docs/troubleshooting/client-side.md (1 hunks)
- docs/tutorial/get-started-with-faiss-agent.md (1 hunks)
- docs/tutorial/vald-multicluster-on-k8s.md (5 hunks)
- docs/user-guides/cluster-role-binding.md (1 hunks)
- k8s/gateway/gateway/mirror/clusterrole.yaml (1 hunks)
- k8s/gateway/gateway/mirror/clusterrolebinding.yaml (1 hunks)
- k8s/gateway/gateway/mirror/configmap.yaml (1 hunks)
- k8s/gateway/gateway/mirror/deployment.yaml (1 hunks)
- k8s/gateway/gateway/mirror/hpa.yaml (1 hunks)
- k8s/gateway/gateway/mirror/pdb.yaml (1 hunks)
- k8s/gateway/gateway/mirror/priorityclass.yaml (1 hunks)
- k8s/gateway/gateway/mirror/serviceaccount.yaml (1 hunks)
- k8s/gateway/gateway/mirror/svc.yaml (1 hunks)
Files skipped from review due to trivial changes (14)
- docs/api/insert.md
- docs/api/object.md
- docs/api/remove.md
- docs/api/search.md
- docs/api/update.md
- docs/api/upsert.md
- docs/contributing/coding-style.md
- docs/troubleshooting/client-side.md
- docs/tutorial/get-started-with-faiss-agent.md
- docs/tutorial/vald-multicluster-on-k8s.md
- docs/user-guides/cluster-role-binding.md
- k8s/gateway/gateway/mirror/clusterrolebinding.yaml
- k8s/gateway/gateway/mirror/priorityclass.yaml
- k8s/gateway/gateway/mirror/serviceaccount.yaml
Additional context used
LanguageTool
docs/performance/continuous-benchmark.md
[style] ~64-~64: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...ig for running benchmark job
Tune if can not getting the expected performance with d...(CAN_NOT_PREMIUM)
[style] ~65-~65: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...config for benchmark job pod
Tune if can not getting the expected performance with d...(CAN_NOT_PREMIUM)
Additional comments not posted (8)
k8s/gateway/gateway/mirror/pdb.yaml (1)
1-31
: LGTM!The
PodDisruptionBudget
resource for thevald-mirror-gateway
is well-defined:
- The file includes the standard Apache 2.0 license header.
- The Helm chart labels follow the recommended Kubernetes labels.
- The
maxUnavailable
is set to 50%, which allows some disruption but ensures that not all pods are unavailable at the same time.The code changes are approved.
k8s/gateway/gateway/mirror/hpa.yaml (1)
1-35
: LGTM!The
HorizontalPodAutoscaler
resource for thevald-mirror-gateway
is well-defined:
- The file includes the standard Apache 2.0 license header.
- The Helm chart labels follow the recommended Kubernetes labels.
- The
minReplicas
andmaxReplicas
are set to 3 and 9 respectively, which allows the deployment to scale based on CPU utilization.- The
targetCPUUtilizationPercentage
is set to 80%, which is a good default value.The code changes are approved.
k8s/gateway/gateway/mirror/svc.yaml (1)
1-45
: LGTM!The
Service
resource for thevald-mirror-gateway
is well-defined:
- The file includes the standard Apache 2.0 license header.
- The Helm chart labels follow the recommended Kubernetes labels.
- The exposed ports
grpc
,readiness
, andpprof
are well-defined and follow a consistent naming convention.- The
clusterIP
is set toNone
, making it a headless service, which is appropriate for a stateful application likevald-mirror-gateway
.The code changes are approved.
k8s/gateway/gateway/mirror/clusterrole.yaml (1)
1-55
: LGTM!The ClusterRole configuration looks good and follows best practices:
- The metadata labels are properly set, including the Helm chart version and component name.
- The rules grant the necessary permissions for the gateway-mirror component to manage
valdmirrortargets
resources.k8s/gateway/gateway/mirror/deployment.yaml (1)
1-184
: LGTM!The Deployment configuration looks good and follows best practices:
- The metadata labels are properly set, including the Helm chart version and component name.
- The spec defines a rolling update strategy with reasonable maxSurge and maxUnavailable values.
- The template spec includes proper security context settings, such as running as a non-root user and dropping all capabilities.
- Liveness, readiness, and startup probes are configured to ensure the health of the container.
- Resource limits and requests are set to ensure proper resource allocation.
- The container is configured to use a read-only root filesystem and runs with a non-root user for enhanced security.
- Environment variables are set to provide pod-specific information to the container.
- The container is configured to mount a config map volume for configuration.
k8s/gateway/gateway/mirror/configmap.yaml (1)
1-28
: LGTM!The ConfigMap configuration looks good and follows best practices:
- The metadata labels are properly set, including the Helm chart version and component name.
- The data section contains the configuration in a
config.yaml
key, which can be mounted as a file in the container.- The configuration includes various settings for the server, health check, metrics, observability, and gateway components.
Makefile.d/k8s.mk (1)
44-44
: LGTM, but verify thek8s/gateway/mirror
directory generation.The change looks good and enables the gateway mirror feature.
To ensure the mirror gateway is correctly deployed, please verify that:
- The
k8s/gateway/mirror
directory is generated by this Makefile target.- The directory contains the necessary Kubernetes resources (e.g., Deployment, Service) for the mirror gateway.
You can run the following commands to check:
docs/performance/continuous-benchmark.md (1)
48-65
: Formatting changes LGTM!The formatting updates to the properties table headers and content alignment enhance the readability without altering the underlying information.
Tools
LanguageTool
[style] ~64-~64: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...ig for running benchmark job
Tune if can not getting the expected performance with d...(CAN_NOT_PREMIUM)
[style] ~65-~65: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...config for benchmark job pod
Tune if can not getting the expected performance with d...(CAN_NOT_PREMIUM)
* 🐛 📝 Fix broken links in document files Signed-off-by: vankichi <[email protected]> * style: format code with Gofumpt and Prettier This commit fixes the style issues introduced in 07bb715 according to the output from Gofumpt and Prettier. Details: #2611 --------- Signed-off-by: vankichi <[email protected]> Co-authored-by: deepsource-autofix[bot] <62050782+deepsource-autofix[bot]@users.noreply.github.com>
* 🐛 📝 Fix broken links in document files * style: format code with Gofumpt and Prettier This commit fixes the style issues introduced in 07bb715 according to the output from Gofumpt and Prettier. Details: #2611 --------- Signed-off-by: vankichi <[email protected]> Co-authored-by: Kiichiro YUKAWA <[email protected]> Co-authored-by: deepsource-autofix[bot] <62050782+deepsource-autofix[bot]@users.noreply.github.com>
Description
I have fixed the broken links in the document files.
According to fixing, I realized
k8s/gateway/mirror
is missing even though their links are written in the document file.So, I have updated
Makefile.d/k8s.mk
to generatek8s/gateway/mirror
.Related Issue
Versions
Checklist
Special notes for your reviewer
Summary by CodeRabbit
New Features
vald-mirror-gateway
.vald-mirror-gateway
.Documentation
Style