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

add version information #46

Merged

Conversation

everettraven
Copy link
Collaborator

@everettraven everettraven commented Apr 13, 2023

Description:

  • Adds an internal version package with:

    • A function for getting the controller version information
    • A function for getting the apiserver version information
  • Updates the Makefile to set the necessary version flags when building

  • Adds a --version flag to the controller manager

  • Updates goreleaser to set the version flags when building the controller and apiserver

  • In a follow up, we will have to configure the version information for the apiserver. The apiserver-runtime package that we are currently using to build the apiserver hardcodes version information that overrides any of the information we include. I left a TODO comment to reflect this. A solution is to update the apiserver-runtime tooling OR create or own implementation that we use to set the version info. This can likely be addressed as part of Remove Catalogmetadata CRD and serve CatalogMetadata with aggregated apiserver #39 when we configure the apiserver to work properly.

Motivation:

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 13, 2023
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 17, 2023
Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 17, 2023
@everettraven everettraven marked this pull request as ready for review April 17, 2023 19:40
@everettraven everettraven removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 17, 2023
@everettraven everettraven changed the title WIP: add version information add version information Apr 17, 2023
.goreleaser.yml Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Signed-off-by: Bryce Palmer <bpalmer@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add version information
3 participants