polaris VS gatekeeper

We are delighted to announce that the interface of Ryviu account has been updated according to Shopify Polaris. Aligned with Shopify's top-tier standards for safety, performance, and functionality, these changes aim to simplify the process of importing and managing product reviews for your store.

Shopify Polaris: Shopify's Polaris Design System features a color module with primary, secondary, and functional colors, plus an extended palette for shades and tints. Similar to others, it underscores the role of color in conveying meaning, maintaining visual hierarchy, and ensuring accessibility.

shopify design system: https://polaris.shopify.com/

I love the idea because community contributions in OS projects are always super focused on the code aspect while the design work is performed by the core team. Sometimes the results are shared publicly (Cals Design System or Shopify's Polaris)

Currently Im using templates, so my options are kind of limited by that. I cannot do fancy React or Vue apps (would love to tho). My main point of reference is the Polaris design system by Shopify (https://polaris.shopify.com). Simple but efficient.

Learn UX. There are a couple of publicly available design systems out there that give some guidelines about UX: Material Design, Polaris, Human Interface Guidelines.

https://polaris.shopify.com/ - Shopify

When the Gatekeeper validatingwebhook came up, I was really worried that'd be the issue! Regardless I'd recommend anyone who cares about their cluster not collapsing to change the gatekeeper webhook to only intercept resources you care about: https://github.com/open-policy-agent/gatekeeper/pull/1806

Kyverno adds an extra layer of security where only the allowed type of manifest is deployed onto kubernetes, otherwise, it will reject or we can set validationFailureAction to audit which only logs the policy violation message for reporting. Kubewarden and Gatekeeper are alternative tools available to enforce policies on Kubernetes CRD.

Now, we have the hardest part resolved and let's turn our attention to the OPA Gatekeeper. Gatekeeper uses the OPA Constraint Framework to describe and enforce policy. Right now there are mainly 3 parts we should pay attention:

They enable you to establish the policies and regulations that govern cluster deployments and applications. Using predefined policies, policy engines can dynamically modify or create configurations. Policy engines such as Gatekeeper and Kyverno can be leveraged to meet legal and compliance requirements while maintaining operational flexibility and development speed.

Setup policy around what resource requirements can be requested by an app per environment. OPA and gatekeeper or kyverno can help. Setup access control for who can create or modify apps.

OPA Gatekeeper is an open source, general purpose policy engine. OPA decouples policy decisions from other responsibilities of an application, like those commonly referred to as business logic. OPA works equally well making decisions for Kubernetes, Microservices, functional application authorization and more, thanks to its single unified policy language.