Skip to content

Commit

Permalink
Merge branch 'master' into master
Browse files Browse the repository at this point in the history
  • Loading branch information
kanishk6103 authored Jul 6, 2024
2 parents 4b149f5 + 459af4b commit 94433b2
Show file tree
Hide file tree
Showing 188 changed files with 282 additions and 184 deletions.
2 changes: 1 addition & 1 deletion _data/discuss/meshery.json

Large diffs are not rendered by default.

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: pod-readiness
displayName: Pod Readiness
createdAt: "2024-07-05T16:49:44Z"
createdAt: "2024-07-06T00:23:53Z"
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
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: example-labels-and-annotations
displayName: Example Labels and Annotations
createdAt: "2024-07-05T16:49:41Z"
createdAt: "2024-07-06T00:23:49Z"
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
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: pod-resource-request
displayName: Pod Resource Request
createdAt: "2024-07-05T16:49:45Z"
createdAt: "2024-07-06T00:23:54Z"
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
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: istio-operator
displayName: Istio Operator
createdAt: "2024-07-05T16:49:58Z"
createdAt: "2024-07-06T00:24:10Z"
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
Expand Down
Original file line number Diff line number Diff line change
@@ -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-05T16:50:08Z"
createdAt: "2024-07-06T00:24:21Z"
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
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: minecraft-app
displayName: Minecraft App
createdAt: "2024-07-05T16:49:48Z"
createdAt: "2024-07-06T00:23:58Z"
description: Deploying minecraft application
logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
license: Apache-2.0
Expand Down
Original file line number Diff line number Diff line change
@@ -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-05T16:50:03Z"
createdAt: "2024-07-06T00:24:16Z"
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.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: default-ns
displayName: default-ns
createdAt: "2024-07-05T16:49:51Z"
createdAt: "2024-07-06T00:24:02Z"
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
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: run-daemonset-on-gke-autopilot
displayName: Run DaemonSet on GKE Autopilot
createdAt: "2024-07-05T16:50:04Z"
createdAt: "2024-07-06T00:24:17Z"
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.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: apache-airflow
displayName: Apache Airflow
createdAt: "2024-07-05T16:49:50Z"
createdAt: "2024-07-06T00:24:00Z"
description: |-
Apache Airflow (or simply Airflow) is a platform to programmatically author, schedule, and monitor workflows.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: design-with-validation-errors
displayName: Design With Validation Errors
createdAt: "2024-07-05T16:49:38Z"
createdAt: "2024-07-06T00:23:46Z"
description: Design with proper validation
logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
license: Apache-2.0
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
version: 0.0.1
name: key-cloak-operator
displayName: Key cloak operator
createdAt: "2024-07-05T16:49:53Z"
createdAt: "2024-07-06T00:24:04Z"
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
Expand Down
Loading

0 comments on commit 94433b2

Please sign in to comment.