Add 'namespace' config for NSaaS #9531
Draft
Conversation
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
fridim
changed the title
fridim
force-pushed
the
nsaas-config-and-example
branch
from
939e911 to
99d9e19
Compare
This introduces a new namespace configuration designed to deploy OpenShift workloads directly to an existing namespace without requiring infrastructure provisioning or a bastion host. This approach is for users who have direct, but potentially limited, namespace-level access to a shared OpenShift cluster and do not manage the underlying infrastructure. The configuration runs on localhost and connects to the OpenShift API using provided credentials (API token or username/password). Workloads to be deployed are specified in the ocp_workloads_namespaced list variable. A new example role, ocp_workloads_namespaced_example, is included to demonstrate how to build compatible, namespaced workloads. This role shows: - Adding oc login initial authentication. - Managing Kubernetes resources (Deployment, Service) and OpenShift resources (Route) via the kubernetes.core.k8s module and Jinja2 templates. - Including lifecycle tasks for creation, verification, and destruction of the application.
fridim
force-pushed
the
nsaas-config-and-example
branch
from
99d9e19 to
2060858
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 introduces a new namespace configuration designed to deploy OpenShift workloads directly to an existing namespace without requiring infrastructure provisioning or a bastion host.
This approach is for users who have direct, but potentially limited, namespace-level access to a shared OpenShift cluster and do not manage the underlying infrastructure.
The configuration runs on localhost and connects to the OpenShift API using provided credentials (API token or username/password). Workloads to be deployed are specified in the ocp_workloads_namespaced list variable.
A new example role, ocp_workloads_namespaced_example, is included to demonstrate how to build compatible, namespaced workloads. This role shows:
SUMMARY
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION