[Catalog] Update Catalog items

Signed-off-by: l5io <[email protected]>
meshery · Jul 4, 2024 · 440a0b6 · 440a0b6
1 parent 36dea78
commit 440a0b6
Show file tree

Hide file tree

Showing 185 changed files with 2,426 additions and 182 deletions.
diff --git a/catalog/0194ff83-0a43-4b83-9c75-b8f0f32da6b7/artifacthub-pkg.yml b/catalog/0194ff83-0a43-4b83-9c75-b8f0f32da6b7/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: pod-readiness
 displayName: Pod Readiness
-createdAt: "2024-07-04T00:24:37Z"
+createdAt: "2024-07-04T10:04:47Z"
 description: Pod readiness in Kubernetes indicates when a Pod is prepared to handle requests and execute its intended tasks. It hinges on the successful initialization of its containers and the positive response from readiness probes, which verify the health and operational readiness of the Pod's components. This readiness status is crucial for ensuring that services can safely direct traffic to the Pod without encountering errors or delays caused by incomplete initialization or unavailability. Managing Pod readiness effectively enhances application reliability and performance by enabling Kubernetes to efficiently distribute Pods across nodes while ensuring they are capable of fulfilling their roles. Regular monitoring and adjustment of readiness probes and configurations are essential for maintaining optimal application responsiveness and resilience in dynamic Kubernetes environments.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/02413809-9fbf-4649-ae22-3d0947d264c6/artifacthub-pkg.yml b/catalog/02413809-9fbf-4649-ae22-3d0947d264c6/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: example-labels-and-annotations
 displayName: Example Labels and Annotations
-createdAt: "2024-07-04T00:24:34Z"
+createdAt: "2024-07-04T10:04:45Z"
 description: This design contains example of how label and annotation can be created and organised
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/05ff8dbb-2552-4a23-a6a8-318fe412bf30/artifacthub-pkg.yml b/catalog/05ff8dbb-2552-4a23-a6a8-318fe412bf30/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: pod-resource-request
 displayName: Pod Resource Request
-createdAt: "2024-07-04T00:24:38Z"
+createdAt: "2024-07-04T10:04:47Z"
 description: This design focuses on specifying the minimum CPU and memory requirements for Kubernetes Pods. By setting resource requests, this design ensures optimal resource allocation within Kubernetes clusters, thereby enhancing workload performance and maintaining stability across various applications and services. This feature is essential for fine-tuning resource utilization, preventing resource contention, and supporting efficient scaling and management of containerized workloads in cloud-native environments.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/06ef6097-8f21-4a76-b025-0c9271168814/artifacthub-pkg.yml b/catalog/06ef6097-8f21-4a76-b025-0c9271168814/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: istio-operator
 displayName: Istio Operator
-createdAt: "2024-07-04T00:24:52Z"
+createdAt: "2024-07-04T10:04:56Z"
 description: 'This YAML defines a Kubernetes Deployment for the Istio Operator within the istio-operator namespace. The deployment ensures a single replica of the Istio Operator pod is always running, which is managed by a service account named istio-operator. The deployment''s metadata includes the namespace and the deployment name. The pod selector matches pods with the label name: istio-operator, ensuring the correct pods are managed. The pod template specifies metadata and details for the containers, including the container name istio-operator and the image gcr.io/istio-testing/operator:1.5-dev, which runs the istio-operator command with the server argument.'
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/075ec9ba-6ad7-4421-a09c-3b8edd5fb4a6/artifacthub-pkg.yml b/catalog/075ec9ba-6ad7-4421-a09c-3b8edd5fb4a6/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: accelerated-mtls-handshake-for-envoy-data-planes
 displayName: Accelerated mTLS handshake for Envoy data planes
-createdAt: "2024-07-04T00:25:02Z"
+createdAt: "2024-07-04T10:05:02Z"
 description: Cryptographic operations are among the most compute-intensive and critical operations when it comes to secured connections. Istio uses Envoy as the “gateways/sidecar” to handle secure connections and intercept the traffic. Depending upon use cases, when an ingress gateway must handle a large number of incoming TLS and secured service-to-service connections through sidecar proxies, the load on Envoy increases. The potential performance depends on many factors, such as size of the cpuset on which Envoy is running, incoming traffic patterns, and key size. These factors can impact Envoy serving many new incoming TLS requests. To achieve performance improvements and accelerated handshakes, a new feature was introduced in Envoy 1.20 and Istio 1.14. It can be achieved with 3rd Gen Intel® Xeon® Scalable processors, the Intel® Integrated Performance Primitives (Intel® IPP) crypto library, CryptoMB Private Key Provider Method support in Envoy, and Private Key Provider configuration in Istio using ProxyConfig.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/081aa52c-7921-48dd-b81e-03f4ebfc70b5/artifacthub-pkg.yml b/catalog/081aa52c-7921-48dd-b81e-03f4ebfc70b5/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: minecraft-app
 displayName: Minecraft App
-createdAt: "2024-07-04T00:24:42Z"
+createdAt: "2024-07-04T10:04:49Z"
 description: Deploying minecraft application
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/08379ae3-cd9e-4b55-a190-91a47a1ff638/artifacthub-pkg.yml b/catalog/08379ae3-cd9e-4b55-a190-91a47a1ff638/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: fault-tolerant-batch-workloads-on-gke
 displayName: Fault-tolerant batch workloads on GKE
-createdAt: "2024-07-04T00:24:58Z"
+createdAt: "2024-07-04T10:04:59Z"
 description: |-
     A batch workload is a process typically designed to have a start and a completion point. You should consider batch workloads on GKE if your architecture involves ingesting, processing, and outputting data instead of using raw data. Areas like machine learning, artificial intelligence, and high performance computing (HPC) feature different kinds of batch workloads, such as offline model training, batched prediction, data analytics, simulation of physical systems, and video processing.
 

diff --git a/catalog/0a2d8c39-df40-490b-94b7-75d0fb7fc207/artifacthub-pkg.yml b/catalog/0a2d8c39-df40-490b-94b7-75d0fb7fc207/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: default-ns
 displayName: default-ns
-createdAt: "2024-07-04T00:24:45Z"
+createdAt: "2024-07-04T10:04:51Z"
 description: This is a sample default namespace that can be used for testing.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/0aa86dd0-415c-4bf8-ae76-832560470b74/artifacthub-pkg.yml b/catalog/0aa86dd0-415c-4bf8-ae76-832560470b74/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: run-daemonset-on-gke-autopilot
 displayName: Run DaemonSet on GKE Autopilot
-createdAt: "2024-07-04T00:24:58Z"
+createdAt: "2024-07-04T10:04:59Z"
 description: |-
     GKE uses the total size of your deployed workloads to determine the size of the nodes that Autopilot provisions for the cluster. If you add or resize a DaemonSet after Autopilot provisions a node, GKE won't resize existing nodes to accommodate the new total workload size. DaemonSets with resource requests larger than the allocatable capacity of existing nodes, after accounting for system pods, also won't get scheduled on those nodes.
 

diff --git a/catalog/0b6b1ff8-cb2e-41d4-baff-e0a053f7e4d9/artifacthub-pkg.yml b/catalog/0b6b1ff8-cb2e-41d4-baff-e0a053f7e4d9/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: apache-airflow
 displayName: Apache Airflow
-createdAt: "2024-07-04T00:24:43Z"
+createdAt: "2024-07-04T10:04:50Z"
 description: |-
     Apache Airflow (or simply Airflow) is a platform to programmatically author, schedule, and monitor workflows.
 

diff --git a/catalog/0d8d6d6d-362f-49e3-9a88-2d7e6aa20542/artifacthub-pkg.yml b/catalog/0d8d6d6d-362f-49e3-9a88-2d7e6aa20542/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: design-with-validation-errors
 displayName: Design With Validation Errors
-createdAt: "2024-07-04T00:24:31Z"
+createdAt: "2024-07-04T10:04:43Z"
 description: Design with proper validation
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/0e426f91-14df-4f70-b6cc-ed3624d53ccd/artifacthub-pkg.yml b/catalog/0e426f91-14df-4f70-b6cc-ed3624d53ccd/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: key-cloak-operator
 displayName: Key cloak operator
-createdAt: "2024-07-04T00:24:47Z"
+createdAt: "2024-07-04T10:04:52Z"
 description: This YAML snippet describes a Kubernetes Deployment for a Keycloak operator, ensuring a single replica. It specifies labels and annotations for metadata, including a service account. The pod template defines a container running the Keycloak operator image, with environment variables set for namespace and pod name retrieval. Security context settings prevent privilege escalation. Probes are configured for liveness and readiness checks on port 8081, with resource requests and limits ensuring proper resource allocation for the container.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/104be089-dae0-4d09-be70-c1d121673119/artifacthub-pkg.yml b/catalog/104be089-dae0-4d09-be70-c1d121673119/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: mtls-handshake-acceleration-for-istio
 displayName: mTLS-handshake-acceleration-for-Istio
-createdAt: "2024-07-04T00:25:05Z"
+createdAt: "2024-07-04T10:05:03Z"
 description: Cryptographic operations are among the most compute-intensive and critical operations when it comes to secured connections. Istio uses Envoy as the “gateways/sidecar” to handle secure connections and intercept the traffic. Depending upon use cases, when an ingress gateway must handle a large number of incoming TLS and secured service-to-service connections through sidecar proxies, the load on Envoy increases. The potential performance depends on many factors, such as size of the cpuset on which Envoy is running, incoming traffic patterns, and key size. These factors can impact Envoy serving many new incoming TLS requests. To achieve performance improvements and accelerated handshakes, a new feature was introduced in Envoy 1.20 and Istio 1.14. It can be achieved with 3rd Gen Intel® Xeon® Scalable processors, the Intel® Integrated Performance Primitives (Intel® IPP) crypto library, CryptoMB Private Key Provider Method support in Envoy, and Private Key Provider configuration in Istio using ProxyConfig.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/107f4fc2-0655-4d00-be3d-164947159647/artifacthub-pkg.yml b/catalog/107f4fc2-0655-4d00-be3d-164947159647/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: hello-kubernetes-tutorial
 displayName: Hello Kubernetes Tutorial
-createdAt: "2024-07-04T00:24:32Z"
+createdAt: "2024-07-04T10:04:44Z"
 description: This tutorial will get you up and running with Dapr in a Kubernetes cluster. You will be deploying the same applications from Hello World. To recap, the Python App generates messages and the Node app consumes and persists them.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/114c94c9-052b-46a2-86fe-4cdd2e88c746/artifacthub-pkg.yml b/catalog/114c94c9-052b-46a2-86fe-4cdd2e88c746/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: my-first-app-design
 displayName: my first app design
-createdAt: "2024-07-04T00:24:46Z"
+createdAt: "2024-07-04T10:04:52Z"
 description: 'This infrastructure design defines two services within a system: 1. **Customer Service**:   - Type: Customer   - Version: 0.0.50   - Model: Jira Service Desk Operator   - Attributes: This service is configured with specific settings, including an email address, legacy customer mode, and a name. It is categorized as a tool within the system.2. **Notebook Service**:   - Type: Notebook   - Version: 1.6.1   - Model: Kubeflow   - Attributes: This service is categorized as a machine learning tool. It has metadata related to its source URI and appearance. These services are components within a larger system or design, each serving a distinct purpose. The Customer Service is associated with customer-related operations, while the Notebook Service is related to machine learning tasks.'
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/129c524b-ead9-4170-b236-a1c9dd274ece/artifacthub-pkg.yml b/catalog/129c524b-ead9-4170-b236-a1c9dd274ece/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: gitlab-runner-deployment
 displayName: gitlab runner deployment
-createdAt: "2024-07-04T00:24:44Z"
+createdAt: "2024-07-04T10:04:51Z"
 description: |
     This configuration ensures that a single instance of the GitLab Runner is deployed within the gitlab-runner namespace. The GitLab Runner is configured with a specific ServiceAccount, CPU resource requests and limits, and is provided with a ConfigMap containing the configuration file config.toml. The deployment is designed to continuously restart the pod (restartPolicy: Always) to ensure the GitLab Runner remains available for executing jobs.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg

diff --git a/catalog/17c46515-50ef-436c-9383-451e13348ddd/artifacthub-pkg.yml b/catalog/17c46515-50ef-436c-9383-451e13348ddd/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: pod-multi-containers
 displayName: Pod Multi Containers
-createdAt: "2024-07-04T00:24:38Z"
+createdAt: "2024-07-04T10:04:47Z"
 description: '"Pod Multi Containers" design facilitates the deployment of Kubernetes Pods that consist of multiple containers, each serving a distinct role within a single cohesive unit.'
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/189a3e71-8be9-4e64-9fed-150a9b1060de/artifacthub-pkg.yml b/catalog/189a3e71-8be9-4e64-9fed-150a9b1060de/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: resilient-web-app
 displayName: Resilient Web App
-createdAt: "2024-07-04T00:25:04Z"
+createdAt: "2024-07-04T10:05:03Z"
 description: This is a simple app that uses nginx as a web proxy for improving the resiliency of web app
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/19b4edf1-a88c-4255-9544-ea7268c9b466/artifacthub-pkg.yml b/catalog/19b4edf1-a88c-4255-9544-ea7268c9b466/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: hello-wasm
 displayName: Hello WASM
-createdAt: "2024-07-04T00:24:35Z"
+createdAt: "2024-07-04T10:04:46Z"
 description: Sample WASM implementation with service mesh
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/1abccf09-dcb8-46e4-8cac-f9e33c27516d/artifacthub-pkg.yml b/catalog/1abccf09-dcb8-46e4-8cac-f9e33c27516d/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: aws-rds-controller
 displayName: AWS rds controller
-createdAt: "2024-07-04T00:24:55Z"
+createdAt: "2024-07-04T10:04:57Z"
 description: This YAML manifest defines a Kubernetes Deployment for the ACK RDS Controller application. It orchestrates the deployment of the application within a Kubernetes cluster, ensuring its availability and scalability. The manifest specifies various parameters such as the number of replicas, pod template configurations including container settings, environment variables, resource limits, and security context. Additionally, it includes probes for health checks, node selection preferences, tolerations, and affinity rules for optimal scheduling. The manifest encapsulates the deployment requirements necessary for the ACK RDS Controller application to run effectively in a Kubernetes environment.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/1d2ca262-3d69-4bfd-86ff-61b3c9162881/artifacthub-pkg.yml b/catalog/1d2ca262-3d69-4bfd-86ff-61b3c9162881/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: istio-http-header-filter-(clone)
 displayName: Istio HTTP Header Filter (Clone)
-createdAt: "2024-07-04T00:25:05Z"
+createdAt: "2024-07-04T10:05:04Z"
 description: This is a test design
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/1d3b05ee-7c11-4c01-be93-81c3bb1b6524/artifacthub-pkg.yml b/catalog/1d3b05ee-7c11-4c01-be93-81c3bb1b6524/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: emojivoto-application
 displayName: Emojivoto Application
-createdAt: "2024-07-04T00:24:39Z"
+createdAt: "2024-07-04T10:04:48Z"
 description: This design deploys Linkerd sample emojivoto application.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/1e2478e0-7611-4d4f-a44f-ea02cebf7b91/artifacthub-pkg.yml b/catalog/1e2478e0-7611-4d4f-a44f-ea02cebf7b91/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: postgresql-cluster
 displayName: postgreSQL cluster
-createdAt: "2024-07-04T00:24:46Z"
+createdAt: "2024-07-04T10:04:52Z"
 description: This YAML configuration defines a PostgreSQL cluster deployment tailored for Google Kubernetes Engine (GKE) utilizing the Cloud Native PostgreSQL (CNPG) operator. The cluster, named "gke-pg-cluster," is designed to offer a standard PostgreSQL environment, featuring three instances for redundancy and high availability. Each instance is provisioned with 2Gi of premium storage, ensuring robust data persistence. Resource allocations are specified, with each instance requesting 1Gi of memory and 1000m (milliCPU) of CPU, and limits set to the same values. Additionally, the cluster is configured with pod anti-affinity, promoting distribution across nodes for fault tolerance. Host-based authentication is enabled for security, permitting access from IP range 10.48.0.0/20 using the "md5" method. Monitoring capabilities are integrated, facilitated by enabling pod monitoring. The configuration also includes tolerations and additional pod affinity rules, enhancing scheduling flexibility and optimizing resource utilization within the Kubernetes environment. This deployment exemplifies a robust and scalable PostgreSQL infrastructure optimized for cloud-native environments, aligning with best practices for reliability, performance, and security.
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/1f3c7dcd-e49a-4bf7-985a-661d6c64d8d7/artifacthub-pkg.yml b/catalog/1f3c7dcd-e49a-4bf7-985a-661d6c64d8d7/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: doks-nginx-deployment
 displayName: doks-nginx-deployment
-createdAt: "2024-07-04T00:25:01Z"
+createdAt: "2024-07-04T10:05:01Z"
 description: This is a sample design used for exploring kubernetes deployment and service
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/1f79b0c6-2efe-4ee9-b08c-e1bd07a3926b/artifacthub-pkg.yml b/catalog/1f79b0c6-2efe-4ee9-b08c-e1bd07a3926b/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: example-edge-network-relationship-
 displayName: 'Example Edge-Network Relationship '
-createdAt: "2024-07-04T00:24:31Z"
+createdAt: "2024-07-04T10:04:43Z"
 description: "The design showcases the operational dynamics of the Edge-Network Relationship. There are two ways you can use this design in your architecture design.\n1. Cloning this design by clicking the clone button.\n2. Start from scratch by creating an edge-network relationship on your own.\n\n<strong>How to create an Edge-Network relationship on your own?</strong>\n\n1. Navigate to MeshMap.\n2. Click on the Kubernetes icon inside the dock it will open a Kubernetes drawer from where you can select any component that Kubernetes supports.\n3. Search for the Ingress and Service component from the search bar provided in the drawer.\n4. Drag-n-drop both the components on the canvas.\n5. Hover over the Ingress component, Some handlebars will show up on four sides of the component. \n6. Move the cursor close to either of the handlebars, an arrow will show up, click on that arrow. This will open up two options:\n    1. <strong> Question mark: </strong>  Opens the Help Center\n    2. <strong>Arrow (Edge handle): </strong> This edge handle is used for creating the edge relationship\n7. Click on the Edge handle and move your cursor close to the Service component. An edge will appear going from the Ingress to Service component which represents the edge relationship between the two components.\n8. Congratulations! You just created a relationship between Ingress and Service."
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 license: Apache-2.0

diff --git a/catalog/1fa80124-d38d-41d1-a768-0fcb7cdae31e/artifacthub-pkg.yml b/catalog/1fa80124-d38d-41d1-a768-0fcb7cdae31e/artifacthub-pkg.yml
@@ -1,7 +1,7 @@
 version: 0.0.1
 name: horizontalpodautoscaler
 displayName: HorizontalPodAutoscaler
-createdAt: "2024-07-04T00:24:49Z"
+createdAt: "2024-07-04T10:04:54Z"
 description: |-
     A HorizontalPodAutoscaler (HPA for short) automatically updates a workload resource (such as a Deployment or StatefulSet), with the aim of automatically scaling the workload to match demand
     Horizontal scaling means that the response to increased load is to deploy more Pods. This is different from vertical scaling, which for Kubernetes would mean assigning more resources (for example: memory or CPU) to the Pods that are already running for the workload.