Skip to content

Deployment manifest generated by deploy.sh tracks latest instead of tagged version #2970

@vidarno

Description

@vidarno

What steps did you take and what happened:
Cloned a specific version/tag of the repo with
git clone --branch v0.12.1 https://github.com/metal3-io/baremetal-operator.git
Ran
deploy.sh
which generates manifests that include a Deployment which does not include the tag, so the image will default to track "latest".

What did you expect to happen:
I expected the version to be pinned to the tag/version I cloned

Anything else you would like to add:
This issue is based on issue #2960 which covered several things. The topic was discussed in the last community meeting and users have reported the same issue in our Slack.

A PR is incoming shortly.

Environment:

  • Baremetal Operator version: v0.12.1
  • Environment (metal3-dev-env or other): N/A

/kind bug

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.triage/acceptedIndicates an issue is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions