Skip to content

feat: Support Istio Virtual Service - #626

Open
LeoDOD wants to merge 7 commits into
stakater:mainfrom
LeoDOD:feature/support-virtualservice
Open

feat: Support Istio Virtual Service#626
LeoDOD wants to merge 7 commits into
stakater:mainfrom
LeoDOD:feature/support-virtualservice

Conversation

@LeoDOD

@LeoDOD LeoDOD commented Aug 28, 2026

Copy link
Copy Markdown

Changes

  • added virtualService section to values.yaml with full documentation (hosts, gateways, exportTo, http, tls, tcp, routes)
  • added virtualService schema block to values.schema.json
  • created templates/virtualservice.yaml : supports single-VS and multi-VS (routes map) modes; http/tls/tcp are toYaml pass-through.
  • API version auto-detects networking.istio.io/v1 vs v1beta1
  • Added test to validate the new template.

Remarks

  • virtualService.enabled defaults to false to be fully backwards compatible
  • when routes is omitted, a single VirtualService is rendered using the top-level virtualService fields; when routes is a map, one VirtualService is rendered per entry (name suffix skipped when key is "default")

@LeoDOD LeoDOD changed the title Feature/support Istio VirtualService feat: Support Istio Virtual Service Aug 28, 2026
LeoDOD and others added 4 commits August 28, 2026 10:07
Added tests for Istio VirtualService configuration including rendering conditions, API version handling, and route specifications.
- Introduced a comprehensive schema for the VirtualService configuration, including properties such as enabled, exportTo, gateways, hosts, http, routes, tcp, and tls.
- Enhanced descriptions for each property to clarify usage and requirements.
- Removed the previous, less detailed VirtualService schema to streamline the configuration process.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants