Cloud Native Catalog

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

This is a sample default namespace that can be used for testing.

Caveats and Considerations

No caveats. Feel free to reuse.

Technologies

What this pattern does

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.

Caveats and Considerations

Ensure networking is setup properly and correct annotation are applied to each resource for custom Intel configuration

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

This is a test design

Caveats and Considerations

NA

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

Cinder is a Block Storage service for OpenStack. This example shows how it can be used as an attachment mounted to a pod in Kubernetes. Start kubelet with cloud provider as openstack with a valid cloud config Sample cloud_config [Global] auth-url=https://os-identity.vip.foo.bar.com:5443/v2.0 username=user password=pass region=region1 tenant-id=0c331a1df18571594d49fe68asa4e Create a cinder volume Ex cinder create --display-name=test-repo 2Use the id of the cinder volume created to create a pod definition Create a new pod with the definition cluster/kubectl.sh create -f examples/mysql-cinder-pd/mysql.yaml This should now 1. Attach the specified volume to the kubelet's host machine\\
2. Format the volume if required (only if the volume specified is not already formatted to the fstype specified) 3. Mount it on the kubelet's host machine 4. Spin up a container with this volume mounted to the path specified in the pod definition

Caveats and Considerations

Currently the cinder volume plugin is designed to work only on linux hosts and offers ext4 and ext3 as supported fs types Make sure that kubelet host machine has the following executables.\\
Ensure cinder is installed and configured properly in the region in which kubelet is spun up

Technologies

What this pattern does

Defines a Kubernetes PersistentVolumeClaim (PVC) requesting 10Gi storage with 'manual' storage class. Supports both ReadWriteMany and ReadWriteOnce access modes, with optional label-based PV selection. Carefully adjust storage size for specific storage solutions, and consider annotations, security, monitoring, and scalability needs.

Caveats and Considerations

Ensure that the chosen storageClassName is properly configured and available in your cluster. Be cautious about the ReadWriteMany and ReadWriteOnce access modes, as they impact compatibility with PersistentVolumes (PVs). The selector should match existing PVs in your cluster if used. Adjust the storage size to align with your storage solution, keeping in mind the AWS EFS special case. Review the need for annotations, confirm the namespace, and implement security measures. Monitor and set up alerts for your PVC, and plan for backup and disaster recovery. Lastly, ensure scalability to meet your application's storage requirements.

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

This is sample app for testing k8s deployment and cilium

Caveats and Considerations

Ensure networking is setup properly and correct annotation are applied to each resource for custom Intel configuration

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

This design is for learning purposes and may be freely copied and distributed.

Caveats and Considerations

This design contains nginx deployment

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

prometheus

Caveats and Considerations

prometheus

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

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.

Caveats and Considerations

Ensure networking is setup properly and correct annotation are applied to each resource for custom Intel configuration

Technologies

What this pattern does

This designs runs a simple python webserver at port 8000. It also containers k8s service which connects to the deployment

Caveats and Considerations

Ensure port are not pre-occupied.

Technologies

What this pattern does

The New Stack (TNS) is a simple three-tier demo application, fully instrumented with the 3 pillars of observability: metrics, logs, and traces. It offers an insight on what a modern observability stack looks like and experience what it's like to pivot among different types of observability data. The TNS app is an example three-tier web app built by Weaveworks. It consists of a data layer, application logic layer, and load-balancing layer. To learn more about it, see How To Detect, Map and Monitor Docker Containers with Weave Scope from Weaveworks. The instrumentation for the TNS app is as follows: Metrics: Each tier of the TNS app exposes metrics on /metrics endpoints, which are scraped by the Grafana Agent. Additionally, these metrics are tagged with exemplar information. The Grafana Agent then writes these metrics to Mimir for storage.Logs: Each tier of the TNS app writes logs to standard output or standard error. It is captured by Kubernetes, which are then collected by the Grafana Agent. Finally, the Agent forwards them to Loki for storage. Traces: Each tier of the TNS app sends traces in Jaeger format to the Grafana Agent, which then converts them to OTel format and forwards them to Tempo for storage. Visualization: A Grafana instance configured to talk to the Mimir, Loki, and Tempo instances makes it possible to query and visualize the metrics, logs, and traces data.

Caveats and Considerations

Ensure enough resources are available on the k8s cluster

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

This is a sample WordPress deployment.

Caveats and Considerations

No caveats. Feel free to reuse or distrubute.

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

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.

Caveats and Considerations

Ensure networking is setup properly and correct annotation are applied to each resource for custom Intel configuration

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

Bank of Anthos is a sample HTTP-based web app that simulates a bank's payment processing network, allowing users to create artificial bank accounts and complete transactions.

Caveats and Considerations

Ensure enough resources are available on the cluster.

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

This is a sample guestbook app to demonstrate distributed systems

Caveats and Considerations

1. Ensure networking is setup properly. 2. Ensure enough disk space is available

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

Google's Microservices sample app is named Online Boutique. Docs - https://docs.meshery.io/guides/sample-apps#online-boutique Source - https://github.com/GoogleCloudPlatform/microservices-demo

Caveats and Considerations

N/A

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies

What this pattern does

This design sets up a Kubernetes Deployment deploying two NGINX containers. Each container utilizes an Azure File storage volume for shared data. The NGINX instances serve web content while accessing an Azure File share, enabling scalable and shared storage for the web servers.

Caveats and Considerations

1. Azure Configuration: Ensure that your Azure configuration, including secrets, is correctly set up to access the Azure File share.

2. Data Sharing: Multiple NGINX containers share the same storage. Be cautious when handling write operations to avoid conflicts or data corruption.

3. Scalability: Consider the scalability of both NGINX and Azure File storage to meet your application's demands.

4. Security: Safeguard the secrets used to access Azure resources and limit access to only authorized entities.

5. Pod Recovery: Ensure that the pod recovery strategy is well-defined to handle disruptions or node failures.

6. Azure Costs: Monitor and manage costs associated with Azure File storage, as it may incur charges based on usage.

7. Maintenance: Plan for regular maintenance and updates of both NGINX and Azure configurations to address security and performance improvements.

8. Monitoring: Implement monitoring and alerts for both the NGINX containers and Azure File storage to proactively detect and address issues.

9. Backup and Disaster Recovery: Establish a backup and disaster recovery plan to safeguard data stored in Azure File storage.

Technologies

What this pattern does

""

Caveats and Considerations

""

Technologies