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

Use versioned links for installation instructions #180

Merged
merged 1 commit into from
Apr 4, 2022

Conversation

cbgbt
Copy link
Contributor

@cbgbt cbgbt commented Apr 4, 2022

Issue number: #179

Description of changes: Doc change. This uses a versioned link to Brupop's YAML documents for installation instructions, which should prevent issues of pulling mismatched CRD definitions from the latest released version of Brupop.

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

@@ -10,14 +10,17 @@ Updates to Bottlerocket are rolled out in [waves](https://github.com/bottlerocke

### Installation

We can install the Bottlerocket update operator using the recommended configuration defined in [bottlerocket-update-operator.yaml](./bottlerocket-update-operator.yaml):
We can install the Bottlerocket update operator using the recommended configuration defined in [bottlerocket-update-operator.yaml](https://github.com/bottlerocket-os/bottlerocket-update-operator/blob/v0.2.0/yamlgen/deploy/bottlerocket-update-operator.yaml):

```sh
kubectl apply -f ./bottlerocket-update-operator.yaml
Copy link
Member

Choose a reason for hiding this comment

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

Just curious and question if customers ignore the recommended configuration link above, and directly run this command with latest changes of brupop. Will they still use latest version of CRD and meet same issue because ./bottlerocket-update-operator.yaml still symlink to yamlgen/deploy/bottlerocket-update-operator.yaml?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Unfortunately so. I think this continues to be a way to make a mistake until we merge #161, which should make the CRDs immutable. Then it won't matter so long as your CRD deployment is newer than the latest release.

Copy link
Member

@gthao313 gthao313 left a comment

Choose a reason for hiding this comment

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

🚀

@cbgbt cbgbt merged commit 327c868 into bottlerocket-os:develop Apr 4, 2022
@cbgbt cbgbt deleted the versioned branch August 10, 2023 08:05
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.

None yet

3 participants