feat: Add TLS ConfigMap parameter #269
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new field to the TrustyAI operator configuration
ConfigMapcalledtlswith can be eitherenabledordisabled.tls: enabled, payload processors will be registered with ModelMesh ashttps. This is the default value if the configuration key is missing.tls: disabled, payload processors will be registered ashttp. This is the opt-in value, only set if explicitly changed on the config map.Two overlays were also updated:
odhrhoaitlsdisabledenabledkServeServerlessenableddisabled4.14registry.redhat.io/openshift4/ose-oauth-proxy@sha256:ab112105ac37352a2a4916a39d6736f5db6ab4c29bad4467de8d613e80e9bb33This allows for:
odh: TLS-disabled and KServe integration enabledrhoai: TLS-enabled and KServe integration disabled and a pinned OAuth proxy image