Skip to content

feat(helm): add licenseProxy values for corporate HTTP proxy support#5

Merged
Cadolbeau merged 2 commits into
mainfrom
feat/license-proxy-values
May 29, 2026
Merged

feat(helm): add licenseProxy values for corporate HTTP proxy support#5
Cadolbeau merged 2 commits into
mainfrom
feat/license-proxy-values

Conversation

@cadolbeau-absyss

Copy link
Copy Markdown
Contributor

Summary

  • Add a licenseProxy section to values.yaml (host, port, user, password) that automatically generates a ConfigMap containing license.config and mounts it into vtom-server, vtom-apiserver, itc, and itm
  • Allows the Absyss Java license client to reach license-ctrl.customer.absyss.com through a corporate HTTP proxy without any manual Kubernetes object creation
  • When licenseProxy.host is empty (default), no ConfigMap is created and no volume mount is added — existing deployments are unaffected
  • Fixes the missing license.config mount on vtom-server (deployment-server.yaml), which had no proxy support even when configured manually
  • Updates values-client-template.yaml with the new commented section so operators are aware of the option

Usage

licenseProxy:
  host: "proxy.corp.example.com"
  port: 3128
  user: ""        # leave empty if the proxy requires no authentication
  password: ""    # leave empty if the proxy requires no authentication

Test plan

  • helm template with licenseProxy.host set renders the ConfigMap and volume mounts in all 4 deployments
  • helm template with licenseProxy.host empty renders no ConfigMap and no volume mounts
  • Pods start and license registration succeeds in a proxied on-premise environment

Add a licenseProxy section to values.yaml (host, port, user, password)
that automatically generates a ConfigMap containing license.config and
mounts it into vtom-server, vtom-apiserver, itc, and itm. This allows
the Absyss Java license client to reach license-ctrl.customer.absyss.com
through a corporate HTTP proxy without any manual Kubernetes object creation.

When licenseProxy.host is empty (default), no ConfigMap is created and no
volume mount is added — existing deployments are unaffected.

Also adds the missing license.config mount to vtom-server (deployment-server.yaml),
which previously had no proxy support even when configured manually.

The values-client-template.yaml is updated with the new commented section
so operators are aware of the option during deployment.

@Cadolbeau Cadolbeau left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@Cadolbeau Cadolbeau merged commit 2a8a860 into main May 29, 2026
4 checks passed
@Cadolbeau Cadolbeau deleted the feat/license-proxy-values branch May 29, 2026 10:01
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