# Meshery v1.0.50

2026-06-29 · [Original release notes](https://github.com/meshery/meshery/releases/tag/v1.0.50) · [Full summary](https://ratatosk.io/en/releases/meshery/v1.0.50)

Security 1 · Breaking changes 1 · Important fixes 5 · Enhancements 77 · Dependency updates 3 · Other changes 32

## Security (1)

### `ws` remote memory-exhaustion crash fixed

- Affects: Meshery Docker extension UI dependencies in `/install/docker-extension/ui`

A peer could send many tiny fragments and data chunks with modest network traffic, causing a `ws` server or client to crash from OOM. The UI lockfile now uses `ws` 8.21.0 and 7.5.11; the 8.21.0 fix prevents this described crash.

> - Bump ws in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#20110)

## Breaking changes (1)

### AWS API Gateway v2 hierarchical relationships refactored

- Affects: AWS API Gateway v2 `Route`/`API` and `Stage`/`API` hierarchical relationships (Inferred)

The relationships used the prior schema and had `mutatorRef` logic that needed correction; the route relationship targeted the AWS logical name instead of the Kubernetes object name. They now use the `v1alpha3` schema with corrected `mutatorRef` logic, and the route relationship targets the Kubernetes object name.

Evidence: “- Updated `hierarchical-inventory-route-api` to use `v1alpha3` schema and correct `mutatorRef` logic (targeting K8s object name instead of AWS logical name).” https://github.com/meshery/meshery/pull/17631

> - [Models] Implemented AWS APIGatewayV2 Bindings & Refactored Hierarchical Relationships to v1alpha3 schema @AhmedAzzam-Web (#17631)

## Important fixes (5)

### Azure Container Service relationship model names corrected

- Affects: setups using the `azure-container-service` model and its existing relationships

Selectors in eight existing relationship files used the misspelled `azure-conatiner-service` model name, leaving incorrect model-name references. The files now refer to `azure-container-service`.

> - feat(meshmodel): fix typo and add ManagedClustersAgentPool relationship for azure-container-service @adityaupasani2 (#17760)

### AWS networking relationships added to `aws-ec2-controller/v1.9.2`

- Affects: AWS models using `aws-ec2-controller/v1.9.2`

When modeling AWS routing and egress, `RouteTable → Subnet` existed, but route targets and the listed NAT Gateway, instance, and VPC endpoint relationships were missing. The model now includes ten relationships: `RouteTable` to `InternetGateway`, `NATGateway`, `VPCPeeringConnection`, `TransitGateway`, and `VPCEndpoint`; `NATGateway` to `Subnet` and `ElasticIPAddress`; `Instance` to `Subnet`; and `VPCEndpoint` to `Subnet` and `SecurityGroup`.

> - [Models] Add AWS routing and NAT Gateway relationships for aws-ec2-controller @akshayghalme (#19087)

### Exoscale icons now include their brand background

- Affects: Kanvas/shapes using `crossplane-provider-exoscale` model versions `v1.0.0` and `v1.0.1`

When `svgComplete` was empty in meshmodel metadata, Kanvas/shapes showed only a white glyph without the Exoscale brand background. The metadata now provides the full red-circle-and-white-logo icon.

> - fix(meshmodel): populate svgComplete for Exoscale icons @ShubhamSoni09 (#19939)

### `mesheryctl` `minimum()` tie handling fixed

- Affects: `mesheryctl` code paths that use `minimum()` and encounter tied minimum arguments (Inferred)

When two arguments tied for the minimum, such as `a == b < c`, `minimum()` returned the largest argument instead.

> - [mesheryctl] Fix minimum() returning max on argument ties @Priyanshu6968 (#20285)

### Add Cluster upload handling for errored contexts fixed

- Affects: kubeconfig uploads through Add Cluster

When an uploaded kubeconfig contained an unreachable or unsavable context, the UI read the wrong response buckets and tried to access a missing `error` field, then displayed a post-upload crash as an upload failure even though the upload succeeded. It now handles those contexts and builds notifications from the context name and server.

> - [UI] Fix Add Cluster crash on kubeconfig upload with errored contexts @marblom007 (#20317)

## Enhancements (77)

- AWS EC2/VPC resource relationships added
- Five `aws-mq-controller` relationships added (To use: `aws-mq-controller` model version `v1.2.1`)
- Four relationships added to `Terminator` in `aws-node-termination-handler-2`
- `aws-ecr-controller` ECR topology relationships added
- 14 non-binding relationships for `aws-route53-controller`
- CloudFront-to-Kubernetes visual reference relationships (To use: `aws-cloudfront-controller` version `v1.3.1`)
- AWS Glue model added to Meshery's meshmodel registry
- Ten non-binding reference relationships for `aws-applicationautoscaling-controller` (To use: `aws-applicationautoscaling-controller` model version `v1.2.1`)
- AWS Lambda-to-SQS relationship definition added
- AWS Elasticsearch-to-CloudWatch log publishing relationship added
- NVIDIA GPU Operator and node-feature-discovery model definitions added
- Azure `BatchAccount` relationships added
- IAM Role binding relationships added for EKS resources
- Five hierarchical API Gateway inventory relationships added to Kanvas
- Four edge relationships added to the `aws-apigatewayv2-controller/v1.2.1` model
- CloudWatch `LogGroup` reference for ECS `TaskDefinition` log routing (To use: Use as a manual edge; it does not populate automatically.)
- Flux v1.8.0 hierarchical resource relationships in Kanvas
- Kanvas adds `TaskDefinition` nesting within `Cluster`
- AWS DynamoDB references from Deployments and Pods
- Non-binding SQS Queue references to Kubernetes workloads
- Non-binding Azure Service Bus `NamespacesQueue` references for Kubernetes `Deployment` and `Pod` workloads
- Non-binding Azure Event Hub references for Kubernetes workloads (To use: Azure Event Hub model version `v2.14.0`)
- AWS RDS references to Kubernetes workloads (To use: model version `aws-rds-controller v1.7.12`)
- Non-binding AWS Lambda references to Kubernetes Deployments and Pods (To use: `aws-lambda-controller v1.12.2` model version)
- Karpenter resource hierarchy in Kanvas (To use: Karpenter model v1.0.0)
- MetalLB resource hierarchy in Kanvas
- Azure Database for PostgreSQL and MySQL FlexibleServer subnet relationships added (To use: Azure Service Operator model versions v2.13.0 and v2.14.0)
- ECS Service-to-TargetGroupBinding ARN binding
- Non-binding ECS Service–EC2 SecurityGroup firewall relationship added
- EC2 Subnet-to-ECS Service network mapping added
- Non-binding ECS Cluster-to-EC2 Instance relationship
- StackGres parent-inventory relationships added
- Azure security rules linked to parent Network Security Groups
- Eight AWS API Gateway v2 relationships added (To use: the `aws-apigatewayv2-controller/v1.2.1` model)
- 12 cross-service relationships added to the `aws-s3-controller` model
- AWS API Gateway v2 bindings and permission relationship added
- Parent-inventory relationship added for `ManagedClustersAgentPool`
- 19 relationships added for `aws-elasticache-controller` v1.3.3
- KEDA authentication dependency relationships added (To use: KEDA v2.19.0 model components)
- Six cert-manager relationship definitions added
- KEDA v2.19.0 adds hierarchical relationships for scaled workloads
- Non-binding AWS Lambda-to-Kubernetes reference relationships added (To use: the `aws-lambda-controller/v1.10.1` model files)
- AWS KMS Key relationships for Kubernetes Pods and Deployments
- Visual-only, non-binding AWS SNS topic references to Kubernetes Deployments and Pods
- AWS cross-service relationships added to Meshery models
- ECS `TargetGroup` component and Service relationship added (To use: `aws-ecs-controller` model version v1.2.1)
- EventBridge Rule destination relationships added
- GitHub connection definition added to `meshery-core` (To use: `meshery-core` model version `0.7.2`)
- Non-binding ECR Repository reference added for ECS TaskDefinitions
- Non-binding API Gateway V2 Integration-to-Lambda relationship added
- Visual SQS-to-Lambda event source mapping relationship added (To use: SQS model `v1.4.1` and Lambda model `v1.10.1`)
- ElastiCache-to-Kubernetes workload relationships added
- SNS Topic-to-workload reference relationships
- EventBus relationships to Deployments and Pods added
- AWS Secrets Manager links to Deployments and Pods added
- `aws-ec2-controller` Route Table to Internet Gateway relationship added
- `AzureIdentityBinding` links to `AzureIdentity` (To use: `aad-pod-identity` model version v4.1.18)
- `exoscale-icons` model adds 45 annotation icon components
- SQS Queue-to-DLQ relationship added
- AWS RDS DBProxy-to-VPC relationship added
- Relationships added to `ms-catalogs-worker`
- AWS Secrets Manager secret-rotation links for RDS and Aurora
- ECS TaskDefinition execution- and task-role links to IAM Roles
- Azure VirtualNetwork-to-Subnet relationship added
- Public IP-to-network interface relationship support
- AWS RDS inventory hierarchy relationships
- AWS API Gateway relationships for Kubernetes resources in Kanvas
- AWS Secrets Manager Secret relationships for Kubernetes workloads
- Non-binding AWS Secrets Manager Secret relationships to Kubernetes workloads (To use: `aws-secretsmanager-controller` v1.0.7)
- Six CloudWatch-to-workload reference relationships added
- Kanvas S3 Bucket relationships to Deployments and Pods (To use: An S3 Bucket connected to a Deployment or Pod in Kanvas)
- Kanvas PVC-to-Pod reference relationship
- Kubernetes `Deployment`-to-`Service` relationship (To use: Kubernetes `v1.35.0` model)
- Seven edge relationships added to `aws-rds-controller/v1.7.4`
- Redis ConfigMap sample added to the Meshery Catalog
- AWS NoSQL dependency relationships for Kubernetes workloads added
- AWS Lambda Function–DynamoDB Table relationship with environment variable injection

## Dependency updates (3)

3 more, none mentioning security

- `- Bump launch-editor from 2.12.0 to 2.14.1 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#20104)`
- `- Bump tmp from 0.2.6 to 0.2.7 in /ui @[dependabot[bot]](https://github.com/apps/dependabot) (#20080)`
- `- Rewire model data references to repo-root models/ and bump meshkit v1.0.19 @miacycle (#20312)`

## Other changes (32)

- Raunak Madan removed from `MAINTAINERS.md`
- Exoscale icon model asset generation script removed
- WASM module dependency updated
- Model files removed from `server/meshmodel`
- Visual-only ElasticsearchDomain–VPC relationships in `aws-elasticsearchservice-controller`
- Condensed `AGENTS.md` with a `CLAUDE.md` alias
- Context version validation errors wrapped in `mesheryctl system channel`
- Contributing documentation restructured
- Pattern deletion now rejects invalid design IDs
- Registry commands now default to the repository-root `models/` directory
- Channel-setting variable name corrected in `mesheryctl`
- Meaningful relationships added for Azure App Service
- Left sidebar navigation rows and caret controls updated
- Stray boolean `s` prop removed from the environment card `PopupButton`
- MeshModel registry mobile layout updated
- Environments page icons now use theme colors
- Recent Designs widget no longer clips action buttons
- Responsive preferences and performance settings UI
- GitHub workflows update `actions/checkout` to `@v6`
- Contributing documentation restructured
- Documentation-site scrollbars styled to match meshery.io
- Production AI provider usage guidance added
- Priyanshu Bharti's introduction added
- Ananyaa created
- Yana Pandey's introduction added to meeting notes
- `Ankush Khakale.md` personal introduction added
- Piyush Chandrakar's introduction added to the meetings document
- `Udaybir-Singh.md` profile information file added
- Introduction to Harsh Pratap Singh added
- Introductory note from Chethan
- sulagna-ghosh created
- `Yash-Mahakal.md` added

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
