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
Adds values.openshift.yaml with ready-to-use OpenShift overrides.
Adds an OpenShift Route template to provide TCP passthrough access to the worker proxy port.
Switches the proxy Service to ClusterIP when OpenShift support is enabled, with the Route handling external traffic.
Applies an OpenShift-compatible security context by removing fixed UID/GID settings so SCC can assign values from the namespace range.
Makes PVC storageClass conditional, allowing the cluster default storage class to be used when left unset.
Adds a new openshift: configuration section to values.yaml (disabled by default).
Adds unit tests covering all new OpenShift-specific paths.
##Testing
Tested on OpenShift Local (CRC). The worker successfully authenticated to a self-managed Boundary controller using the OpenShift-specific chart configuration.
Related
Issue:
Chart/Component:
Checklist
I have documented a clear reason for, and description of, the change I am making.
Added/updated tests or validation steps (if applicable)
Verified local lint/validation
No breaking changes, or clearly documented
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Summary
Adds values.openshift.yaml with ready-to-use OpenShift overrides.
Adds an OpenShift Route template to provide TCP passthrough access to the worker proxy port.
Switches the proxy Service to ClusterIP when OpenShift support is enabled, with the Route handling external traffic.
Applies an OpenShift-compatible security context by removing fixed UID/GID settings so SCC can assign values from the namespace range.
Makes PVC storageClass conditional, allowing the cluster default storage class to be used when left unset.
Adds a new openshift: configuration section to values.yaml (disabled by default).
Adds unit tests covering all new OpenShift-specific paths.
##Testing
Tested on OpenShift Local (CRC). The worker successfully authenticated to a self-managed Boundary controller using the OpenShift-specific chart configuration.
Related
Checklist
I have documented a clear reason for, and description of, the change I am making.
Added/updated tests or validation steps (if applicable)
Verified local lint/validation
No breaking changes, or clearly documented
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.