THREESCALE-12448 - Add configuration option to enable openshift deterministically by urbanikb · Pull Request #580 · 3scale/zync

urbanikb · 2026-03-18T06:38:38Z

This is needed by THREESCALE-12448 to enable the openshift integration mode even if the services don't exist yet.

Verification

Tested locally to verify that route can be created even if service does not exist. This was done by commenting the apicast routes and developer services - there are 2 services necessary to exist for the startup - the sidekiq requires system-master to be up and zync requires system-provider to be up (it communicates with it - see

zync/app/adapters/three_scale/api/instrumented_http_client.rb

Line 11 in a852c44

if (system_provider_port = ENV['SYSTEM_PROVIDER_PORT'].presence)

).

Routes have been created successfully even for apicast and developer portal:

% oc get routes
NAME                         HOST/PORT                                                                  PATH   SERVICES             PORT      TERMINATION     WILDCARD
backend                      backend-3scale.apps.3scale-bu.3scale.app-services-dev.net                         backend-listener     http      edge/Allow      None
zync-3scale-api-crtfb        api-3scale-apicast-production.apps.3scale-bu.3scale.app-services-dev.net          apicast-production   gateway   edge/Redirect   None
zync-3scale-api-msspt        api-3scale-apicast-staging.apps.3scale-bu.3scale.app-services-dev.net             apicast-staging      gateway   edge/Redirect   None
zync-3scale-master-xgf8h     master.apps.3scale-bu.3scale.app-services-dev.net                                 system-master        http      edge/Redirect   None
zync-3scale-provider-nfl98   3scale.apps.3scale-bu.3scale.app-services-dev.net                                 system-developer     http      edge/Redirect   None
zync-3scale-provider-ngtmd   3scale-admin.apps.3scale-bu.3scale.app-services-dev.net                           system-provider      http      edge/Redirect   None

borisurbanik@Boriss-MacBook-Pro 3scale-operator % oc get deployment zync-que -n 3scale-test -o jsonpath='{.spec.template.spec.containers[0].image}'
quay.io/3scale/zync:true-openshift%
borisurbanik@Boriss-MacBook-Pro 3scale-operator % oc exec deployment/zync-que -- bundle exec rails runner "puts Rails.application.config.x.openshift.enabled"
W, [2026-03-18T15:49:19.100518 #156]  WARN -- [Bugsnag]: No valid API key has been set, notifications will not be sent
true

borisurbanik@Boriss-MacBook-Pro 3scale-operator % oc get svc
NAME               TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)     AGE
backend-listener   ClusterIP   172.30.238.121   <none>        3000/TCP    9m54s
backend-redis      ClusterIP   172.30.9.96      <none>        6379/TCP    32m
system-master      ClusterIP   172.30.223.6     <none>        3000/TCP    6m31s
system-memcache    ClusterIP   172.30.115.154   <none>        11211/TCP   9m9s
system-mysql       ClusterIP   172.30.240.116   <none>        3306/TCP    32m
system-provider    ClusterIP   172.30.174.35    <none>        3000/TCP    9m9s
system-redis       ClusterIP   172.30.39.81     <none>        6379/TCP    32m
system-searchd     ClusterIP   172.30.210.149   <none>        9306/TCP    9m49s
zync               ClusterIP   172.30.110.145   <none>        8080/TCP    9m10s
zync-database      ClusterIP   172.30.110.194   <none>        5432/TCP    9m10s

borisurbanik@Boriss-MacBook-Pro 3scale-operator % oc exec deployment/zync-que -c que -- env | grep -E 'APICAST_|SYSTEM_'
SYSTEM_REDIS_PORT_6379_TCP_ADDR=172.30.39.81
SYSTEM_SEARCHD_SERVICE_PORT=9306
SYSTEM_PROVIDER_SERVICE_PORT=3000
SYSTEM_MYSQL_SERVICE_HOST=172.30.240.116
SYSTEM_MEMCACHE_PORT_11211_TCP_PROTO=tcp
SYSTEM_REDIS_SERVICE_HOST=172.30.39.81
SYSTEM_MEMCACHE_PORT_11211_TCP=tcp://172.30.115.154:11211
SYSTEM_MYSQL_PORT_3306_TCP_PORT=3306
SYSTEM_MYSQL_PORT_3306_TCP_ADDR=172.30.240.116
SYSTEM_PROVIDER_SERVICE_HOST=172.30.174.35
SYSTEM_PROVIDER_PORT_3000_TCP_PORT=3000
SYSTEM_REDIS_PORT_6379_TCP=tcp://172.30.39.81:6379
SYSTEM_MYSQL_PORT=tcp://172.30.240.116:3306
SYSTEM_PROVIDER_SERVICE_PORT_HTTP=3000
SYSTEM_REDIS_PORT=tcp://172.30.39.81:6379
SYSTEM_REDIS_SERVICE_PORT=6379
SYSTEM_MEMCACHE_SERVICE_PORT_MEMCACHE=11211
SYSTEM_SEARCHD_SERVICE_HOST=172.30.210.149
SYSTEM_SEARCHD_PORT_9306_TCP=tcp://172.30.210.149:9306
SYSTEM_SEARCHD_PORT_9306_TCP_ADDR=172.30.210.149
SYSTEM_PROVIDER_PORT_3000_TCP=tcp://172.30.174.35:3000
SYSTEM_MYSQL_PORT_3306_TCP=tcp://172.30.240.116:3306
SYSTEM_MYSQL_PORT_3306_TCP_PROTO=tcp
SYSTEM_MYSQL_SERVICE_PORT=3306
SYSTEM_PROVIDER_PORT=tcp://172.30.174.35:3000
SYSTEM_REDIS_PORT_6379_TCP_PORT=6379
SYSTEM_MEMCACHE_SERVICE_PORT=11211
SYSTEM_MEMCACHE_PORT_11211_TCP_ADDR=172.30.115.154
SYSTEM_SEARCHD_PORT=tcp://172.30.210.149:9306
SYSTEM_SEARCHD_PORT_9306_TCP_PORT=9306
SYSTEM_MEMCACHE_SERVICE_HOST=172.30.115.154
SYSTEM_SEARCHD_SERVICE_PORT_SEARCHD=9306
SYSTEM_MEMCACHE_PORT=tcp://172.30.115.154:11211
SYSTEM_SEARCHD_PORT_9306_TCP_PROTO=tcp
SYSTEM_MEMCACHE_PORT_11211_TCP_PORT=11211
SYSTEM_PROVIDER_PORT_3000_TCP_PROTO=tcp
SYSTEM_REDIS_PORT_6379_TCP_PROTO=tcp
SYSTEM_PROVIDER_PORT_3000_TCP_ADDR=172.30.174.35

After startup with services commented out the developer portal shows maintenance page:
.

The page starts to serve the developer portal once the service is created later without any action needed on Zync end.

akostadinov · 2026-03-18T12:35:33Z

config/openshift.yml

Suggested change

enabled: true

Hm, I am wondering, can what if we drop this config file, and in the place were currently Rails.application.config.x.openshift.enabled is used we use Rails.application.config.integrations.kubernetes instead? Because it kind of seems strange that we have two different configs for enabling/disabling the same integration (well, assuming they are the same).

If for some reason we need to keep this openshift.yml file, I would hardcode enabled: true just for the production environment, and keep false for dev and test.

But I'd prefer to get rid of it.

This is the openshift connection configuration kind of and the other file is ability to select which integrations are enabled. Given Zync's purpose was to have many integrations over time, it makes some sense.

But if we don't support any actual openshift configuration, we can as well remove openshift.yml as needless.

I suggest though to for now hardcode true here and go about removing this separately if we want. Nice catch that we want false for development as well!

Current code uses service discovery env var. Adding new SYSTEM_PROVIDER_URL that can be set to route requests internally when not using service discovery links.

akostadinov · 2026-03-19T15:29:16Z

app/adapters/three_scale/api/instrumented_http_client.rb

+    #
+    # SYSTEM_PROVIDER_URL - explicit URL set by the operator (e.g. http://system-provider:3000)
+    # SYSTEM_PROVIDER_PORT - legacy: injected by Kubernetes service discovery
+    if (system_provider_url = (ENV['SYSTEM_PROVIDER_URL'] || ENV['SYSTEM_PROVIDER_PORT']).presence)


Boris: if we run in kubernetes, then maybe hardcode the DNS name, otherwise use the host from the message

akostadinov reviewed Mar 18, 2026

View reviewed changes

Enable openshift by default; Add additional var for provider url

26fe871

Current code uses service discovery env var. Adding new SYSTEM_PROVIDER_URL that can be set to route requests internally when not using service discovery links.

urbanikb force-pushed the THREESCALE-12448 branch from 6f34c80 to 26fe871 Compare March 18, 2026 17:06

akostadinov reviewed Mar 19, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

THREESCALE-12448 - Add configuration option to enable openshift deterministically#580

THREESCALE-12448 - Add configuration option to enable openshift deterministically#580
urbanikb wants to merge 1 commit into3scale:masterfrom
urbanikb:THREESCALE-12448

urbanikb commented Mar 18, 2026 •

edited

Loading

Uh oh!

akostadinov Mar 18, 2026

Uh oh!

mayorova Mar 18, 2026

Uh oh!

akostadinov Mar 18, 2026

Uh oh!

akostadinov Mar 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

urbanikb commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Verification

Uh oh!

akostadinov Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

mayorova Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

akostadinov Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

akostadinov Mar 19, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

urbanikb commented Mar 18, 2026 •

edited

Loading