Skip to content

Commit

Permalink
Added overlays and renamed overrides folder to core-bases to be more …
Browse files Browse the repository at this point in the history
…aligned with kustomize format
  • Loading branch information
andrewballantyne committed Jun 25, 2024
1 parent 072b2e2 commit 3b21179
Show file tree
Hide file tree
Showing 29 changed files with 26 additions and 10 deletions.
2 changes: 1 addition & 1 deletion docs/architecture.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
[Dashboard Deployment `containers`]: ../manifests/overrides/base/deployment.yaml
[Dashboard Deployment `containers`]: ../manifests/core-bases/base/deployment.yaml
[OpenShift OAuth Proxy repo]: https://github.com/openshift/oauth-proxy
[OpenShift SDK]: https://github.com/openshift/dynamic-plugin-sdk
[SDK tidbits]: SDK.md
Expand Down
2 changes: 1 addition & 1 deletion docs/dev-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ This is the default context for running a local UI. Make sure you build the pro

> Note: You must be logged-in with `oc` before you can start the backend. Details for that are in the the [contribution guidelines](../CONTRIBUTING.md#give-your-dev-env-access).

> Note: The CLI logged-in user will need to be a `cluster-admin` level user on the cluster to mimic the Dashboard Service Account level of permissions. You could also bind the [cluster role](../manifests/overrides/base/cluster-role.yaml) to your user as we do with the service account [binding](../manifests/overrides/base/cluster-role-binding.yaml).
> Note: The CLI logged-in user will need to be a `cluster-admin` level user on the cluster to mimic the Dashboard Service Account level of permissions. You could also bind the [cluster role](../manifests/core-bases/base/cluster-role.yaml) to your user as we do with the service account [binding](../manifests/core-bases/base/cluster-role-binding.yaml).

```bash
npm run start
Expand Down
2 changes: 1 addition & 1 deletion docs/release-steps.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
[base/kustomization.yaml]: ../manifests/overrides/base/kustomization.yaml
[base/kustomization.yaml]: ../manifests/core-bases/base/kustomization.yaml
[quay repo]: https://quay.io/repository/opendatahub/odh-dashboard?tab=tags
[drafting a new release]: https://github.com/opendatahub-io/odh-dashboard/releases/new
[semver]: https://semver.org/
Expand Down
2 changes: 1 addition & 1 deletion manifests/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Each deployment type will have a `params.env` file where the Operator can inject

Rules for keeping the manifest files in a sane order:

1. When adding a new type of thing, always make it have its own folder; be sure to add the reference to the parent folder's `kustomziation.yaml` (if applicable)
1. When adding a new type of thing, always make it have its own folder; be sure to add the reference to the parent folder's `kustomziation.yaml` (if applicable)
2. When adding to a preexisting folder, be sure to add it to the root `kustomization.yaml` in that folder
3. Do not reference "a file" (has an extension) inside another folder. Reference other folders, which will pick up the `kustomization.yaml` inside that folder; those `kustomization.yaml` files should reference sibling files
4. Folders matter -- see the README in each for more details
Expand Down
2 changes: 1 addition & 1 deletion manifests/common/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@ These are manifests that are shared in both ODH & RHOAI deployments.

These files are not intended to be the base of overriding or changing in any way. These should be immutable between both RHOAI and ODH deployments.

> **Note:** See the [`../overrides`](../overrides/README.md) folder for those that can be overridden
> **Note:** See the [`../overrides`](../core-bases/README.md) folder for those that can be overridden
5 changes: 5 additions & 0 deletions manifests/core-bases/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Core-Bases Manifests

These are manifest files that are intended to be used in part by other deployments and configured for their own use-cases.

> **Note:** There should be note root `kustomization.yaml` as each folder should be treated as a specific target for inclusion or overrides.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
7 changes: 7 additions & 0 deletions manifests/overlays/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Overlay Manifests

These are shared modifications to existing deployments. These set of folders are to be considered for custom deployments or modifications to existing deployments to suit adhoc and non-operator default deployments.

> **Note:** Consider making overlays inside each deployment if your overlay is non-generic.
Each overlay should come with a readme to help with the use-case for it.
3 changes: 3 additions & 0 deletions manifests/overlays/dev/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# Dev Overlay

Allows for custom direct deployments of the min-viable resources. Used by the custom deployment install without the operator.
6 changes: 6 additions & 0 deletions manifests/overlays/dev/kustomization.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- ../common/crd
- ../core-bases/base
- ../common/apps
5 changes: 0 additions & 5 deletions manifests/overrides/README.md

This file was deleted.

0 comments on commit 3b21179

Please sign in to comment.