You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, these are the hoops you have to jump through if, for example, you want to change the deployment's readiness probe:
Kuby.definition('myapp')doenvironment(:production)dokubernetesdoadd_plugin(:rails_app)dodeployment.spec.template.spec.container(:web).readiness_probedotimeout_seconds1# custom value goes hereendendendendend
Obviously that's neither obvious or discoverable, unless you're really familiar with Kuby's source code. Some config options like tls_enabled are already conveniently exposed as properties. It would be nice to expose a bunch of others as properties too. That way, modifying the readiness probe could be as easy as
where the call to web_readiness_probe is just a convenience method that returns the web pod's readiness object (which is an instance of KubeDSL::DSL::V1::Probe).
The text was updated successfully, but these errors were encountered:
Right now, these are the hoops you have to jump through if, for example, you want to change the deployment's readiness probe:
Obviously that's neither obvious or discoverable, unless you're really familiar with Kuby's source code. Some config options like
tls_enabled
are already conveniently exposed as properties. It would be nice to expose a bunch of others as properties too. That way, modifying the readiness probe could be as easy asor even
where the call to
web_readiness_probe
is just a convenience method that returns the web pod's readiness object (which is an instance ofKubeDSL::DSL::V1::Probe
).The text was updated successfully, but these errors were encountered: