Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the OpenShift release manifests and installer flag #2652

Merged
merged 1 commit into from
Jan 9, 2023

Conversation

AlanGreene
Copy link
Member

Changes

In the early days of the Dashboard project there were significant differences between the Dashboard releases on Kubernetes and OpenShift, including default provision of an oauth-proxy deployment, ingress, etc.

That is no longer the case since Tekton Dashboard v0.10.0 in September 2020, the only remaining difference between the release manifests is the namespace (openshift-pipelines vs. tekton-pipelines).

/misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Remove the OpenShift specific release manifests and the `--openshift` flag from the installer script. These existed for legacy reasons which are no longer relevant. The only remaining difference between the default and OpenShift manifests is the namespace used (`tekton-pipelines` vs. `openshift-pipelines`) and the installer script already provides a mechanism to customise this.

Action required: If you currently rely on one of the `openshift-*.yaml` release manifests, switch to the default manifests and replace references to the `tekton-pipelines` namespace with `openshift-pipelines`. Alternatively use the installer script with the `--namespace` flag to customise the value.

In the early days of the Dashboard project there were significant
differences between the Dashboard releases on Kubernetes and OpenShift,
including default provision of an `oauth-proxy` deployment, ingress, etc.

That is no longer the case since Tekton Dashboard v0.10.0 in September 2020,
the only remaining difference between the release manifests is the namespace
(`openshift-pipelines` vs. `tekton-pipelines`).
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 6, 2023
@AlanGreene
Copy link
Member Author

Some final testing in progress…
/hold

@tekton-robot tekton-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 6, 2023
@AlanGreene
Copy link
Member Author

/hold cancel

@tekton-robot tekton-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 6, 2023
Copy link
Contributor

@briangleeson briangleeson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 9, 2023
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: briangleeson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 9, 2023
@tekton-robot tekton-robot merged commit d0c0f53 into tektoncd:main Jan 9, 2023
@AlanGreene AlanGreene deleted the installer_openshift_cleanup branch January 9, 2023 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants